About Upgrading from Previous Releases

In TimesTen releases 22.1.1.27.0 and greater, the TimesTenClassic Custom Resouce Definition (CRD) defines different schema versions. The TimesTen Operator supports the creation, monitoring, and management of TimesTenClassic objects in these schema versions. For more information about TimesTen CRDs, see About TimesTen CRDs.

In TimesTen releases 22.1.1.27.0 and greater, note the following:

  • You can create TimesTenClassic objects in different schema versions. However, to use attributes specific to the latest release of the TimesTen Operator, you must define your object with the v4 schema definitions. For information about these attributes, see TimesTenClassicSpecSpec.

  • Kubernetes uses the v4 schema version as the default version. If you use the kubectl get command to fetch a TimesTenClassic object, Kubernetes returns the object in v4 format, unless you explicitly ask for a different format.

  • Not only does Kubernetes support multiple versions of a CRD simultaneously, but it can serve an object in a schema version that is different than the one in which it was created. A TimesTenClassic object that you created with one schema version can be fetched with another schema version. For example, you can create a v4 TimesTenClassic object and can fetch it as a different version of the object.

  • Kubernetes stores newly created objects using one schema version. Kubernetes stores TimesTenClassic objects in the v4 schema.

  • Use the following syntax to define v4 TimesTenClassic objects: 

    apiVersion: timesten.oracle.com/v4
kind: TimesTenClassic

    Using timesten.oracle.com/v4 for apiVersion instructs Kubernetes to create a v4 object. For more information about apiVersion, see TimesTenClassic.