Closed Birdrock closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/179063412
The labels on this github issue will be updated when the story is started.
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! :eyes:
Co-authored-by: Andrew Wittrock awittrock@vmware.com
WHAT is this change about?
Istio changed how ConfigMaps are read. cf-for-k8s is Kapp versioning the
istio
ConfigMap
, causing Istio to not detect it.Does this PR introduce a change to
config/values.yml
?No.
Acceptance Steps
istio
ConfigMap
to different configuration and observe propogation.