Upgrade the TimesTen CRDs

You can upgrade TimesTen CRDs that are installed in your Kubernetes cluster. In TimesTen releases 22.1.1.27.0 and greater, the TimesTenClassic CRD contains different schema versions. The v4 schema version is the most current. The v3 and v2 schema versions are available to facilitate compatibility with previous releases of the TimesTen Operator. The v2 schema version is deprecated and will be removed in a future release. For more information, see About Upgrading from Previous Releases.

Note the following:

• You cannot downgrade TimesTen CRDs.

• Since CRDs are cluster-scoped, if you delete TimesTen CRDs from your Kubernetes cluster, all TimesTenClassic objects that are deployed in this cluster are also deleted.

This example uses YAML manifest files for the upgrade. To use Helm charts, see Use Helm in Your TimesTen Kubernetes Operator Environment.

1. On your development host, change to the directory that contains the YAML manifest files for the upgrade. In this example, change to the new_kube_files/deploy directory.

   cd new_kube_files/deploy

2. Replace the TimesTen CRDs that are installed in your Kubernetes cluster.

   kubectl replace -f crd.yaml

   The output is the following:

   customresourcedefinition.apiextensions.k8s.io/timestenclassics.timesten.oracle.com replaced
   customresourcedefinition.apiextensions.k8s.io/timestenscaleouts.timesten.oracle.com replaced

Congratulations! You successfully upgraded the TimesTen CRDs.