Follow below step for manual upgrade testing
- Set environment variables to overwrite values in Makefile. You should overwrite the IMAGE_OWNER and VERSION etc values for pushing container images into your quay.io account.
IMAGE_OWNER ?= IMAGE_OWNER
VERSION ?= VERSION
- Add
replaces
property in opendatahub-operator.clusterserviceversion.yaml and add version which you would like to upgrade with next version
replaces: opendatahub-operator.v2.4.0
- Build and push docker container image
make image
- Build bundle image
make bundle-build
- Push bundle image into registry
make bundle-push
- Build catalog source image
make catalog-build
- Push catalog source image into registry
make catalog-push
Deploy CatalogSource on cluster to install Open Data Hub Operator
.
- Deploy CatalogSource. Deploy catalog source on cluster by using your catalog source container image and wait until catalog source pod is ready
cat <<EOF | oc create -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: opendatahub-catalog
namespace: openshift-marketplace
spec:
sourceType: grpc
image: quay.io/$IMAGE_OWNER/opendatahub-operator-catalog:$VERSION
displayName: Open Data Hub Operator
publisher: ODH
EOF
- Subscribe to the ODH custom catalog
cat <<EOF | oc create -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: opendatahub-operator
namespace: openshift-operators
spec:
channel: fast
name: opendatahub-operator
source: opendatahub-catalog
sourceNamespace: openshift-marketplace
EOF
-
Follow steps
1 to 7
to build new version of catalog-source image -
Apply updated version of catalog
cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: opendatahub-catalog
namespace: openshift-marketplace
spec:
sourceType: grpc
image: quay.io/$IMAGE_OWNER/opendatahub-operator-catalog:$VERSION
displayName: Open Data Hub Operator
publisher: ODH
EOF
-
Select
fast
channel to update -
Go to Installed Operator
Open Data Hub Operator
and upgrade operator with latest version under tabSubscription
- When Operator is installed it creates a namespace called
opendatahub
. - Users need to create required
DataScienceCluster
resource by going to theInstalled Operators
tab in the OpenShift Cluster. - Users should explicitly set components with
managementState: Managed
in order for components to be installed.
cat <<EOF | oc apply -f -
apiVersion: datasciencecluster.opendatahub.io/v1
kind: DataScienceCluster
metadata:
name: example
spec:
components:
codeflare:
managementState: Managed
dashboard:
managementState: Managed
datasciencepipelines:
managementState: Managed
kserve:
managementState: Managed
serving:
ingressGateway:
certificate:
type: OpenshiftDefaultIngress
managementState: Managed
name: knative-serving
modelmeshserving:
managementState: Managed
modelregistry:
managementState: Managed
registriesNamespace: "odh-model-registries"
ray:
managementState: Managed
kueue:
managementState: Managed
trainingoperator:
managementState: Managed
workbenches:
managementState: Managed
trustyai:
managementState: Managed
EOF