I think many People Don't know about your channel. Your conten is not only Best But complete. There are lot of Vlog on CI/CD but all incomplete. Thank you very much . At least in Interview i can explain this.
Hey man, i was just searching how CICD pipeline works and i got you. It was really good enough to understand the topic. I have a request to you, we would love to and appreciate if possible for you to make a video for complete CI/CD project from scratch. Thanks.....
Very useful , Nicely explain with attractive design diagram. Thank you very much. I would like to request and looking forward to see the video on Config repo which here you mention once CI completion then Config repo will kick off to deployment. Thank you very much again
Thanks for providing the design. Could you please make videos on detail implementation? Also please let me know how an Integration testing should be implemented. I have an urgent requirement on integration testing. I have already bookmarked this playlist
Great job and the diagram really helps.CI refers to Continuous integration and CD refers to Continuous deployment/delivery, I guess you mistakenly used the "CICD" term as Continuous integration and the Deployment pipeline as CD.
my doubts for canary deployment - what would happen if there are different apps across multiple node? - in case of any issues are we going to rollback the whole deployment? - what if multiple teams have their changes in the same deployment? we can't rollback others changes for our failure.
He didn't go a lot into detail there. I think you would roll back the whole deployment and "all" the changes. However, this would normally be done in a microservice environment where you don't have combined changes of multiple teams and only very small incremental changes instead of huge release packages.
@@MikeZadik deployments generally are multi app dependent. like at least UI changes also with backend changes. if we follow canary deployment, we will have to rollback those as well. great video though. I might be missing few things. need to read more on this.
Also consider you could use something like launchdarkly to feature flag changes and turn them on gradually after the release is completed and roll back the feature if something breaks
What if you have two app repos one for frontend and one for backend and you’re trying to accomplish this, how would you deploy both at the same time? Ensuring the new frontend can hit the new backend.
You would deploy your new backend first, then you would deploy the front-end. New backend should be compatible with the old front-end, or you would have to just run two versions of it during the transition
It's actually CI/CD&CD. Continuous Delivery & continuous deployment. Delivery just means making the artifacts available, deployment means actually deploying to those environments
i don’t like the idea of images going to a single repository I think production environment should have a separate image repository if an image does not pass QA or pre-prod you don’t want that cluttering your production repository
First of all, LOVE the content your are providing. I have already learned so much. I have a question regarding your setup though. I have implemented your Windows setup from this video ruclips.net/video/XBU_6OSlgyI/видео.html Now I have a bit of a challenge when accessing resources behind VPN. My Corp. is using Split tun. OVPN. I am using windows client and everything, WSL included, works great. We also work with a client that forces us to use their Fortinet full tunnel VPN. When I install the client on the Windows layer, my WSL is unable to connect to the internet. I am thinking about spinning up a docker and install the VPN client inside. Not sure if I should install my tools there too, or "somehow" use it as a proxy for the WSL. Any ideas, what would be the best approach to solve this issue?
Hmm I'm actually not sure what the best solution for you would be. I found this, there seems to be issues with WSL2 when using Full tunnel VPNs so you are not alone.. github.com/microsoft/WSL/issues/4277
You are completely right. I feel like an idiot for not doing this. Here's a link to a playlist I just created ruclips.net/p/PLnFWJCugpwfwQgjlSg_-csiJbpBIze2qa Will add it to the video description and create/maintain more playlists in the future. Thanks again for the suggestion!
Playlist: ruclips.net/p/PLnFWJCugpwfwQgjlSg_-csiJbpBIze2qa
View my diagram: app.eraser.io/workspace/d0mh9JjnYl2TWetXPsXV
It would be good if you can provide a complete yaml script as per your diagram
I think many People Don't know about your channel. Your conten is not only Best But complete. There are lot of Vlog on CI/CD but all incomplete. Thank you very much . At least in Interview i can explain this.
I took a DevOps course and your videos helping very much to understand the subject.
I enjoy the simplicity of your explanation of CICD pipeline projects.
the channel is a DevOps mine, thanks so much for helping those in need.. you'll be rewarded some day, both here on earth and in the after life
Why do you recommend to have a dedicated repo for your configuration? What about having a /kubernetes folder in your application repository instead?
Is it possible you create a video putting this theory and architecture into practice using Jenkins or another automation tool?
Did you find any answers ?
Same here
Same here
It would be good if you can provide a complete yaml script as per your diagram
I'm happy I discovered your channel. This is great stuff!
Hey man, i was just searching how CICD pipeline works and i got you. It was really good enough to understand the topic. I have a request to you, we would love to and appreciate if possible for you to make a video for complete CI/CD project from scratch. Thanks.....
Simple, yet detailed. i wish i can like this video more than once. you've definitely earn a sub
Very useful , Nicely explain with attractive design diagram. Thank you very much. I would like to request and looking forward to see the video on Config repo which here you mention once CI completion then Config repo will kick off to deployment. Thank you very much again
I love your videos man, very interesting. Thank you for sharing your knowledge with us.
Great tutorial as always
amazing explanation, looking forward for more related content!
Thanks for providing the design. Could you please make videos on detail implementation? Also please let me know how an Integration testing should be implemented. I have an urgent requirement on integration testing. I have already bookmarked this playlist
Very interesting explanation, keep it up
I’m all about the version tagging stray 😎 I got some great content for ya already put together.
amazing content man! thank you for sharing!
My CS prof spent 2 weeks on this stuff. U did it in 10 min 😂
Thank you so much for this info! 😊
great tutorial!!
best video and thank you for that
Commenting for Better Reach
Great job and the diagram really helps.CI refers to Continuous integration and CD refers to Continuous deployment/delivery, I guess you mistakenly used the "CICD" term as Continuous integration and the Deployment pipeline as CD.
You had a video that showed this solved with different git branches. Did you delete that?
my doubts for canary deployment
- what would happen if there are different apps across multiple node?
- in case of any issues are we going to rollback the whole deployment?
- what if multiple teams have their changes in the same deployment? we can't rollback others changes for our failure.
He didn't go a lot into detail there.
I think you would roll back the whole deployment and "all" the changes. However, this would normally be done in a microservice environment where you don't have combined changes of multiple teams and only very small incremental changes instead of huge release packages.
@@MikeZadik deployments generally are multi app dependent. like at least UI changes also with backend changes. if we follow canary deployment, we will have to rollback those as well. great video though. I might be missing few things. need to read more on this.
Also consider you could use something like launchdarkly to feature flag changes and turn them on gradually after the release is completed and roll back the feature if something breaks
How do you handle multiple deployments being integrated and deployed at very short intervals? 😅
I use a combination of ArgoCD + ArgoRollouts for that. I have videos on both if you are interested
Where does config management and IaC fit into this CI/CD pipeline
unit tests are part of branch protection - must be run just after liniting
and there is no reason to package them into container image
What if you have two app repos one for frontend and one for backend and you’re trying to accomplish this, how would you deploy both at the same time? Ensuring the new frontend can hit the new backend.
You would deploy your new backend first, then you would deploy the front-end. New backend should be compatible with the old front-end, or you would have to just run two versions of it during the transition
Great!
Hi, I am confused why is the "Deployment Pipeline" not part of the "CD" in "CI/CD" pipeline?
It's actually CI/CD&CD. Continuous Delivery & continuous deployment. Delivery just means making the artifacts available, deployment means actually deploying to those environments
@@DevOpsJourney Sure that makes sense. Thanks for the excellent videos.
Why have a separate repo when you could have it all in the same repo and have the workflows separate?
Teams responsible should be different hence better to have separate repos as best practices
best
i don’t like the idea of images going to a single repository I think production environment should have a separate image repository if an image does not pass QA or pre-prod you don’t want that cluttering your production repository
First of all, LOVE the content your are providing. I have already learned so much.
I have a question regarding your setup though. I have implemented your Windows setup from this video ruclips.net/video/XBU_6OSlgyI/видео.html
Now I have a bit of a challenge when accessing resources behind VPN. My Corp. is using Split tun. OVPN. I am using windows client and everything, WSL included, works great.
We also work with a client that forces us to use their Fortinet full tunnel VPN. When I install the client on the Windows layer, my WSL is unable to connect to the internet.
I am thinking about spinning up a docker and install the VPN client inside. Not sure if I should install my tools there too, or "somehow" use it as a proxy for the WSL.
Any ideas, what would be the best approach to solve this issue?
Hmm I'm actually not sure what the best solution for you would be. I found this, there seems to be issues with WSL2 when using Full tunnel VPNs so you are not alone.. github.com/microsoft/WSL/issues/4277
Put some effort into making playlists.
I have not found one and no, I will not be scrolling to your previous video. Bye
You are completely right. I feel like an idiot for not doing this. Here's a link to a playlist I just created ruclips.net/p/PLnFWJCugpwfwQgjlSg_-csiJbpBIze2qa
Will add it to the video description and create/maintain more playlists in the future. Thanks again for the suggestion!
Thanks for this presentation!