Thank you

thanks for suggestion. sure will do.

thanks for your input. sure will do soon

Thank you

Thank you Ravi Prakash. sure will try to creat videos on AWS interview questions

Thank you

My pleasure, keep learning

thanks for suggestion, cheers

yes pls check my playlists in the channel

same for GCP aswell, tftest.hcl, tfmock.hcl files and run will remain same irrespective of AWS/GCP/Azure simplest way i would suggest is...search github for any GCP code and add tests to it

Thanks bro for the feedback. It's iTerm2 terminal for Mac. Applied autosuggestion, syntax highlight and kubecolor on top it for kubectl colours

Great suggestion!, will do soon, thank you

Thanks, it's Audio-Technica ATR2100x-USB Cardioid Dynamic USB XLR Microphone

@@learnwithgvr Thank you

thank you

thank you

if do not specify it will consider defult namespace. if you want any specific namespace you can update your kubeconfig desired context namespace

thanks a lot

Thanks for the feedback, it was first video and listen 1.5x speed for better reach

Thank you for feedback

Thank you George

Thank you

Thank you Maheshwar...sure will continue the videos. Any new topics you are looking please message here

Yes can, logic is jere RoleId and Secret Id dual authentication, generate token

Thanks for suggestion and feedback. Sure will try to make these videos

@@learnwithgvr you must be ur teaching skill is awesome

Thanks a lot. Any suggestions/requests for making aws services videos

Thanks a lot Rahul. keep learning

Thanks Bro ..keep learning

Thanks bro

Thanks bro

Thank you, keep learning

thank you for the feedback. keep learning

thank you

thats correct, i have made detailed video on PSA kzfaq.info/get/bejne/gL99atCEuM7KoGQ.htmlsi=244KY5vBDSSp3l2o

Thank you, keep leaning

Any idea? Maybe an init job that configures the kubernetes auth in vault side?

Leverage GitOps approach

Thanks you and Yet to do

Thank you bro, keep learning

Thanks for feedback and Keep Learning

Thanks for the feedback shanti. Keep learning

Thanks

One possible way to restrict pod access in kubernetes is to use Network policies. Network policies allow you to control the traffic flow between pods based on labels and selectors. For example, you can create a network policy that only allows pods with a certain label to communicate with each other, and deny all other traffic. Hope this helps apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: access-pod1 spec: podSelector: matchLabels: app: pod1 # select pod1 ingress: - from: - podSelector: matchLabels: user: John # allow pods with user: John label --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: access-pod2 spec: podSelector: matchLabels: app: pod2 # select pod2 ingress: - from: - podSelector: matchLabels: user: James # allow pods with user: James label

Thanks you for feedback, keep learning

Thanks a lot and keep learning

Thank you bro, keep learning