Upgrade 1.4.1 Common Component: kubeflow-knative

[bryanpaget]

EPIC: Kubeflow Upgrade Planning

Component	Local Manifests Path	Upstream	Issue	AAW Sign-off	CNS Sign-off	Notes
kubeflow-knative	common/knative	v1.4.1				No structural changes.

Adjustments

KF v1.4 Adjustments:

• 1.4.1
  • Upgraded knative serving to v0.22.1
  • No additional adjustments required for 1.4.1 apart from what was already done for 1.3.1.

KF v1.3 Adjustments:

• Adjustments to config-domain for eventual serving workloads on the AAW domain
• Adjustments to config-istio for eventual serving workloads on the AAW domain

Kubeflow V2 Manifests

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

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

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ../../.cache/manifests/manifests-1.2-branch/knative/installs/generic

AAW Dev / Prod Live Manifests

The difference is state is largely accounted for in these issue(s):

• Kserve integration and documentation aaw#667

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 common component knative #130

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

resources:
- github.com/kubeflow/manifests/common/knative/knative-serving/base?ref=v1.3.1
- github.com/kubeflow/manifests/common/knative/knative-eventing/base?ref=v1.3.1

patchesStrategicMerge:
- config-domain.yaml

patches:
- config-istio.yaml

Note: I needed to override the whole config-istio object so used patches instead of 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.

• Adjustments to config-domain were successful
• Adjustments to config-istio were successful

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.