Skip to content

Add 4.14 RN xrefs for STS/CCO/OLM token auth #66839

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

Merged
adellape merged 1 commit into from
Oct 24, 2023
Merged

Add 4.14 RN xrefs for STS/CCO/OLM token auth #66839

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
9 changes: 3 additions & 6 deletions release_notes/ocp-4-14-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,8 +274,7 @@ For more information, see xref:../operators/admin/olm-adding-operators-to-cluste

With this release, OperatorHub detects when an Amazon Web Services (AWS) cluster is using the Security Token Service (STS). When detected, a "Cluster in STS Mode" notification displays with additional instructions before installing an Operator to ensure it runs correctly. The *Operator Installation* page is also modified to add the required *role ARN* field.

For more information, see _Token authentication for Operators on cloud providers_.
//xref :../operators/operator_sdk/osdk-token-auth.adoc#osdk-token-auth[Token authentication for Operators on cloud providers].
For more information, see xref:../operators/operator_sdk/osdk-token-auth.adoc#osdk-token-auth[Token authentication for Operators on cloud providers].

[id="ocp-4-14-developer-perspective"]
==== Developer Perspective
Expand Down Expand Up @@ -698,8 +697,7 @@ For more information, see xref:../authentication/understanding-and-managing-pod-

With this release, some Operators managed by Operator Lifecycle Manager (OLM) on Amazon Web Services (AWS) clusters can use the Cloud Credential Operator (CCO) in manual mode with the Security Token Service (STS). These Operators authenticate with limited-privilege, short-term credentials that are managed outside the cluster.

For more information, see _Token authentication for Operators on cloud providers_.
//xref :../operators/operator_sdk/osdk-token-auth.adoc#osdk-token-auth[Token authentication for Operators on cloud providers].
For more information, see xref:../operators/operator_sdk/osdk-token-auth.adoc#osdk-token-auth[Token authentication for Operators on cloud providers].

[id="ocp-4-14-auth-op-noproxy"]
==== Authentication Operator honors `noProxy` during connection checks
Expand Down Expand Up @@ -944,8 +942,7 @@ For more information, see _{olmv1-first}_.

With this release, Operators managed by Operator Lifecycle Manager (OLM) can support token authentication when running on Amazon Web Services (AWS) clusters that use the Security Token Service (STS). The Cloud Credential Operator (CCO) is updated to semi-automate provisioning certain limited-privilege, short-term credentials, provided that the Operator author has enabled their Operator to support AWS STS.

For more information about enabling OLM-based Operators to support CCO-based workflows with AWS STS, see _Token authentication for Operators on cloud providers_.
//xref :../operators/operator_sdk/osdk-token-auth.adoc#osdk-token-auth[Token authentication for Operators on cloud providers].
For more information about enabling OLM-based Operators to support CCO-based workflows with AWS STS, see xref:../operators/operator_sdk/osdk-token-auth.adoc#osdk-token-auth[Token authentication for Operators on cloud providers].

[id="ocp-4-14-osdk-multi-platform"]
==== Configuring Operator projects with support for multiple platforms
Expand Down