You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ferenced above. I believe a few things could have been done as manual adjustments that we should make sure we e keeping. Largely any manual yaml adjustments would have been documented in high level GitHub issues or tracked 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 the yaml output for the component is what you expect and all of the overrides are taken into account.
The kubeflow-namespace Namespace is patched correctly (removed label)
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.
The text was updated successfully, but these errors were encountered:
Adjustments
1.3.1
1.4.1
1.6.0
katib-metricscollector-injection: enabled
label from kubeflow namespaceKubeflow 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:
apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - github.com/kubeflow/manifests/common/kubeflow-namespace/base?ref=v1.4.1 patches: - path: namespace_patch.json target: kind: Namespace name: kubeflow version: v1
Kubeflow V1.6 Manifests
Testing
Usually a good idea to make sure all of the overrides are working is to run the following command and verify all the yaml output for the component is what you expect and all of the overrides are taken into account.
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.The text was updated successfully, but these errors were encountered: