Comment by Robert Nsinga on "Ask anything to GitLab"

I just created a fresh GCP cluster, successfully linked it to my gitlab.com project settings (under Kubernetes integrations) and now I'm a bit confused by a failing "staging" job that returns Unable to connect to the server: x509: certificate signed by unknown authority ERROR: Job failed: exit code 1. Btw, I'm following this tutorial (https://www.youtube.com/watch?v=PoBaY_rqeKA) and I can't go past editing the.gitlab-ci.yml config file KUBE_DOMAIN value which is the IP of my Kubernetes master. Any reaction is most welcome. And yes I did a kubectl describe -o yaml and copied the ca.crt and token values into the appropriate fields.

Sounds like a problem with the certificate authority. I don't think this is the best place to try to resolve you issues, as we don't have the ability to easily follow up.

Can you create an issue in our issue tracker? https://gitlab.com/gitlab-org/gitlab-ce/issues

Hey, probably certificate issue. Maybe badly copied credentials from GCP.

Btw take a look at quick start guide I made for GKE + GitLab.com docs.gitlab.com/ce/topics/autodevops/quick_start_…. I tested it several times to confirm it works.

Hey @Job, I'm working with the default ca.crt PEM in secrets. Is it self-signed? If yes, is that why staging is rejected? I don't mind filing an issue, but I also want to take this opportunity to have a real one-on-one on this live AMA.

Hey @Dmitriy... before I make another attempt, I gotta let you understand that GCP is deprecating the Kubernetes dashboard. So I access my secrets using kubectl CLI kubectl describe secret/<default-secret> -o yaml. How badly copied can it be?

@Job and @Dmitriy, after looking into issues on gitlab, kubernetes, and GCP online, I found out that after entering <cluster-ip>/ui in the browser it automatically resolves to <cluster-ip>/api/v1/namespaces/kube-system/…... And that's the error (at least for me). The fix is to edit the "proxy" at the end and place it here <cluster-ip>/api/v1proxy/namespaces/kube-system/services/kubernetes-dashboard/. In a few words that's how I got it to work. After I was able to copy the ca.crt and token into my gitlab configuration. I can now breathe a little -staging passed, yay!... but I can't open the staging URL 😒. I guess I gotta figure out how to access the pods in the browser. From gitlab.com I am able to make a few edits from the staging terminal, but I can't temporarily view them in the browser using the generated URL. Any pointers?

Search Hashnode