Secure access to GKE workloads with Workload Identity

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 ต.ค. 2024

ความคิดเห็น • 7

  • @googlecloudtech
    @googlecloudtech  2 ปีที่แล้ว +1

    What do you think about the Workload Identity tool for GKE? Let us know in the comments below and don’t forget to like and subscribe for the latest in GKE Essentials! → goo.gle/GoogleCloudTech

  • @AlejandroBiancucci
    @AlejandroBiancucci 3 หลายเดือนก่อน

    Thanks for simplifying these topics. They can be really confusing at times ñ. This helps.

  • @patricknelson
    @patricknelson 2 ปีที่แล้ว +2

    I’ve been getting into Workload Identity more lately. One thing I’ve really been wondering about is if it’s possible to differentiate between the service account performing image pulling vs. the service account actually used to execute the workload (i.e. at the pod level). Is that possible? You can use imagePullSecrets but that’s precisely what I’m trying to avoid using, and I just want a SA who’s sole purpose is just for pulling images from a separate project. 🤦‍♂️

  • @thecloudcareers
    @thecloudcareers 2 ปีที่แล้ว

    This is one of best feature.
    Which avoids rotation of keys

  • @dheer211
    @dheer211 2 ปีที่แล้ว

    Great video thank you

  • @AleksanderSumowski
    @AleksanderSumowski 10 วันที่ผ่านมา

    The speaker says multiple times on her own that the topic is confusing, then ends with statement that she is confident the audience will understand the topic. Please don't it

  • @aravindpoojari68
    @aravindpoojari68 2 ปีที่แล้ว

    All good but wasted first 3 minutes explaining IAM.