git lab integration with kubernate cluster with “Add existing kubernate cluster” option











up vote
0
down vote

favorite












I'm trying to integrate a Kubernetes cluster into gitlab by using the "Add existing Kubernetes cluster" option. This integration is required to configure this cluster as a Runner in gitlab to execute the build.



Below details have been provided for the integration:



Kubernetes cluster name : kube_cluster
API URL : https://ipadress:port ex: https://10.8.9.0:8443
CA certificate:
CA certificate from kubernate cluster
Token: token obtained by below command
kubectl -o json get secret default-xxxxx-ght | jq -r '.data.token' | base64 -d > token.txt


but the integration fails during the Helm installation without a proper error message in git lab. How to solve this issue? Is there a way to find out what is actually failing in background?



Error message:



"Something went wrong while installing Helm Tiller
Can't start installation process"


enter image description here










share|improve this question
























  • Do you have access to your Kubernetes cluster?
    – Rico
    Nov 10 at 0:10















up vote
0
down vote

favorite












I'm trying to integrate a Kubernetes cluster into gitlab by using the "Add existing Kubernetes cluster" option. This integration is required to configure this cluster as a Runner in gitlab to execute the build.



Below details have been provided for the integration:



Kubernetes cluster name : kube_cluster
API URL : https://ipadress:port ex: https://10.8.9.0:8443
CA certificate:
CA certificate from kubernate cluster
Token: token obtained by below command
kubectl -o json get secret default-xxxxx-ght | jq -r '.data.token' | base64 -d > token.txt


but the integration fails during the Helm installation without a proper error message in git lab. How to solve this issue? Is there a way to find out what is actually failing in background?



Error message:



"Something went wrong while installing Helm Tiller
Can't start installation process"


enter image description here










share|improve this question
























  • Do you have access to your Kubernetes cluster?
    – Rico
    Nov 10 at 0:10













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm trying to integrate a Kubernetes cluster into gitlab by using the "Add existing Kubernetes cluster" option. This integration is required to configure this cluster as a Runner in gitlab to execute the build.



Below details have been provided for the integration:



Kubernetes cluster name : kube_cluster
API URL : https://ipadress:port ex: https://10.8.9.0:8443
CA certificate:
CA certificate from kubernate cluster
Token: token obtained by below command
kubectl -o json get secret default-xxxxx-ght | jq -r '.data.token' | base64 -d > token.txt


but the integration fails during the Helm installation without a proper error message in git lab. How to solve this issue? Is there a way to find out what is actually failing in background?



Error message:



"Something went wrong while installing Helm Tiller
Can't start installation process"


enter image description here










share|improve this question















I'm trying to integrate a Kubernetes cluster into gitlab by using the "Add existing Kubernetes cluster" option. This integration is required to configure this cluster as a Runner in gitlab to execute the build.



Below details have been provided for the integration:



Kubernetes cluster name : kube_cluster
API URL : https://ipadress:port ex: https://10.8.9.0:8443
CA certificate:
CA certificate from kubernate cluster
Token: token obtained by below command
kubectl -o json get secret default-xxxxx-ght | jq -r '.data.token' | base64 -d > token.txt


but the integration fails during the Helm installation without a proper error message in git lab. How to solve this issue? Is there a way to find out what is actually failing in background?



Error message:



"Something went wrong while installing Helm Tiller
Can't start installation process"


enter image description here







kubernetes gitlab






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 10 at 0:09









Rico

23.8k94864




23.8k94864










asked Nov 9 at 9:30









Rakesh G

11




11












  • Do you have access to your Kubernetes cluster?
    – Rico
    Nov 10 at 0:10


















  • Do you have access to your Kubernetes cluster?
    – Rico
    Nov 10 at 0:10
















Do you have access to your Kubernetes cluster?
– Rico
Nov 10 at 0:10




Do you have access to your Kubernetes cluster?
– Rico
Nov 10 at 0:10












1 Answer
1






active

oldest

votes

















up vote
0
down vote













According to their issue, one needs to upgrade the GitLab version to v11.1 to work around that bug, although another person is experiencing TLS weirdness after upgrading, so watch out for that, too






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',
    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%2f53223036%2fgit-lab-integration-with-kubernate-cluster-with-add-existing-kubernate-cluster%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








    up vote
    0
    down vote













    According to their issue, one needs to upgrade the GitLab version to v11.1 to work around that bug, although another person is experiencing TLS weirdness after upgrading, so watch out for that, too






    share|improve this answer

























      up vote
      0
      down vote













      According to their issue, one needs to upgrade the GitLab version to v11.1 to work around that bug, although another person is experiencing TLS weirdness after upgrading, so watch out for that, too






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        According to their issue, one needs to upgrade the GitLab version to v11.1 to work around that bug, although another person is experiencing TLS weirdness after upgrading, so watch out for that, too






        share|improve this answer












        According to their issue, one needs to upgrade the GitLab version to v11.1 to work around that bug, although another person is experiencing TLS weirdness after upgrading, so watch out for that, too







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 10 at 19:19









        Matthew L Daniel

        6,41511826




        6,41511826






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53223036%2fgit-lab-integration-with-kubernate-cluster-with-add-existing-kubernate-cluster%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

            Florida Star v. B. J. F.

            Error while running script in elastic search , gateway timeout

            Adding quotations to stringified JSON object values