Skip to content
New issue

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

Kubernetes step incorrectly requires the configmap or secret feature to be enabled #5063

Closed
mcasperson opened this issue Nov 6, 2018 · 2 comments

Comments

@mcasperson
Copy link

commented Nov 6, 2018

When creating a volume that links to a config map or volume, the validation rules required that the secret or config map features be enabled and populated even if referencing an external resource.

@octoreleasebot

This comment has been minimized.

Copy link

commented Nov 6, 2018

Release Note: Fixed validation for kubernetes volumes that referenced external configmaps or secrets

@lock

This comment has been minimized.

Copy link

commented Feb 4, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.