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 deploy containers step validation fails when volume secret references local secret #5478

Closed
MJRichardson opened this issue Apr 12, 2019 · 2 comments
Assignees
Labels
feature/kubernetes kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@MJRichardson
Copy link

When using the Deploy Kubernetes Container step with the Secret feature enabled and configured, saving the step fails with an error when adding a Secret Volume that references the secret created as part of this step.

Steps to Reproduce:

  1. Add a Deploy Kubernetes Container step.
  2. Configure the step to deploy a container.
  3. Enable the “Secret” feature.
  4. Add a Volume that is configured as “Reference the secret created as part of this step”.
  5. Add an item to the secret with a name and value.
  6. Hit save and the error message “The secret feature must not be left blank or disabled because a volume has been configured to reference it.” appears.

Reported by https://help.octopus.com/t/error-deploying-kubernetes-container-with-secret-volume/22692

@MJRichardson MJRichardson added kind/bug This issue represents a verified problem we are committed to solving feature/kubernetes labels Apr 12, 2019
@MJRichardson MJRichardson self-assigned this Apr 12, 2019
@MJRichardson MJRichardson added this to the 2019.4.3 milestone Apr 12, 2019
@MJRichardson
Copy link
Author

Release note: Resolved spurious validation failure related to secret volume on deploy k8s containers step

@lock
Copy link

lock bot commented Jul 11, 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 Jul 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature/kubernetes kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

1 participant