CI/CD pipeline using Git-Lab , Helm and Kubernete cluster (Nginx-Ingress) in AWS












0














Is it possible to create a fully automated CI/CD pipeline :- example
suppose developer commit the code of frontend microservice and backend microservice then CI/CD pipelines start and we just need to browse that service using domain without manual work.










share|improve this question






















  • Anything is possible in theory. Whether or not something is feasible in a certain environment, within a certain timeframe, etc., is another question. But to answer your question more directly, I've built a CI/CD pipeline in GitLab before that will take any changes and redeploy in various environments. The tech stack was similar: microservices, Kubernetes, Helm, etc.
    – Lansana
    Nov 12 at 13:38












  • Lansana ..... I am stucking in how to attach the domain automatically after success CD to any environment
    – Lakshman raj Singh Banafar
    Nov 13 at 5:50










  • you can install helm and register gitlab runner to your repo and using gitlab-ci setup the pipeline steps.
    – c4f4t0r
    Nov 15 at 16:34
















0














Is it possible to create a fully automated CI/CD pipeline :- example
suppose developer commit the code of frontend microservice and backend microservice then CI/CD pipelines start and we just need to browse that service using domain without manual work.










share|improve this question






















  • Anything is possible in theory. Whether or not something is feasible in a certain environment, within a certain timeframe, etc., is another question. But to answer your question more directly, I've built a CI/CD pipeline in GitLab before that will take any changes and redeploy in various environments. The tech stack was similar: microservices, Kubernetes, Helm, etc.
    – Lansana
    Nov 12 at 13:38












  • Lansana ..... I am stucking in how to attach the domain automatically after success CD to any environment
    – Lakshman raj Singh Banafar
    Nov 13 at 5:50










  • you can install helm and register gitlab runner to your repo and using gitlab-ci setup the pipeline steps.
    – c4f4t0r
    Nov 15 at 16:34














0












0








0







Is it possible to create a fully automated CI/CD pipeline :- example
suppose developer commit the code of frontend microservice and backend microservice then CI/CD pipelines start and we just need to browse that service using domain without manual work.










share|improve this question













Is it possible to create a fully automated CI/CD pipeline :- example
suppose developer commit the code of frontend microservice and backend microservice then CI/CD pipelines start and we just need to browse that service using domain without manual work.







amazon-web-services kubernetes devops gitlab-ci helm






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 at 13:24









Lakshman raj Singh Banafar

111




111












  • Anything is possible in theory. Whether or not something is feasible in a certain environment, within a certain timeframe, etc., is another question. But to answer your question more directly, I've built a CI/CD pipeline in GitLab before that will take any changes and redeploy in various environments. The tech stack was similar: microservices, Kubernetes, Helm, etc.
    – Lansana
    Nov 12 at 13:38












  • Lansana ..... I am stucking in how to attach the domain automatically after success CD to any environment
    – Lakshman raj Singh Banafar
    Nov 13 at 5:50










  • you can install helm and register gitlab runner to your repo and using gitlab-ci setup the pipeline steps.
    – c4f4t0r
    Nov 15 at 16:34


















  • Anything is possible in theory. Whether or not something is feasible in a certain environment, within a certain timeframe, etc., is another question. But to answer your question more directly, I've built a CI/CD pipeline in GitLab before that will take any changes and redeploy in various environments. The tech stack was similar: microservices, Kubernetes, Helm, etc.
    – Lansana
    Nov 12 at 13:38












  • Lansana ..... I am stucking in how to attach the domain automatically after success CD to any environment
    – Lakshman raj Singh Banafar
    Nov 13 at 5:50










  • you can install helm and register gitlab runner to your repo and using gitlab-ci setup the pipeline steps.
    – c4f4t0r
    Nov 15 at 16:34
















Anything is possible in theory. Whether or not something is feasible in a certain environment, within a certain timeframe, etc., is another question. But to answer your question more directly, I've built a CI/CD pipeline in GitLab before that will take any changes and redeploy in various environments. The tech stack was similar: microservices, Kubernetes, Helm, etc.
– Lansana
Nov 12 at 13:38






