Hello, I am getting an error $ chmod 400 "$KUBECONFIG" chmod: : No such file or directory On the job from the Cluster Management pipelines. Kindly help. What did I miss.
Hi Oleksii, you're very welcome. Thank you for the feedback. Could you please create an issue and assign it to Cesar? For now, we have some lab instructions that could be of help to you. The pre-requisite is that you already own your domain name. The instructions show you how to set up a DNS CNAME record to point to an EKS URL. Here are two links that may be of help to you: 1) This one is a bit dated so start at step 31: gitlab.com/tech-marketing/workshops/cicd/cd-labs-instructions/-/blob/master/subchapters/create-simple-java.md 2)gitlab.com/tech-marketing/workshops/cicd/cd-labs-instructions/-/blob/master/subchapters/examples-for-setting-DNS-CNAME-record.md
@@Gitlab there is a typo after step 32 where in the word "now" is mentioned as "not" which gives a totally different meaning 😊 It reads "That's it! The EKS cluster is not all set to be used for deployments in your project."
Thanks for the very helpful video, seeing it actually work gives reassurance this migration to agents is indeed possible. Where did you get the autodevops gitlab-ci.yml file from though? Is it just something you had local to copy/paste from as couldn't find this in the templates
What will happen to the kubernetes cluster at the gitlab instance level? Will autodevops continue to work? out of the box without manipulating .gitlab-ci.yaml
Hi Alexandr! Auto DevOps should work with this setup. For more information, please refer to: about.gitlab.com/blog/2022/02/08/gitops-with-gitlab-auto-devops/
I am getting below error in - Job detect-helm2-releases $ if [ -n "$KUBE_CONTEXT" ]; then kubectl config use-context "$KUBE_CONTEXT"; fi error: no context exists with the name:"sk-myproj/demo/skdemo:k8s-agent" What am I doing wrong?
Hi Subhash, thank you for the question. From the error, it appears that the location for your agent is not correct. Please double check the path and also make sure your agent has been registered on GitLab AND deployed to your Kubernetes cluster.
Hello, I am getting an error
$ chmod 400 "$KUBECONFIG"
chmod: : No such file or directory
On the job from the Cluster Management pipelines. Kindly help. What did I miss.
nice video, so i have a question, im error with access web 404, the configurations ingress and pods its ready! that may be occurring?
I do not understand at 5:03 how the pipeline can be launched as they are not yet a working gitlab-runner, how did you bootstrap ?
Any doc/youtube for Openshift 4 equivalent?
Hey Cesar, much appreciate the video. Is it possible to provide some tutorial on how to use domain name with SSL? Thanks.
Hi Oleksii, you're very welcome. Thank you for the feedback. Could you please create an issue and assign it to Cesar? For now, we have some lab instructions that could be of help to you. The pre-requisite is that you already own your domain name. The instructions show you how to set up a DNS CNAME record to point to an EKS URL. Here are two links that may be of help to you: 1) This one is a bit dated so start at step 31: gitlab.com/tech-marketing/workshops/cicd/cd-labs-instructions/-/blob/master/subchapters/create-simple-java.md 2)gitlab.com/tech-marketing/workshops/cicd/cd-labs-instructions/-/blob/master/subchapters/examples-for-setting-DNS-CNAME-record.md
@@Gitlab there is a typo after step 32 where in the word "now" is mentioned as "not" which gives a totally different meaning 😊
It reads "That's it! The EKS cluster is not all set to be used for deployments in your project."
Thanks for the very helpful video, seeing it actually work gives reassurance this migration to agents is indeed possible. Where did you get the autodevops gitlab-ci.yml file from though? Is it just something you had local to copy/paste from as couldn't find this in the templates
fully reproduce config but get all time stuck deployment with no agents available
What will happen to the kubernetes cluster at the gitlab instance level? Will autodevops continue to work? out of the box without manipulating .gitlab-ci.yaml
Hi Alexandr! Auto DevOps should work with this setup. For more information, please refer to: about.gitlab.com/blog/2022/02/08/gitops-with-gitlab-auto-devops/
I am getting below error in - Job detect-helm2-releases
$ if [ -n "$KUBE_CONTEXT" ]; then kubectl config use-context "$KUBE_CONTEXT"; fi
error: no context exists with the name:"sk-myproj/demo/skdemo:k8s-agent"
What am I doing wrong?
Hi Subhash, thank you for the question. From the error, it appears that the location for your agent is not correct. Please double check the path and also make sure your agent has been registered on GitLab AND deployed to your Kubernetes cluster.