Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Only changing the image does not update the instance group #1280

Open
manno opened this issue Feb 11, 2021 · 1 comment
Open

Only changing the image does not update the instance group #1280

manno opened this issue Feb 11, 2021 · 1 comment
Labels
bug Something isn't working unscheduled

Comments

@manno
Copy link
Member

manno commented Feb 11, 2021

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

@manno manno added the bug Something isn't working label Feb 11, 2021
@cf-gitbot
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working unscheduled
Projects
None yet
Development

No branches or pull requests

2 participants