We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What steps did you take and what happened:
I am using the AWS Provider in SecretProviderClass to create secrets for my pods.
Initially, I thought the Secret CSI pods were not scheduled due to the taint. However, they were successfully spawned on each tainted node:
What did you expect to happen:
The Secret CSI should work even on nodes with taints.
Which provider are you using:
Environment:
kubectl version
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What steps did you take and what happened:
I am using the AWS Provider in SecretProviderClass to create secrets for my pods.
Initially, I thought the Secret CSI pods were not scheduled due to the taint. However, they were successfully spawned on each tainted node:
What did you expect to happen:
The Secret CSI should work even on nodes with taints.
Which provider are you using:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: