cf-for-k8s
cf-for-k8s copied to clipboard
ConfigMap are created as ver1, ver2, ver3, but not picked up yb pods
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:
- 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.
- re-apply with kapp.
- configmap-ver2 created
- pods are still using configmap-ver1
- pods are still unable to connect to db
Expected behavior
- pods use configmap-ver2
- pods are able to connect to db
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
- remove_resource_requirements: true
Cluster information
aks
CLI versions
- ytt version 0.34.0
- kapp version 0.37.0
- Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:11:29Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"linux/amd64"}
- cf version 6.53.0+8e2b70a4a.2020-10-01
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/178593281
The labels on this github issue will be updated when the story is started.