$ tar xvf operator-sdk-v1.31.0-ocp-linux-x86_64.tar.gz
The Operator SDK provides a command-line interface (CLI) tool that Operator developers can use to build, test, and deploy an Operator. You can install the Operator SDK CLI on your workstation so that you are prepared to start authoring your own Operators.
The Red Hat-supported version of the Operator SDK CLI tool, including the related scaffolding and testing tools for Operator projects, is deprecated and is planned to be removed in a future release of OpenShift Container Platform. Red Hat will provide bug fixes and support for this feature during the current release lifecycle, but this feature will no longer receive enhancements and will be removed from future OpenShift Container Platform releases. The Red Hat-supported version of the Operator SDK is not recommended for creating new Operator projects. Operator authors with existing Operator projects can use the version of the Operator SDK CLI tool released with OpenShift Container Platform 4.16 to maintain their projects and create Operator releases targeting newer versions of OpenShift Container Platform. The following related base images for Operator projects are not deprecated. The runtime functionality and configuration APIs for these base images are still supported for bug fixes and for addressing CVEs.
For the most recent list of major functionality that has been deprecated or removed within OpenShift Container Platform, refer to the Deprecated and removed features section of the OpenShift Container Platform release notes. For information about the unsupported, community-maintained, version of the Operator SDK, see Operator SDK (Operator Framework). |
Operator authors with cluster administrator access to a Kubernetes-based cluster, such as OpenShift Container Platform, can use the Operator SDK CLI to develop their own Operators based on Go, Ansible, Java, or Helm. Kubebuilder is embedded into the Operator SDK as the scaffolding solution for Go-based Operators, which means existing Kubebuilder projects can be used as is with the Operator SDK and continue to work. See Developing Operators for full documentation on the Operator SDK.
OpenShift Container Platform 4.16 supports Operator SDK 1.31.0. |
You can install the OpenShift SDK CLI tool on Linux.
Go v1.19+
docker
v17.03+, podman
v1.9.3+, or buildah
v1.7+
Navigate to the OpenShift mirror site.
From the latest 4.16 directory, download the latest version of the tarball for Linux.
Unpack the archive:
$ tar xvf operator-sdk-v1.31.0-ocp-linux-x86_64.tar.gz
Make the file executable:
$ chmod +x operator-sdk
Move the extracted operator-sdk
binary to a directory that is on your PATH
.
To check your
|
$ sudo mv ./operator-sdk /usr/local/bin/operator-sdk
After you install the Operator SDK CLI, verify that it is available:
$ operator-sdk version
operator-sdk version: "v1.31.0-ocp", ...
You can install the OpenShift SDK CLI tool on macOS.
Go v1.19+
docker
v17.03+, podman
v1.9.3+, or buildah
v1.7+
For the amd64
and arm64
architectures, navigate to the OpenShift mirror site for the amd64
architecture and OpenShift mirror site for the arm64
architecture respectively.
From the latest 4.16 directory, download the latest version of the tarball for macOS.
Unpack the Operator SDK archive for amd64
architecture by running the following command:
$ tar xvf operator-sdk-v1.31.0-ocp-darwin-x86_64.tar.gz
Unpack the Operator SDK archive for arm64
architecture by running the following command:
$ tar xvf operator-sdk-v1.31.0-ocp-darwin-aarch64.tar.gz
Make the file executable by running the following command:
$ chmod +x operator-sdk
Move the extracted operator-sdk
binary to a directory that is on your PATH
by running the following command:
Check your
|
$ sudo mv ./operator-sdk /usr/local/bin/operator-sdk
After you install the Operator SDK CLI, verify that it is available by running the following command::
$ operator-sdk version
operator-sdk version: "v1.31.0-ocp", ...