Comments (10)
I was facing same issue, for me this worked: #30 (comment)
So probably you can try to install driver with these values:
helm upgrade --install csi-secrets-store \
--namespace kube-system secrets-store-csi-driver/secrets-store-csi-driver \
--set grpcSupportedProviders="aws" --set syncSecret.enabled="true"
from secrets-store-csi-driver-provider-aws.
Thanks @shapirov103 and @mehowthe that was in fact the issue for me as well. Note, the secret only "syncs" with k8s secrets after applying the pod/deployment/etc that references it with secretKeyRef
. I was confused at first why it wasn't showing up in kubectl get secrets
after applying the SecretProviderClass
by itself.
from secrets-store-csi-driver-provider-aws.
Same issue here, trying to use secret sync feature:
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
name: argo-aws-secrets
spec:
provider: aws
secretObjects:
- secretName: bootstrap-repo-secret-sync
type: Opaque
labels:
"argocd.argoproj.io/secret-type": "repository"
data:
- objectName: github-ssp-ssh
key: sshPrivateKey
- objectName: github-ssp-ssh
key: url
parameters:
objects: |
- objectName: "github-ssp-ssh"
objectType: "secretsmanager"
The behavior is exactly as described in the issue: env reference fails, however volume is mounted successfully when kubernetes secret is not referenced. Secret is not created.
On EKS version 1.19:
AWS provider image: public.ecr.aws/aws-secrets-manager/secrets-store-csi-driver-provider-aws:1.0.r1-10-g1942553-2021.06.04.00.07-linux-amd64
CSI Driver image: k8s.gcr.io/csi-secrets-store/driver:v0.0.23
from secrets-store-csi-driver-provider-aws.
Leaving syncSecret.enabled = false
is considered a best practice as per the docs.
from secrets-store-csi-driver-provider-aws.
Same issue here. There appears to be an issue with SecretsManagerSync
-- i.e. this test is not passing: https://github.com/aws/secrets-store-csi-driver-provider-aws/blob/main/tests/aws.bats#L136
from secrets-store-csi-driver-provider-aws.
@mehowthe thank you and confirmed, the issue was due to the helm chart value for sync secret was not set. Did not expect the behavior to be "opt-in", however, it is marked as optional, so works as designed.
from secrets-store-csi-driver-provider-aws.
Adding --set grpcSupportedProviders="aws" --set syncSecret.enabled="true"
works a treat. It creates the Environment Variable.
However once the secret value is rotated in AWS Secrets Manager, only the file is updated and not the Environment value.
from secrets-store-csi-driver-provider-aws.
@askulkarni2 the docs clearly states - if you don't need it.
from secrets-store-csi-driver-provider-aws.
Adding
--set grpcSupportedProviders="aws" --set syncSecret.enabled="true"
works a treat. It creates the Environment Variable. However, once the secret value is rotated in AWS Secrets Manager, only the file is updated and not the Environment value.
Even I noticed the same behavior, I had to drop the secret object & roll restart of pods for the new value to show up as ENV. Is there any fix for this?
from secrets-store-csi-driver-provider-aws.
This is indented behavior of the Secret Store Driver, closing.
from secrets-store-csi-driver-provider-aws.
Related Issues (20)
- When adding nodeSelector and tolerations to schedule onto a specific node, secrets can no longer be fetched. HOT 3
- Pod Identity Association not recognised by secrets store CSI driver HOT 21
- [Question] Inside .yaml, there is a way to retrieve all aws secrets without pass keys? HOT 1
- Unable to mount secret, "Failed fetching secret <secretName>: RequestCanceled: request context canceled" HOT 1
- Expose Additional Security Context Settings in Helm Chart HOT 1
- Is it possible to use this outside of EKS? HOT 3
- Allow setting `driver-writes-secrets` argument via Helm values HOT 1
- Please consider changing the object parameter format. HOT 2
- AWS provider pod failing with "panic: runtime error: invalid memory address or nil pointer dereference" HOT 2
- Provider socket does not exist if provider pod starts before driver pod HOT 2
- Wait(n=1) would exceed context deadline HOT 1
- Secret access cross account without resource based policy HOT 1
- Cross account secret access HOT 1
- Request support for adding custom CA certs to helm chart HOT 1
- Error with affinity HOT 7
- Support of Access Management Roles Anywhere HOT 2
- Consider adding a changelog or useful notes to Github releases
- Respect Audience Annotation
- secrets does not working on mysql-pods
- not creating k8s secrets
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from secrets-store-csi-driver-provider-aws.