Description
Overview
EPIC: Kubeflow Upgrade Planning
Component | Local Manifests Path | Upstream | Initial Work |
---|---|---|---|
katib | apps/jupyter/jupyter-web-app | v1.3.1 |
Adjustments
- mysql image uses tag 8.0.22
Kubeflow V2 Manifests
The following is the kustomize that was used in Kubeflow V2:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ../../../.cache/manifests/manifests-1.2-branch/katib/installs/katib-standalone
images:
- name: mysql
newName: mysql
newTag: 8.0.22
AAW Dev / Prod Live Manifests
At the moment there is no difference in state then what is overridden above.
Note: While most everything 95% would have been automated, stored as config and is using what is referenced above. I believe a few things could have been done as manual adjustments that we should make sure we are keeping. Largely any manual yaml adjustments would have been documented in high level GitHub issues or tracked in the YAML repository under the AAW group.
Kubeflow V3 Manifests
The following is the P.R. that will be merged into the main branch for Kubeflow V3:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- github.com/kubeflow/manifests/apps/katib/upstream/installs/katib-with-kubeflow?ref=v1.3.1
images:
- name: mysql
newName: mysql
newTag: 8.0.22
Testing
Usually a good idea to make sure all of the overrides are working is to run the following command and verify all of the yaml output for the component is what you expect and all of the overrides are taken into account.
- Katib deployment output points to mysql:8.0.22
- Upstream resources are outputted successfully
task stack:aaw:preview
Note: The command above will render all of the manifests into manifests top level folder with the name
aaw.yaml
. A trick to keep the yaml output small is understacks/aaw/kustomization.yaml
to only have the component you wish to test referenced.