When I updated cf-values.yml and regenerate cf-for-k8s-rendered.yml with ytt. configmap-ver2, configmap-ver3 are created in namespace, but pods are still using ver1.
To Reproduce*
Steps to reproduce the behavior:
generate cf-for-k8s-rendered.yml with cf-values.yml and db-values.yml
apply cf-for-k8s-rendered.yml with kapp
update values in db-values.yml, e.g. changing username from to username@host
re-generate cf-for-k8s-rendered.yml with updated db-values.
Describe the bug
When I updated cf-values.yml and regenerate cf-for-k8s-rendered.yml with ytt. configmap-ver2, configmap-ver3 are created in namespace, but pods are still using ver1.
To Reproduce*
Steps to reproduce the behavior:
Expected behavior
Additional context
cf-for-k8s SHA
https://github.com/cloudfoundry/cf-for-k8s/commit/19b760e16d2745a58b6d7bd0da535a7aa439ca6b
Deploy instructions
https://cf-for-k8s.io/docs/deploying/ https://cf-for-k8s.io/docs/platform_operators/setup-static-loadbalancer-ip https://cf-for-k8s.io/docs/platform_operators/external-databases https://cf-for-k8s.io/docs/platform_operators/external-blobstore
Cluster information
aks
CLI versions