Closed davewalter closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/177387349
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:
WHAT is this change about?
This PR introduces a way to build the UAA image using kbld and pack as part of the new image management initiative. See #173162792 for details of the changes covered in this PR.
Does this PR introduce a change to
config/values.yml
?No
Acceptance Steps
This PR does not change anything in and of itself. The UAA images built are not used when deploying CF for K8s. That work will come later, once we have finished implementing the required build process for those component images that we are able to build.
If you want to manually verify that the UAA image that the new process works in CF for K8s, then you can:
./images/build.sh
kapp deploy -a cf -f <(ytt -f config -f /tmp/${K8S_ENV}.yml | kbld -f - -f images/kbld.lock.yml) -y
Tag your pair, your PM, and/or team
@Birdrock @acosta11