Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. Upgrading from a Streams version before 1.7
The v1beta2 API version for all custom resources was introduced with Streams for Apache Kafka 1.7. For Streams for Apache Kafka 1.8, v1alpha1 and v1beta1 API versions were removed from all Streams for Apache Kafka custom resources apart from KafkaTopic and KafkaUser.
Upgrade of the custom resources to v1beta2 prepares Streams for Apache Kafka for a move to Kubernetes CRD v1, which is required for Kubernetes 1.22.
If you are upgrading from a Streams for Apache Kafka version prior to version 1.7:
- Upgrade to Streams for Apache Kafka 1.7
-
Convert the custom resources to
v1beta2 - Upgrade to Streams for Apache Kafka 1.8
You must upgrade your custom resources to use API version v1beta2 before upgrading to Streams for Apache Kafka version 2.9.
3.1. Upgrading custom resources to v1beta2
To support the upgrade of custom resources to v1beta2, Streams for Apache Kafka provides an API conversion tool, which you can download from the Streams for Apache Kafka 1.8 software downloads page.
You perform the custom resources upgrades in two steps.
Step one: Convert the format of custom resources
Using the API conversion tool, you can convert the format of your custom resources into a format applicable to v1beta2 in one of two ways:
- Converting the YAML files that describe the configuration for Streams for Apache Kafka custom resources
- Converting Streams for Apache Kafka custom resources directly in the cluster
Alternatively, you can manually convert each custom resource into a format applicable to v1beta2. Instructions for manually converting custom resources are included in the documentation.
Step two: Upgrade CRDs to v1beta2
Next, using the API conversion tool with the crd-upgrade command, you must set v1beta2 as the storage API version in your CRDs. You cannot perform this step manually.
For more information, see Upgrading from a Streams for Apache Kafka version earlier than 1.7.
