Skip to content

Commit 1f565a3

Browse files
authored
Merge pull request #52652 from EricPonvelle/OSDOCS-4507_TrustBundleRemove
OSDOCS-4507: Added instructions for removing a CA bundle from ROSA
2 parents dbc13f0 + 329c946 commit 1f565a3

File tree

2 files changed

+101
-1
lines changed

2 files changed

+101
-1
lines changed

modules/configmap-removing-ca.adoc

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * builds/setting-up-trusted-ca
4+
5+
:_content-type: PROCEDURE
6+
[id="configmap-removing-ca_{context}"]
7+
= Removing certificate authorities on a {product-title} cluster
8+
9+
You can remove certificate authorities (CA) from your cluster with the `rosa` CLI tool.
10+
11+
.Prerequisites
12+
13+
* You must have cluster administrator privileges.
14+
* You have installed the `rosa` CLI tool.
15+
* Your cluster has certificate authorities added.
16+
17+
.Procedure
18+
19+
* Use the `rosa edit` command to modify the CA trust bundle. You must pass empty strings to the `--additional-trust-bundle-file` argument to clear the trust bundle from the cluster:
20+
+
21+
[source,terminal]
22+
----
23+
$ rosa edit cluster -c <cluster_name> --additional-trust-bundle-file ""
24+
----
25+
+
26+
.Example Output
27+
+
28+
[source,yaml]
29+
----
30+
I: Updated cluster <cluster_name>
31+
----
32+
33+
.Verification
34+
35+
* You can verify that the trust bundle has been removed from the cluster by using the `rosa describe` command:
36+
+
37+
[source,yaml]
38+
----
39+
$ rosa describe cluster -c <cluster_name>
40+
----
41+
+
42+
Before removal, the Additional trust bundle section appears, redacting its value for security purposes:
43+
+
44+
[source,yaml]
45+
----
46+
Name: <cluster_name>
47+
ID: <cluster_internal_id>
48+
External ID: <cluster_external_id>
49+
OpenShift Version: 4.11.9
50+
Channel Group: stable
51+
DNS: <dns>
52+
AWS Account: <aws_account_id>
53+
API URL: <api_url>
54+
Console URL: <console_url>
55+
Region: us-east-1
56+
Multi-AZ: false
57+
Nodes:
58+
- Control plane: 3
59+
- Infra: 2
60+
- Compute: 2
61+
Network:
62+
- Type: OVNKubernetes
63+
- Service CIDR: <service_cidr>
64+
- Machine CIDR: <machine_cidr>
65+
- Pod CIDR: <pod_cidr>
66+
- Host Prefix: <host_prefix>
67+
Proxy:
68+
- HTTPProxy: <proxy_url>
69+
Additional trust bundle: REDACTED
70+
----
71+
+
72+
After removing the proxy, the Additional trust bundle section is removed:
73+
+
74+
[source,yaml]
75+
----
76+
Name: <cluster_name>
77+
ID: <cluster_internal_id>
78+
External ID: <cluster_external_id>
79+
OpenShift Version: 4.11.9
80+
Channel Group: stable
81+
DNS: <dns>
82+
AWS Account: <aws_account_id>
83+
API URL: <api_url>
84+
Console URL: <console_url>
85+
Region: us-east-1
86+
Multi-AZ: false
87+
Nodes:
88+
- Control plane: 3
89+
- Infra: 2
90+
- Compute: 2
91+
Network:
92+
- Type: OVNKubernetes
93+
- Service CIDR: <service_cidr>
94+
- Machine CIDR: <machine_cidr>
95+
- Pod CIDR: <pod_cidr>
96+
- Host Prefix: <host_prefix>
97+
Proxy:
98+
- HTTPProxy: <proxy_url>
99+
----

networking/configuring-cluster-wide-proxy.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,8 @@ include::modules/configuring-a-proxy-after-installation-cli.adoc[leveloffset=+2]
8686
[id="removing-cluster-wide-proxy_{context}"]
8787
== Removing a cluster-wide proxy
8888

89-
You can remove your cluster-wide proxy by using the `rosa` CLI tool.
89+
You can remove your cluster-wide proxy by using the `rosa` CLI tool. After removing the cluster, you should also remove any trust bundles that are added to the cluster.
9090

9191
include::modules/nw-rosa-proxy-remove-cli.adoc[leveloffset=+2]
92+
include::modules/configmap-removing-ca.adoc[leveloffset=+2]
9293
endif::openshift-rosa[]

0 commit comments

Comments
 (0)