I really like your content, I learned and implemented so many concepts. Hoping for shell scripting videos. You are awesome, u don’t know how many u r inspiring. ❤
For programmatic access, it's no longer available as a button there. Create the IAM user -> click on the user -> security credentials tab -> create access key Thanks for the content!
thanks so much for this, it would be great if you could please point me to a video that can help me detect the the the new container on eco to us to eco environment, more like a continuation from this video, thanks
Thank you for your video, but I get the following issue: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
Thanks for your great tutorials & quick intro to different tools Would appreciate if you can run a quick intro to istio and deploy a full deployment with istio Egress & Ingress
Thank you for suggestion, I was thinking about istio for a long time. I'll make few more about github actions and still aws load balancer controller is pending :)
Can you added the part of CICD for the ECS too? I am deploying my API on Fargate through ECS and struggle to find a way to automate the development, due to the Task Definition and Tasks and Services.
Hello Anton, My issue is: How do I implement the tagging strategy for aws multiple accounts. Such that each deployment pipeline tag release is independent of the other accounts. Dev pipeline tag release can be at 0.1.9 and Prod pipeline can be 0.1.1 this scenario looks like a single account pipeline process. In my situation, if I merge my Dev branch to Prod branch, the pipeline will take the Dev tag and does its incrementation, which I don't like
Not sure if I follow, you would want to create a single immutable artifact for service and promote it between different environments: dev -> staging -> qa -> prod (example may have different envs). In your case looks like you create different artifacts for different environments.
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
I really like your content, I learned and implemented so many concepts. Hoping for shell scripting videos. You are awesome, u don’t know how many u r inspiring. ❤
Would you recommend creating a policy, group and user via terraform and placing it in infrastructure repository?
For programmatic access, it's no longer available as a button there.
Create the IAM user -> click on the user -> security credentials tab -> create access key
Thanks for the content!
thanks, yes they've made some changes to ui
Nice, thank you for helpful videos!
Happy to help!
This video was great, but can you change up your royalty free music a few times in the video? This gets really repetitive.
thanks! i no longer use music but thanks for the feedback
how about deploying the app to your cluster as a final process ? Do you have a video for that ?
sure - ua-cam.com/video/X9R5ySkiUkc/v-deo.html
thanks so much for this, it would be great if you could please point me to a video that can help me detect the the the new container on eco to us to eco environment, more like a continuation from this video, thanks
Thanks for the feedback, well I have couple for example argocd image updater - ua-cam.com/video/cTQybeDzngU/v-deo.html
Thank you for your video, but I get the following issue:
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
Most likely node/npm version mismatch. Check versions and upgrade if necessary
How to implement caching for multi stage build here
It's been a while but maybe this can help - docs.docker.com/build/cache/backends/gha/
чтож летс криэйт ит!
k
Very helpful ! Thanks 🚀
thank you!
👉 How to Manage Secrets in Terraform - ua-cam.com/video/3N0tGKwvBdA/v-deo.html
👉 Terraform Tips & Tricks - ua-cam.com/video/7S94oUTy2z4/v-deo.html
👉 ArgoCD Tutorial - ua-cam.com/video/zGndgdGa1Tc/v-deo.html
Hey Anton!
I am facing this error:
Error: not a valid repository/tag: invalid reference format
Please help!
thank you buddy for the information, but I had some problems focusing because of the background music
thanks, i don't use bg music anymore. thanks for the feedback
Thanks for this useful video. A humble suggestion: In such tutorial videos, the less background music the better.
Thanks! Agree I don’t use it anymore
Thanks for your great tutorials & quick intro to different tools
Would appreciate if you can run a quick intro to istio and deploy a full deployment with istio Egress & Ingress
Thank you for suggestion, I was thinking about istio for a long time. I'll make few more about github actions and still aws load balancer controller is pending :)
Brown Kevin Lee Michelle Garcia Gary
?
Great tutorial! Very useful :)
Thanks a lot!
like always the best guides videos in youtube
thank you!!
Really good, but crazy speed. Not my taste
Thank, noted!
Hope to see your new video. You always update the trend on the market ! Awesome content
Appreciate it!
Too clear mate thanks
❤️
Thanks, works like a charm!
You're welcome!
Perfect
Thank you!!
Awesome video Sir
Thank you!
❤ excellent. Thanks 🙏
Can you added the part of CICD for the ECS too? I am deploying my API on Fargate through ECS and struggle to find a way to automate the development, due to the Task Definition and Tasks and Services.
I'll see what I can do in the future, EKS is way more popular than AWS native ECS.
Hello Anton,
My issue is: How do I implement the tagging strategy for aws multiple accounts. Such that each deployment pipeline tag release is independent of the other accounts. Dev pipeline tag release can be at 0.1.9 and Prod pipeline can be 0.1.1
this scenario looks like a single account pipeline process. In my situation, if I merge my Dev branch to Prod branch, the pipeline will take the Dev tag and does its incrementation, which I don't like
Not sure if I follow, you would want to create a single immutable artifact for service and promote it between different environments: dev -> staging -> qa -> prod (example may have different envs). In your case looks like you create different artifacts for different environments.
I just get an permission denied at the git clone
it's public repo, try https clone..
show 10
?
Excellent tutorial thank you!
Welcome!
спс. Работаю девопсом и мне помогло. Скину на кофе завтра
Spasibo :)