Upgrade 1.4.1 Apps: central-dashboard

[bryanpaget]

EPIC: Kubeflow Upgrade Planning

Component	Local Manifests Path	Upstream	Issue	AAW Sign-off	CNS Sign-off	Notes
central-dashboard	apps/centraldashboard	v1.4.1				No structural changes.

Adjustments

• 1.4.1

  • Configmap will need to updated
  • The image sha will need to be updated once forked centraldashboard code is rebased and merged.

• 1.3.1

  • Add image pull secret to centraldashboard deployment
  • Change REGISTRATION_FLOW to true in centraldashboard deployment
  • Change centraldashboard links in configmap

Kubeflow V2 Manifests

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

• https://github.com/StatCan/aaw-kubeflow-manifests/tree/master/kustomize/application/centraldashboard

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
patchesStrategicMerge:
- deployment.yaml
- links-configmap.yaml
resources:
- ../../../.cache/manifests/manifests-1.2-branch/stacks/azure/application/centraldashboard

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:

• feat(component): Add apps component centraldashboard #121

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- github.com/kubeflow/manifests/apps/centraldashboard/upstream/overlays/istio?ref=v1.3.1

patchesStrategicMerge:
- deployment.yaml
- centraldashboard-config.yaml

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.

• The centraldashboard deployment has been modified correctly (image, imagepullsecrets, and envvar)
• The centraldashboard-config configmap has been modified correctly

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.