Upgrade 1.4.1 Common Component: kubeflow-namespace

[wg102]

Overview

EPIC: Kubeflow Upgrade Planning

Component	Local Manifests Path	Upstream	Initial Work
kubeflow-namespace	common/kubeflow-namespace	v1.4.1

Adjustments

• 1.3.1
  • Remove the control-plane label from kubeflow namespace
• 1.4.1
  • No additional adjustments required for 1.4.1 apart from what was already done for 1.3.1.

Kubeflow V2 Manifests

The following is the kustomize that was used in Kubeflow V2:

• https://github.com/StatCan/aaw-kubeflow-manifests/blob/master/kustomize/namespaces/kustomization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
patches:
- path: namespace_patch.json
  target:
    kind: Namespace
    name: kubeflow
    version: v1
resources:
- ../../.cache/manifests/manifests-1.2-branch/namespaces/base

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 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:

• feat(component): Add common component kubeflow-namespace #128

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

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.

• 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.