Skip to content

Commit 7ac894e

Browse files
authored
Merge pull request #97410 from mletalie/OSDOCS-15479
OSDOCS-15479: Update OSD documentation to highlight WIF as the default authentication type
2 parents 0c30bc3 + 3e7533d commit 7ac894e

File tree

2 files changed

+13
-1
lines changed

2 files changed

+13
-1
lines changed

modules/create-wif-cluster-ocm.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,16 @@
2121
.. Click *Next*.
2222
. Select *Run on Google Cloud Platform*.
2323
. Select *Workload Identity Federation* as the Authentication type.
24+
+
25+
[NOTE]
26+
====
27+
Workload Identity Federation (WIF), Google Cloud's recommended method of authentication, is the default authentication type of {product-title} installation. It greatly improves a cluster's resilience by using short-lived, least-privilege credentials and eliminates the need for static service account keys.
28+
====
29+
+
2430
.. Read and complete all the required prerequisites.
2531

2632
.. Click the checkbox indicating that you have read and completed all the required prerequisites.
33+
2734
+
2835
. To create a new WIF configuration, open a terminal window and run the following OCM CLI command.
2936
+

osd_whats_new/osd-whats-new.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,17 @@ With its foundation in Kubernetes, {product-title} is a complete {OCP} cluster p
1515
[id="osd-new-changes-and-updates_{context}"]
1616
== New changes and updates
1717

18+
[id="osd-q3-2025_{context}"]
19+
=== Q3 2025
20+
* **Workload Identify Federation (WIF) is now the default authentication type for {product-title} clusters on {GCP}.**
21+
In alignment with the principle of least privilege as well as Google Cloud's preferred method of credential authentication, WIF is now the default authentication type when creating an {product-title} cluster on {GCP}. WIF greatly improves an {product-title} cluster's resilience against unauthorized access by using short-lived, least-privilege credentials and eliminating the need for static service account keys. For more information, see xref:../osd_gcp_clusters/creating-a-gcp-cluster-with-workload-identity-federation.adoc[Creating a cluster on GCP with Workload Identity Federation authentication].
22+
1823
[id="osd-q2-2025_{context}"]
1924
=== Q2 2025
2025

2126
// * **{product-title} SDN network plugin blocks future major upgrades**
2227
* **Updated version requirements for migration from OpenShift SDN to OVN-Kubernetes.**
23-
Your cluster version must be 4.16.43 or above to initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
28+
Your cluster version must be 4.16.43 or above to initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
2429
+
2530
If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to future major versions of {product-title} without migrating to OVN-Kubernetes.
2631
+

0 commit comments

Comments
 (0)