You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.
I am trying to configure KES with "EKS Service Account credentials", as explained at the end of this link:https://external-secrets.io/provider-aws-secrets-manager/
But it is not working. Has anyone made this configuration working? Am I missing something? Do I need to change anything in the KES k8s deployment to have the IAM Role for ServiceAccount working?
If I follow the example: apiVersion: external-secrets.io/v1alpha1 kind: SecretStore metadata: name: secretstore-sample spec: provider: aws: service: SecretsManager auth: jwt: serviceAccountRef: name: my-serviceaccount
I get the following error: error: error validating "SecretStore.yaml": error validating data: ValidationError(SecretStore.spec.provider.aws): missing required field "region" in io.external-secrets.v1alpha1.SecretStore.spec.provider.aws; if you choose to ignore these errors, turn validation off with --validate=false
If I include the Region: apiVersion: external-secrets.io/v1alpha1 kind: SecretStore metadata: name: secretstore-sample spec: provider: aws: service: SecretsManager region: <REGION> auth: jwt: serviceAccountRef: name: my-serviceaccount
I get this error: The SecretStore "test-secretstore" is invalid: spec.provider.aws.auth.secretRef: Required value
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am trying to configure KES with "EKS Service Account credentials", as explained at the end of this link:https://external-secrets.io/provider-aws-secrets-manager/
But it is not working. Has anyone made this configuration working? Am I missing something? Do I need to change anything in the KES k8s deployment to have the IAM Role for ServiceAccount working?
If I follow the example:
apiVersion: external-secrets.io/v1alpha1 kind: SecretStore metadata: name: secretstore-sample spec: provider: aws: service: SecretsManager auth: jwt: serviceAccountRef: name: my-serviceaccount
I get the following error:
error: error validating "SecretStore.yaml": error validating data: ValidationError(SecretStore.spec.provider.aws): missing required field "region" in io.external-secrets.v1alpha1.SecretStore.spec.provider.aws; if you choose to ignore these errors, turn validation off with --validate=false
If I include the Region:
apiVersion: external-secrets.io/v1alpha1 kind: SecretStore metadata: name: secretstore-sample spec: provider: aws: service: SecretsManager region: <REGION> auth: jwt: serviceAccountRef: name: my-serviceaccount
I get this error:
The SecretStore "test-secretstore" is invalid: spec.provider.aws.auth.secretRef: Required value
Beta Was this translation helpful? Give feedback.
All reactions