Open manno opened 3 years ago
Describe the bug
Only changing the image, does not create a new bpm secret, so the qsts is not updated.
As a workaround, one could add a label to the env.bosh.agent.labels like the kubecf release does.
env.bosh.agent.labels
To Reproduce
After installing kubecf 2.7.12 use upgrade to modify only the image:
helm upgrade kubecf -n kubecf --values values.yaml kubecf-v2.7.12.tgz --set 'operations.custom={uaa-dev}'
Expected behavior
The pods should restart with the correct image.
See discussion on Slack: https://cloudfoundry.slack.com/archives/C1BQKKNP4/p1612893806008200
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/176902103
The labels on this github issue will be updated when the story is started.
Describe the bug
Only changing the image, does not create a new bpm secret, so the qsts is not updated.
As a workaround, one could add a label to the
env.bosh.agent.labels
like the kubecf release does.To Reproduce
After installing kubecf 2.7.12 use upgrade to modify only the image:
helm upgrade kubecf -n kubecf --values values.yaml kubecf-v2.7.12.tgz --set 'operations.custom={uaa-dev}'
Expected behavior
The pods should restart with the correct image.
See discussion on Slack: https://cloudfoundry.slack.com/archives/C1BQKKNP4/p1612893806008200