cloudfoundry / cf-for-k8s

The open source deployment manifest for Cloud Foundry on Kubernetes
Apache License 2.0
301 stars 115 forks source link

ConfigMap are created as ver1, ver2, ver3, but not picked up yb pods #672

Open crudalex opened 3 years ago

crudalex commented 3 years ago

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:

  1. generate cf-for-k8s-rendered.yml with cf-values.yml and db-values.yml
  2. apply cf-for-k8s-rendered.yml with kapp
  3. update values in db-values.yml, e.g. changing username from to username@host
  4. re-generate cf-for-k8s-rendered.yml with updated db-values.
  5. re-apply with kapp.
  6. configmap-ver2 created
  7. pods are still using configmap-ver1
  8. pods are still unable to connect to db

Expected behavior

  1. pods use configmap-ver2
  2. 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

Cluster information

aks

CLI versions

  1. ytt version 0.34.0
  2. kapp version 0.37.0
  3. 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"}
  4. cf version 6.53.0+8e2b70a4a.2020-10-01
cf-gitbot commented 3 years ago

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.