Open SohamChakraborty opened 2 months ago
Discussed this with @olemarkus in #kops-users slack channel and he feels that https://github.com/aws/amazon-eks-pod-identity-webhook/blob/master/pkg/cache/cache.go#L130 needs to check for both namespace + name
and "*" + name
EDIT: I can provide the full cluster spec after redacting sensitive parts if needed.
@kmala Do you know if there's anyone that could take a look at this? Thanks!
the changes looks small as we want to support wild card for all namespaces and don't see any issue with supporting this. let me check if any one can work on it
Awesome, thanks for checking!
I can probably do the PR as well, but it will take a few days before I can find the time.
What happened: We are trying to use wildcard namespace feature in kops that came up with this PR https://github.com/kubernetes/kops/pull/16113. Now using wildcard namespace in kops cluster manifest and then trying to create a pod that references the service account and IAM policy fails with this particular error in
pod-identity-webhook
logs:What you expected to happen: Pod to be mutated and contain the required policy/role.
How to reproduce it (as minimally and precisely as possible): in
kops
cluster manifest, we have this:Then we try to deploy an workload:
pod-identity-webhook complains with:
Anything else we need to know?: When we change the "*" to any namespace (default) everything works just fine as expected.
Environment:
aws eks describe-cluster --name <name> --query cluster.version
): 1.24.16 (not EKS)v0.4.0