External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
Kubernetes requires certain names (at least metadata.name and label names/values) to be <64 characters long, to comply with DNS limits. The helm chart can generate names longer than this, in spite of attempting not to.
This bit me when installing the helm chart with AWS CDK, which is notorious for generating long resource names. I ended up with failures like this:
Error: Service "itlabcirunnerstackclusterchartexternalsecrets449a9ff5-external-webhook" is invalid: metadata.name: Invalid value: "itlabcirunnerstackclusterchartexternalsecrets449a9ff5-external-webhook": must be no more than 63 characters'
This is easily fixed by parameterizing the helm chart installation with a shorter non-default full name, but it might be worth making the defaults work in all cases.
Kubernetes requires certain names (at least
metadata.name
and label names/values) to be <64 characters long, to comply with DNS limits. The helm chart can generate names longer than this, in spite of attempting not to.The default value of
external-secrets.fullname
is properly truncated: https://github.com/external-secrets/external-secrets/blob/fe3c78d2af1202331df6bfbc7237f5f310dd5c21/deploy/charts/external-secrets/templates/_helpers.tpl#L8-L24But it is then appended to in length-sensitive contexts without further truncation: https://github.com/external-secrets/external-secrets/blob/fe3c78d2af1202331df6bfbc7237f5f310dd5c21/deploy/charts/external-secrets/templates/webhook-deployment.yaml#L5
This bit me when installing the helm chart with AWS CDK, which is notorious for generating long resource names. I ended up with failures like this:
This is easily fixed by parameterizing the helm chart installation with a shorter non-default full name, but it might be worth making the defaults work in all cases.