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
Running a health check in our Octopus Deploy cloud server with our deployment target configured with the Octopus Agent in-cluster. The health check pod is created on the target cluster successfully but will remain in Pending status forever as it is missing the Pod annotation that allows GCS Fuse to be used.
This would happen in any environment where a specific Pod annotation would be required.
Reproduction
Deploy an Octopus Tentacle to a Google Kubernetes Engine environment where you are using the GCS Fuse driver as your Persistent Volume option. Run a health check in your deployment target (this sounds like it should also affect any Script Pod).
Error and Stacktrace
[POD EVENT] FailedMount | MountVolume.SetUp failed forvolume "octopus-agent-octopus-deploy-pvc" : rpc error: code = FailedPrecondition desc = failed to find the sidecar containerin Pod spec (Count: 9)
The Kubernetes Pod 'octopus-script-slpfqrh5k2l2ju2gqfseg' is in the 'Pending' phase
More Information
Helm chart support for using custom Persistent Volumes is pending this Pull Request here: OctopusDeploy/helm-charts#381
Workaround
Potentially deploying our own MutatingWebhook could solve the issue by injecting the annotation but this feels like a useful thing for OD to solve in general.
The text was updated successfully, but these errors were encountered:
Team
What happened?
Running a health check in our Octopus Deploy cloud server with our deployment target configured with the Octopus Agent in-cluster. The health check pod is created on the target cluster successfully but will remain in
Pending
status forever as it is missing the Pod annotation that allows GCS Fuse to be used.This would happen in any environment where a specific Pod annotation would be required.
Reproduction
Deploy an Octopus Tentacle to a Google Kubernetes Engine environment where you are using the GCS Fuse driver as your Persistent Volume option. Run a health check in your deployment target (this sounds like it should also affect any Script Pod).
Error and Stacktrace
More Information
Helm chart support for using custom Persistent Volumes is pending this Pull Request here: OctopusDeploy/helm-charts#381
Workaround
Potentially deploying our own MutatingWebhook could solve the issue by injecting the annotation but this feels like a useful thing for OD to solve in general.
The text was updated successfully, but these errors were encountered: