Michael Schmidt
Michael Schmidt
We still use kube2iam because IAM roles for service accounts require exposure of unauthenticated public json oauth provider data in an S3 bucket or a server, and our organization policies...
As an additional piece of this, it took a long time to debug what was happening due to the silent error catch in https://github.com/jcmoraisjr/haproxy-ingress/blob/4862b877a9fb34069478a31ec314fc42955752ad/pkg/converters/ingress/annotations/backend.go#L184-L187, that doesn't log when it gets...