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:
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.
Deployment with imagePullSecrets ouputted 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 under stacks/aaw/kustomization.yaml to only have the component you wish to test referenced.
Overview
EPIC: Kubeflow Upgrade Planning
v1.4.1
Adjustments
Kubeflow V2 Manifests
The following is the kustomize that was used in Kubeflow V2:
AAW Dev / Prod Live Manifests
At the moment there is no difference in state then what is overridden above.
Kubeflow V3 Manifests
The following is the P.R. that will be merged into the main branch for Kubeflow V3:
143
apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources:
patchesStrategicMerge:
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.