Removing tech preview param

openshift · Aug 1, 2023 · 2aff820 · 2aff820
1 parent b64d33b
commit 2aff820
Show file tree

Hide file tree

Showing 7 changed files with 1 addition and 83 deletions.
diff --git a/modules/cco-ccoctl-creating-at-once.adoc b/modules/cco-ccoctl-creating-at-once.adoc
@@ -137,12 +137,6 @@ $ ccoctl aws create-all \
 <3> Specify the directory containing the files for the component `CredentialsRequest` objects.
 <4> Optional: Specify the directory in which you want the `ccoctl` utility to create objects. By default, the utility creates objects in the directory in which the commands are run.
 <5> Optional: By default, the `ccoctl` utility stores the OpenID Connect (OIDC) configuration files in a public S3 bucket and uses the S3 URL as the public OIDC endpoint. To store the OIDC configuration in a private S3 bucket that is accessed by the IAM identity provider through a public CloudFront distribution URL instead, use the `--create-private-s3-bucket` parameter.
-+
-[NOTE]
-====
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-//Does --included make this obsolete?
-====
 endif::aws-sts[]
 ifdef::google-cloud-platform[]
 [source,terminal]
@@ -162,12 +156,6 @@ where:
 ** `<gcp_project_id>` is the GCP project ID in which cloud resources will be created.
 ** `<path_to_directory_with_list_of_credentials_requests>/credrequests` is the directory containing the files of `CredentialsRequest` manifests to create GCP service accounts.
 --
-+
-[NOTE]
-====
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-//Does --included make this obsolete?
-====
 endif::google-cloud-platform[]
 
 ifdef::alibabacloud-default,alibabacloud-customizations,alibabacloud-vpc[]
@@ -193,12 +181,6 @@ where:
 ** `<path_to_ccoctl_output_dir>` is the directory where the generated component credentials secrets will be placed.
 --
 +
-[NOTE]
-====
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-//Does --included make this obsolete?
-====
-+
 .Example output
 +
 [source,terminal]

diff --git a/modules/cco-ccoctl-creating-individually.adoc b/modules/cco-ccoctl-creating-individually.adoc
@@ -111,9 +111,6 @@ $ ccoctl aws create-iam-roles \
 [NOTE]
 ====
 For AWS environments that use alternative IAM API endpoints, such as GovCloud, you must also specify your region with the `--region` parameter.
-
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-//Does --included make this obsolete?
 ====
 +
 For each `CredentialsRequest` object, `ccoctl` creates an IAM role with a trust policy that is tied to the specified OIDC identity provider, and a permissions policy as defined in each `CredentialsRequest` object from the {product-title} release image.

diff --git a/modules/installation-uninstall-clouds.adoc b/modules/installation-uninstall-clouds.adoc
@@ -147,12 +147,6 @@ $ ccoctl ibmcloud delete-service-id \
     --credentials-requests-dir <path_to_credential_requests_directory> \
     --name <cluster_name>
 ----
-+
---
-[NOTE]
-====
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-====
 --
 endif::ibm-cloud,ibm-power-vs[]
 

diff --git a/modules/installation-user-infra-generate-k8s-manifest-ignition.adoc b/modules/installation-user-infra-generate-k8s-manifest-ignition.adoc
@@ -421,29 +421,6 @@ stringData:
   azure_region: ${azure_region}
 ----
 
-[IMPORTANT]
-====
-The release image includes `CredentialsRequest` objects for Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set. You can identify these objects by their use of the `release.openshift.io/feature-set: TechPreviewNoUpgrade` annotation.
-//Does --included make this obsolete?
-* If you are not using any of these features, do not create secrets for these objects. Creating secrets for Technology Preview features that you are not using can cause the installation to fail.
-
-* If you are using any of these features, you must create secrets for the corresponding objects.
-====
-
-*** To find `CredentialsRequest` objects with the `TechPreviewNoUpgrade` annotation, run the following command:
-+
-[source,terminal]
-----
-$ grep "release.openshift.io/feature-set" *
-----
-+
-.Example output
-[source,terminal]
-----
-0000_30_capi-operator_00_credentials-request.yaml:  release.openshift.io/feature-set: TechPreviewNoUpgrade
-----
-// Right now, only the CAPI Operator is an issue, but it might make sense to update `0000_30_capi-operator_00_credentials-request.yaml` to `<tech_preview_credentials_request>.yaml` for the future.
-
 .. Create a `cco-configmap.yaml` file in the manifests directory with the Cloud Credential Operator (CCO) disabled:
 +
 .Sample `ConfigMap` object

diff --git a/modules/manually-create-iam-ibm-cloud.adoc b/modules/manually-create-iam-ibm-cloud.adoc
@@ -152,8 +152,6 @@ $ ccoctl ibmcloud create-service-id \
 --
 [NOTE]
 ====
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-
 If an incorrect resource group name is provided, the installation fails during the bootstrap phase. To find the correct resource group name, run the following command:
 
 [source,terminal]

diff --git a/modules/manually-create-identity-access-management.adoc b/modules/manually-create-identity-access-management.adoc
@@ -234,29 +234,6 @@ data:
   service_account.json: <base64_encoded_gcp_service_account_file>
 endif::google-cloud-platform[]
 ----
-+
-[IMPORTANT]
-====
-The release image includes `CredentialsRequest` objects for Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set. You can identify these objects by their use of the `release.openshift.io/feature-set: TechPreviewNoUpgrade` annotation.
-//Does --included make this obsolete?
-* If you are not using any of these features, do not create secrets for these objects. Creating secrets for Technology Preview features that you are not using can cause the installation to fail.
-
-* If you are using any of these features, you must create secrets for the corresponding objects.
-====
-
-** To find `CredentialsRequest` objects with the `TechPreviewNoUpgrade` annotation, run the following command:
-+
-[source,terminal]
-----
-$ grep "release.openshift.io/feature-set" *
-----
-+
-.Example output
-[source,terminal]
-----
-0000_30_capi-operator_00_credentials-request.yaml:  release.openshift.io/feature-set: TechPreviewNoUpgrade
-----
-// Right now, only the CAPI Operator is an issue, but it might make sense to update `0000_30_capi-operator_00_credentials-request.yaml` to `<tech_preview_credentials_request>.yaml` for the future.
 
 ifdef::cco-multi-mode[]
 . From the directory that contains the installation program, proceed with your cluster creation:

diff --git a/modules/refreshing-service-ids-ibm-cloud.adoc b/modules/refreshing-service-ids-ibm-cloud.adoc
@@ -27,11 +27,4 @@ $ ccoctl <provider_name> refresh-keys \ <1>
 <1> The name of the provider. For example: `ibmcloud` or `powervs`.
 <2> The `kubeconfig` file associated with the cluster. For example, `<installation_directory>/auth/kubeconfig`.
 <3> The directory where the credential requests are stored.
-<4> The name of the {product-title} cluster.
-+
---
-[NOTE]
-====
-If your cluster uses Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set, you must include the `--enable-tech-preview` parameter.
-====
---
+<4> The name of the {product-title} cluster.