GitLab CI/CD: Architecting, Deploying, and Optimizing Pipelines

Kubernetes
#1

Hi. I am going through the course “ GitLab CI/CD: Architecting, Deploying, and Optimizing Pipelines” and I am also doing all the steps in parallel in my gitlab as well.

At the module “Job - Configuring Kubeconfig file” there is this kubeconfig file show in the video.
I am not able to continue to continue with the gitlab jobs as I do not have this exact kubeconfig file from the course.
Dear Kodekloud could you provide this file to me so I can add it and run the job myself in my gitlab too?Without this the job fails.

kubeconfig
kubeconfig1081×536 105 KB

#2

The kubeconfig should be available in the Lab env as ~/.kube/config.

You can refer to the notes here for more info on how to use it in CI.

#3

I am not talking about the Lab env. (Btw I tried that by using the file from the lab and is not working as it is different).
I am talking about the kubeconfig file from the video, from the demo presentation. That one is different.

#4

You don’t need that exact file. If you’re deploying this on your own systems, you need a kubeconfig file that points to a K8s cluster that is accessible to your gitlab install. Not knowing what hardware configuration you have, we can’t say what that file contains. But the key point is that the the kubeconfig file needs to have a K8s endpoint for kube-apiserver that can be accessed from gitlab.

So how are your servers set up?

#5

Is the same way as in the course. From the beginning of the gitlab course I did all the steps as shown in the video ( Not from the lab). Basically at the beginning of the course I cloned the repository of the trainer in my gitlab. But now I miss the kubeconfig file. So I need the kubeconfig file from the video in order to deploy the K8s clusfer as shown in the video.

#6

If I understand what you mean, then you’re using a free Gitlab account for this. If so, then there are two ways you can get access to a K8s cluster:

  • You can use a cluster that’s available on the public internet (say, an EKS cluster from AWS)
  • You can create a local cluster inside of your CI/CD script using something like kind to create the cluster.

For the kubeconfig file, you’d use a kubeconfig that points to that cluster.