Anything is possible in theory. Whether or not something is feasible in a certain environment, within a certain timeframe, etc., is another question. But to answer your question more directly, I've built a CI/CD pipeline in GitLab before that will take any changes and redeploy in various environments. The tech stack was similar: microservices, Kubernetes, Helm, etc.
– Lansana
Nov 12 at 13:38














Lansana ..... I am stucking in how to attach the domain automatically after success CD to any environment
– Lakshman raj Singh Banafar
Nov 13 at 5:50




Lansana ..... I am stucking in how to attach the domain automatically after success CD to any environment
– Lakshman raj Singh Banafar
Nov 13 at 5:50












you can install helm and register gitlab runner to your repo and using gitlab-ci setup the pipeline steps.
– c4f4t0r
Nov 15 at 16:34




you can install helm and register gitlab runner to your repo and using gitlab-ci setup the pipeline steps.
– c4f4t0r
Nov 15 at 16:34












1 Answer
1






active

oldest

votes


















0














I see two possible approaches to it.



First, you can run GitLab Runner on AWS. Read this on deploying elastic and cost-optimized setup on AWS.



Another approach is to integrate your GitLab repo with AWS CodePipeline (or AWS CodeBuild) using GitLab webhook, AWS API Gateway, and AWS Lambda.



Another part of the thing you need to implement as a part of the CI/CD flow is how you control your Kubernetes cluster to update it with a new microservice version. Use Kubernetes API or Kubernetes Client Library.



Best regards.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263143%2fci-cd-pipeline-using-git-lab-helm-and-kubernete-cluster-nginx-ingress-in-aws%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I see two possible approaches to it.



    First, you can run GitLab Runner on AWS. Read this on deploying elastic and cost-optimized setup on AWS.



    Another approach is to integrate your GitLab repo with AWS CodePipeline (or AWS CodeBuild) using GitLab webhook, AWS API Gateway, and AWS Lambda.



    Another part of the thing you need to implement as a part of the CI/CD flow is how you control your Kubernetes cluster to update it with a new microservice version. Use Kubernetes API or Kubernetes Client Library.



    Best regards.






    share|improve this answer


























      0














      I see two possible approaches to it.



      First, you can run GitLab Runner on AWS. Read this on deploying elastic and cost-optimized setup on AWS.



      Another approach is to integrate your GitLab repo with AWS CodePipeline (or AWS CodeBuild) using GitLab webhook, AWS API Gateway, and AWS Lambda.



      Another part of the thing you need to implement as a part of the CI/CD flow is how you control your Kubernetes cluster to update it with a new microservice version. Use Kubernetes API or Kubernetes Client Library.



      Best regards.






      share|improve this answer
























        0












        0








        0






        I see two possible approaches to it.



        First, you can run GitLab Runner on AWS. Read this on deploying elastic and cost-optimized setup on AWS.



        Another approach is to integrate your GitLab repo with AWS CodePipeline (or AWS CodeBuild) using GitLab webhook, AWS API Gateway, and AWS Lambda.



        Another part of the thing you need to implement as a part of the CI/CD flow is how you control your Kubernetes cluster to update it with a new microservice version. Use Kubernetes API or Kubernetes Client Library.



        Best regards.






        share|improve this answer












        I see two possible approaches to it.



        First, you can run GitLab Runner on AWS. Read this on deploying elastic and cost-optimized setup on AWS.



        Another approach is to integrate your GitLab repo with AWS CodePipeline (or AWS CodeBuild) using GitLab webhook, AWS API Gateway, and AWS Lambda.



        Another part of the thing you need to implement as a part of the CI/CD flow is how you control your Kubernetes cluster to update it with a new microservice version. Use Kubernetes API or Kubernetes Client Library.



        Best regards.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 12 at 14:17









        Maksim Aniskov

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263143%2fci-cd-pipeline-using-git-lab-helm-and-kubernete-cluster-nginx-ingress-in-aws%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Bressuire

            Vorschmack

            Quarantine