Skip to content

Commit 2f718fd

Browse files
authored
Merge pull request #87707 from michaelryanmcneill/OSDOCS-13243
OSDOCS-13243: Removing references to Splunk Forwarder tcpout
2 parents e16ee27 + 85643cb commit 2f718fd

File tree

5 files changed

+6
-84
lines changed

5 files changed

+6
-84
lines changed

modules/cluster-wide-proxy-preqs.adoc

Lines changed: 0 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -54,36 +54,5 @@ When using a cluster-wide proxy, you must configure the `s3.<aws_region>.amazona
5454
|https/443
5555
|The https://cloud.redhat.com/openshift site uses authentication from sso.redhat.com to download the cluster pull secret and use Red Hat SaaS solutions to facilitate monitoring of your subscriptions, cluster inventory, and chargeback reporting.
5656
|===
57-
+
58-
** Your proxy must exclude re-encrypting the following site reliability engineering (SRE) and management URLs:
59-
+
60-
[cols="6,1,6",options="header"]
61-
|===
62-
|Address | Protocol/Port | Function
63-
|`*.osdsecuritylogs.splunkcloud.com`
64-
65-
**OR**
66-
67-
`inputs1.osdsecuritylogs.splunkcloud.com`
68-
`inputs2.osdsecuritylogs.splunkcloud.com`
69-
`inputs4.osdsecuritylogs.splunkcloud.com`
70-
`inputs5.osdsecuritylogs.splunkcloud.com`
71-
`inputs6.osdsecuritylogs.splunkcloud.com`
72-
`inputs7.osdsecuritylogs.splunkcloud.com`
73-
`inputs8.osdsecuritylogs.splunkcloud.com`
74-
`inputs9.osdsecuritylogs.splunkcloud.com`
75-
`inputs10.osdsecuritylogs.splunkcloud.com`
76-
`inputs11.osdsecuritylogs.splunkcloud.com`
77-
`inputs12.osdsecuritylogs.splunkcloud.com`
78-
`inputs13.osdsecuritylogs.splunkcloud.com`
79-
`inputs14.osdsecuritylogs.splunkcloud.com`
80-
`inputs15.osdsecuritylogs.splunkcloud.com`
81-
|tcp/9997
82-
|Used by the splunk-forwarder-operator as a log forwarding endpoint to be used by Red Hat SRE for log-based alerting.
83-
84-
|`http-inputs-osdsecuritylogs.splunkcloud.com`
85-
|https/443
86-
|Used by the splunk-forwarder-operator as a log forwarding endpoint to be used by Red Hat SRE for log-based alerting.
87-
|===
8857
--
8958

modules/osd-aws-privatelink-firewall-prerequisites.adoc

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -275,25 +275,6 @@ Alternatively, if you choose to not use a wildcard for Amazon Web Services (AWS)
275275
|443
276276
|Alerting service used by {product-title} to send periodic pings that indicate whether the cluster is available and running.
277277

278-
|`.osdsecuritylogs.splunkcloud.com`
279-
OR
280-
`inputs1.osdsecuritylogs.splunkcloud.com`
281-
`inputs2.osdsecuritylogs.splunkcloud.com`
282-
`inputs4.osdsecuritylogs.splunkcloud.com`
283-
`inputs5.osdsecuritylogs.splunkcloud.com`
284-
`inputs6.osdsecuritylogs.splunkcloud.com`
285-
`inputs7.osdsecuritylogs.splunkcloud.com`
286-
`inputs8.osdsecuritylogs.splunkcloud.com`
287-
`inputs9.osdsecuritylogs.splunkcloud.com`
288-
`inputs10.osdsecuritylogs.splunkcloud.com`
289-
`inputs11.osdsecuritylogs.splunkcloud.com`
290-
`inputs12.osdsecuritylogs.splunkcloud.com`
291-
`inputs13.osdsecuritylogs.splunkcloud.com`
292-
`inputs14.osdsecuritylogs.splunkcloud.com`
293-
`inputs15.osdsecuritylogs.splunkcloud.com`
294-
|9997
295-
|Used by the `splunk-forwarder-operator` as a logging forwarding endpoint to be used by Red{nbsp}Hat SRE for log-based alerting.
296-
297278
|`http-inputs-osdsecuritylogs.splunkcloud.com`
298279
|443
299280
|Required. Used by the `splunk-forwarder-operator` as a logging forwarding endpoint to be used by Red{nbsp}Hat SRE for log-based alerting.

modules/osd-gcp-psc-firewall-prerequisites.adoc

Lines changed: 0 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -153,40 +153,6 @@ Managed clusters require the enabling of telemetry to allow Red Hat to react mor
153153
|443
154154
|Alerting service used by {product-title} to send periodic pings that indicate whether the cluster is available and running.
155155

156-
|`*.osdsecuritylogs.splunkcloud.com`
157-
158-
OR
159-
160-
`inputs1.osdsecuritylogs.splunkcloud.com`
161-
162-
`inputs2.osdsecuritylogs.splunkcloud.com`
163-
164-
`inputs4.osdsecuritylogs.splunkcloud.com`
165-
166-
`inputs5.osdsecuritylogs.splunkcloud.com`
167-
168-
`inputs6.osdsecuritylogs.splunkcloud.com`
169-
170-
`inputs7.osdsecuritylogs.splunkcloud.com`
171-
172-
`inputs8.osdsecuritylogs.splunkcloud.com`
173-
174-
`inputs9.osdsecuritylogs.splunkcloud.com`
175-
176-
`inputs10.osdsecuritylogs.splunkcloud.com`
177-
178-
`inputs11.osdsecuritylogs.splunkcloud.com`
179-
180-
`inputs12.osdsecuritylogs.splunkcloud.com`
181-
182-
`inputs13.osdsecuritylogs.splunkcloud.com`
183-
184-
`inputs14.osdsecuritylogs.splunkcloud.com`
185-
186-
`inputs15.osdsecuritylogs.splunkcloud.com`
187-
|9997
188-
|Used by the `splunk-forwarder-operator` as a logging forwarding endpoint to be used by Red{nbsp}Hat SRE for log-based alerting.
189-
190156
|`http-inputs-osdsecuritylogs.splunkcloud.com`
191157
|443
192158
|Used by the `splunk-forwarder-operator` as a logging forwarding endpoint to be used by Red{nbsp}Hat SRE for log-based alerting.

osd_whats_new/osd-whats-new.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ 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-q1-2025_{context}"]
19+
=== Q1 2025
20+
* **Red{nbsp}Hat SRE log-based alerting endpoints have been updated.** {product-title} customers who are using a firewall to control egress traffic can now remove all references to `*.osdsecuritylogs.splunkcloud.com:9997` from your firewall allowlist. {product-title} clusters still require the `http-inputs-osdsecuritylogs.splunkcloud.com:443` log-based alerting endpoint to be accessible from the cluster.
21+
1822
[id="osd-q4-2024_{context}"]
1923
=== Q4 2024
2024

rosa_release_notes/rosa-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ Egress lockdown is a Technology Preview feature.
2424
====
2525

2626
* **Egress lockdown is now available as a Technology Preview on {product-title} clusters.** You can create a fully operational cluster that does not require a public egress by configuring a virtual private cloud (VPC) and using the `--properties zero_egress:true` flag when creating your cluster. For more information, see xref:../rosa_hcp/rosa-hcp-egress-lockdown-install.adoc#rosa-hcp-egress-lockdown-install[Creating a {product-title} cluster with egress lockdown].
27+
28+
* **Red{nbsp}Hat SRE log-based alerting endpoints have been updated.** {product-title} customers who are using a firewall to control egress traffic can now remove all references to `*.osdsecuritylogs.splunkcloud.com:9997` from your firewall allowlist. {product-title} clusters still require the `http-inputs-osdsecuritylogs.splunkcloud.com:443` log-based alerting endpoint to be accessible from the cluster. This is applicable only to Red{nbsp}Hat OpenShift Service on AWS (classic architecture).
2729
endif::openshift-rosa[]
2830
ifdef::openshift-rosa-hcp[]
2931
[IMPORTANT]

0 commit comments

Comments
 (0)