Skip to content

OSDOCS#11105: [4.19 RN] Removal of Operator SDK binary #93473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: enterprise-4.19
Choose a base branch
from
Open

OSDOCS#11105: [4.19 RN] Removal of Operator SDK binary #93473

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 29 additions & 6 deletions release_notes/ocp-4-19-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -456,7 +456,7 @@ For more information, see xref:../updating/preparing_for_updates/updating-cluste
=== Networking

[id="ocp-4-19-networking-support-load-secrets_{context}"]
==== Creating a route with externally managed certificate (General Availability)
==== Creating a route with externally managed certificate (General Availability)

With this release, {product-title} routes can be configured with third-party certificate management solutions, utilising the `.spec.tls.externalCertificate` field in the route API. This allows you to reference externally managed TLS certificates through secrets, streamlining the process by eliminating manual certificate management. By using externally managed certificates, you reduce errors, ensure a smoother certificate update process, and enable the OpenShift router to promptly serve renewed certificates. For more information, see xref:../networking/routes/secured-routes.adoc#nw-ingress-route-secret-load-external-cert_secured-routes[Creating a route with externally managed certificate].

Expand Down Expand Up @@ -499,6 +499,18 @@ With this release, {product-title} introduces the Data Processing Unit (DPU) Ope
[id="ocp-release-notes-osdk_{context}"]
=== Operator development

[id="ocp-release-notes-osdk-base-images_{context}"]
==== Supported Operator base images

The following base images for Operator projects are updated for compatability with {product-title} {product-version}. The runtime functionality and configuration APIs for these base images are supported for bug fixes and for addressing CVEs.

* The base image for Ansible-based Operator projects
* The base image for Helm-based Operator projects

For more information, see link:https://docs.google.com/document/d/1OpdV5QFP_e9Mv3gSj5SrolBXMBqadhJvf2p7zIHUGuY/edit?tab=t.0[Updating the base image for existing Ansible- or Helm-based Operator projects for {product-title} 4.19 and later] (Red{nbsp}Hat Knowledgebase).

// NOTE: This will be a KCS article. Using a google doc as a placeholder to get reviews.

[id="ocp-release-notes-machine-management_{context}"]
=== Machine management

Expand Down Expand Up @@ -558,7 +570,7 @@ This release introduces the following updates to the *Developer* perspective of
[id="ocp-4-19-notable-technical-changes-readonlyrootfilesystem_{context}"]
=== Pods deploy with readOnlyRootFilesystem set to true

With this release, Cloud Credential Operator pods now deploy with the `readOnlyRootFilesystem` security context setting set to `true`. This enhances security by ensuring that the container root file system is mounted as read-only.
With this release, Cloud Credential Operator pods now deploy with the `readOnlyRootFilesystem` security context setting set to `true`. This enhances security by ensuring that the container root file system is mounted as read-only.

[id="ocp-4-19-deprecated-removed-features_{context}"]
== Deprecated and removed features
Expand Down Expand Up @@ -760,22 +772,22 @@ In the following tables, features are marked with the following statuses:
|Operator SDK
|Deprecated
|Deprecated
|Deprecated
|Removed

|Scaffolding tools for Ansible-based Operator projects
|Deprecated
|Deprecated
|Deprecated
|Removed

|Scaffolding tools for Helm-based Operator projects
|Deprecated
|Deprecated
|Deprecated
|Removed

|Scaffolding tools for Go-based Operator projects
|Deprecated
|Deprecated
|Deprecated
|Removed

|Scaffolding tools for Hybrid Helm-based Operator projects
|Deprecated
Expand Down Expand Up @@ -903,6 +915,17 @@ Kubernetes 1.32 removed the following deprecated APIs, so you must migrate manif
|link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#flowcontrol-resources-v132[Yes]
|===

[id="ocp-4-19-removed-osdk_{context}"]
==== Operator SDK CLI and related scaffolding and testing tools

With this release, the Red{nbsp}Hat-supported version of the Operator SDK CLI tool, including the related scaffolding and testing tools for Operator projects, is no longer released with {product-title}.

Red{nbsp}Hat will provide bug fixes and support for versions of the Operator SDK that were released with earlier versions of {product-title} according to the link:https://access.redhat.com/product-life-cycles?product=OpenShift%20Container%20Platform%204[Product Life Cycles for {product-title} 4] (Red{nbsp} Customer Portal).

Operator authors with existing Operator projects can use the version of the Operator SDK CLI tool released with {product-title} 4.18 to maintain their projects and create Operator releases targeting newer versions of {product-title}. For more information, see link:https://docs.google.com/document/d/1OpdV5QFP_e9Mv3gSj5SrolBXMBqadhJvf2p7zIHUGuY/edit?tab=t.0[Updating the base image for existing Ansible- or Helm-based Operator projects for {product-title} 4.19 and later] (Red{nbsp}Hat Knowledgebase).

For more information about the unsupported, community-maintained, version of the Operator SDK, see link:https://sdk.operatorframework.io[Operator SDK (Operator Framework)].

[id="ocp-4-19-future-deprecation_{context}"]
=== Notice of future deprecation

Expand Down