GitLab CI/CD: Build a Complete Pipeline from Scratch!
HTML-код
- Опубликовано: 2 окт 2024
- Link to the repository mentioned in the video: gitlab.com/abo...
Relevant Udemy courses (including discount coupons):
Helm: www.udemy.com/...
DevOps projects on Kubernetes: www.udemy.com/...
Argo CD and GitOps: www.udemy.com/...
Master CI/CD pipelines by creating a real-world project on GitLab CI. Identify and solve modern DevOps challenges. Grasp the essentials in the first few minutes, then follow the in-depth lab to gain the maximum benefit.
If you have any questions about the video content or if the discount coupon expires, please leave a comment 👇
awesome tutorial..keep posting .full support
One of the greatest videos I have seen in this topic , thanks for the clear explanation.
Could you please make a video about deployment strategies (blue/green , canari) and how to apply them in a real world project
Yes, that’s on the road map
343 profit
I assume if the production namespace is in a production EKS cluster you would variablize the CLUSTER_NAME so that when production is ran manually you would be able to set the cluster name. Is this correct?
how to register eks cluster into gitlab, how to add environmental variables and how to deploy a applications into different namespaces.
The helm course was purchased and passed a year ago. Thanks of that kind of videos as mastering a single tool doesn't help a lot in understanding how these things are working together.
good information !!! Thanks a lot !!!
wow
into the point, great job keep on 👏
You look like an AI model..
Is that good or bad 😀?
Lol,
I thought I was the only one seeing that
@@AhmedElfakharany I purchased one of your courses "Helm - The Kubernetes Package Manager hands-on course" and I'm working with my team to try to refine our pipelines to try to do the right thing. I have question thought about helm versioning and I'm not sure if you have any course on this matter so That could purchase. Some questions:
1) Should we version our helm charts for every deployments?
2) Also, where should we store our charts? At the moment, charts live in the microservice repo along with the source code i.e OrderAPI repo includes the chart related manifest files. What is your opinion.
Some context. We are hoping to move towards pull based deployments 'eventually' (using ArgoCD).
As a team, we are looking to purchase any course you might suggest for us.