Hi Malek, thank you for your lessons. You have a super didactic, and you don't edit the video in the errors, you face all the steps. You deserve much more than 5 coffees.
Great Video. Looking to see if an application like JIRA has a license key when launching it. How can the license key be added into the values.yaml file?
Great video! I am stuck at one part. It's probably obvious, but the secret file is a dockerconfigjson type. The .dockerconfigjson base64 string returns an illage base64 data input. Do we need to create our own json file for gitlab or docker here? @38:45
For secret that uses dockerconfigjson, you can just once type in your terminal: docker login registry.gitlab.com then ask you username and password and will show you login success. so now if you check : ls ".docker/config.json " it will show you the config.json file is there with the following content: { "auths": { "registry.gitlab.com": {} }, "credsStore": "wincred.exe" } so for create secret you can use this config.json file like below: kubectl create secret docker-registry my-secret --from-file=.dockerconfigjson=config.json --dry-run=client -o yaml > secret.yaml also you can reach me by email to discuss about it: howtoskillsvid@gmail.com
Thank you so much, this was the answer on my last question 🙂your explanations are consistently excellent, always making complex topics easy to understand...So if I make any changes to the deployments.yaml I have to push that again to the registry or not? if i want to update the YAML files inside the template folder... that would be also helpful if we know that... thanks again
Hi sir, thank you for your videos. It is helpful to me. Can you do me a favour . Can you do one project below the content 1) Can you take a java source code. 2) can you do the ci/cd using Gitlab . Can you explore the monitoring toll like prometiues,grafana.. can you elaborate ci/ cd stages like build, sonar qube, image repo, deploy kubernetes cluster. Can you do one video for us above the required content
Hello Thanks for yr consideration I am preparing a video, from scratch, build an app by node js then deploy it to K8S manually and also by CI/CD, I will try to add Monitoring to it. it took my time. because i had too re-view my coding after years :)
Your content is really good, but that bell and clicking sound meant I just couldn't watch more than 5 minutes. Thanks for making the content, but I would urge you to consider not using so many like and subscribe reminders I really struggled to concentrate on your excellent content.
What when I have more repositories(each for one microservice)? Do I have to configure gitlab agent on k8s for each of them? I created 2 repositories, first one k8s-gitlab-connection where Kubernetes cluster is configured in Gitlab and agent was installed on k8s cluster. There is connection, it works. But I have an another repository microservice-1-repository, when I configured the pipeline I'm getting "error: no context exists with the name: xxx" for this command "kubectl config use-context: xxx". I guess this happeing because I don't have Kubernetes cluster integration for this specific project. But I don't want to do it for each repository...
I found an answer, I changed config.yaml by adding ci_access: # This agent is accessible from CI jobs in projects in these groups groups: - id: gitlab/repository/group then all my miscroservices can see k8s connections! great content! thx!!!!
I did same setup I have created seperate repo for the girlab-agent to k8s cluster and when I try to run the pipeline agent will connect to the cluster and I'm getting kubect pods details But when I created pipeline and in another repo I'm not able to connect cluster?
Thank you for the the video and for the great content. I am getting an error when deploying the app manually on my k8s cluster. my pod status is "ErrImagePull". Do I need to use another image besides the one I deployed in the gitlab container registry?
When you get "ErrImagePull", you have to check the logs ok K8s. please type: #kubectl describe pod and see why you get this error. if it is related to authentication do: #docker login registry.gitlab.com Then ask enter username and token. if login successful try to manually create your pod and in this time should be OK
Thank you so much. I tried to implement the same usecase. However, it is only working when configuring my container registry, helm chart registry, kubernetes connection operator in one Gitlab project. If I split, I am getting "error: no context exists with the name:". Not sure how you managed to make it work in three different project. Appreciate your help in this case.
Thank you so much for your consideration: 1- create 1st repo for connection between your gitlab and K8s and also test it via CI/CD 2- Create 2ed repo for your Data/Helm chart, etc. Then allow it access to Tunnel between 1st repo and k8s by allowing it in config.yaml EX: ci_access: projects: - id: d6245/helm_project You can reach me out by email: howtoskillsvid@gmail.com
Hi Malek, thank you for your lessons. You have a super didactic, and you don't edit the video in the errors, you face all the steps.
You deserve much more than 5 coffees.
Thank you so much
Great Tutorial - with some hints from the comments and some research its now working and should be a good base for bigger projects... 👍👊🙂
Thanks
Good job, i m ready for job interwiew now
finger cross
excellent! thank you
Great Job
Great video, THANK YOU!
Thank you
you could use helm show chart to extract the chart data :)
Great Video. Looking to see if an application like JIRA has a license key when launching it. How can the license key be added into the values.yaml file?
Great Video Sir! Can you please share how to install the runner as well! As it is not included in the video! Thank You! :)
Hello Rohan
I have a Video about it: th-cam.com/video/6BlsKlhOhDE/w-d-xo.html
Great video! I am stuck at one part. It's probably obvious, but the secret file is a dockerconfigjson type. The .dockerconfigjson base64 string returns an illage base64 data input. Do we need to create our own json file for gitlab or docker here? @38:45
For secret that uses dockerconfigjson, you can just once type in your terminal:
docker login registry.gitlab.com
then ask you username and password and will show you login success.
so now if you check :
ls ".docker/config.json " it will show you the config.json file is there with the following content:
{
"auths": {
"registry.gitlab.com": {}
},
"credsStore": "wincred.exe"
}
so for create secret you can use this config.json file like below:
kubectl create secret docker-registry my-secret --from-file=.dockerconfigjson=config.json --dry-run=client -o yaml > secret.yaml
also you can reach me by email to discuss about it: howtoskillsvid@gmail.com
Thank you so much, this was the answer on my last question 🙂your explanations are consistently excellent, always making complex topics easy to understand...So if I make any changes to the deployments.yaml I have to push that again to the registry or not? if i want to update the YAML files inside the template folder... that would be also helpful if we know that... thanks again
Thank you
Hi sir, thank you for your videos. It is helpful to me. Can you do me a favour . Can you do one project below the content 1) Can you take a java source code.
2) can you do the ci/cd using Gitlab . Can you explore the monitoring toll like prometiues,grafana.. can you elaborate ci/ cd stages like build, sonar qube, image repo, deploy kubernetes cluster. Can you do one video for us above the required content
Hello Thanks for yr consideration
I am preparing a video, from scratch, build an app by node js then deploy it to K8S manually and also by CI/CD, I will try to add Monitoring to it. it took my time. because i had too re-view my coding after years :)
Your content is really good, but that bell and clicking sound meant I just couldn't watch more than 5 minutes. Thanks for making the content, but I would urge you to consider not using so many like and subscribe reminders I really struggled to concentrate on your excellent content.
What when I have more repositories(each for one microservice)? Do I have to configure gitlab agent on k8s for each of them? I created 2 repositories, first one k8s-gitlab-connection where Kubernetes cluster is configured in Gitlab and agent was installed on k8s cluster. There is connection, it works. But I have an another repository microservice-1-repository, when I configured the pipeline I'm getting "error: no context exists with the name: xxx" for this command "kubectl config use-context: xxx". I guess this happeing because I don't have Kubernetes cluster integration for this specific project. But I don't want to do it for each repository...
I found an answer, I changed config.yaml by adding
ci_access:
# This agent is accessible from CI jobs in projects in these groups
groups:
- id: gitlab/repository/group
then all my miscroservices can see k8s connections!
great content! thx!!!!
Really nice presentation.
Do you mind sharing your git? It would be so useful.
Thank you
I did same setup I have created seperate repo for the girlab-agent to k8s cluster and when I try to run the pipeline agent will connect to the cluster and I'm getting kubect pods details
But when I created pipeline and in another repo I'm not able to connect cluster?
hi sir, how about the secret?
Thank you for the the video and for the great content. I am getting an error when deploying the app manually on my k8s cluster. my pod status is "ErrImagePull". Do I need to use another image besides the one I deployed in the gitlab container registry?
When you get "ErrImagePull", you have to check the logs ok K8s. please type:
#kubectl describe pod
and see why you get this error.
if it is related to authentication do:
#docker login registry.gitlab.com
Then ask enter username and token. if login successful try to manually create your pod and in this time should be OK
Thank you so much. I tried to implement the same usecase. However, it is only working when configuring my container registry, helm chart registry, kubernetes connection operator in one Gitlab project. If I split, I am getting "error: no context exists with the name:". Not sure how you managed to make it work in three different project. Appreciate your help in this case.
Thank you so much for your consideration:
1- create 1st repo for connection between your gitlab and K8s and also test it via CI/CD
2- Create 2ed repo for your Data/Helm chart, etc. Then allow it access to Tunnel between 1st repo and k8s by allowing it in config.yaml
EX:
ci_access:
projects:
- id: d6245/helm_project
You can reach me out by email:
howtoskillsvid@gmail.com
hi, have you a repo for this demo ? regards
github.com/mkaraminejad/cicd_pipeline