Workload Identity (OIDC) for AKS

Поділитися
Вставка
  • Опубліковано 26 лис 2024

КОМЕНТАРІ • 8

  • @jakepyrett1715
    @jakepyrett1715 10 місяців тому

    Thanks for video. Was excellent

  • @SwatiKhandelwal-lu4nt
    @SwatiKhandelwal-lu4nt Рік тому +1

    It is asking for many parameter for env which include federated file, how did you not get that value?

  • @jamalashraf7957
    @jamalashraf7957 2 роки тому +1

    I am getting this error --> F1206 09:02:03.164100 1 main.go:15] KEYVAULT_URL environment variable is not set

  • @smartaquarius2021
    @smartaquarius2021 Рік тому

    Enable workload identity feature is in preview and not prod ready yet. Can any share the video to setup same using open source project.

  • @xville8642
    @xville8642 10 місяців тому

    can you give the managed identity RBAC roles on the keyvault instead of using Access Policies? ?

    • @adamsebetich9290
      @adamsebetich9290 8 місяців тому

      yes, that is exactly right. RBAC on key vault is a bit less granular than access policies, but i believe azure wants to move towards rbac for all things anyways

  • @jamalashraf7957
    @jamalashraf7957 2 роки тому

    Great VIDEO! sir would you please tell me that how can i set these env variables in Azure CLI? I am stuck here

  • @raghur5678
    @raghur5678 Рік тому

    i have created workload-identity-sa like this
    apiVersion: v1
    kind: ServiceAccount
    metadata:
    annotations:
    azure.workload.identity: XXX-XXXX-XXX-XXXX
    labels:
    azure.workload.identity/use: "true"
    name: workload-identity-sa
    namespace: backend-services
    via yaml from kubernetes ,but its not created
    and after running this. i am deploying pods into Cluster getting error like Azure.Identity.AuthenticationFailedException: ClientAssertionCredential authentication failed: AADSTS70021: No matching federated identity record found for presented assertion.