You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/cluster-wide-proxy-preqs.adoc
-31Lines changed: 0 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,36 +54,5 @@ When using a cluster-wide proxy, you must configure the `s3.<aws_region>.amazona
54
54
|https/443
55
55
|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.
56
56
|===
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.
Copy file name to clipboardExpand all lines: osd_whats_new/osd-whats-new.adoc
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,10 @@ With its foundation in Kubernetes, {product-title} is a complete {OCP} cluster p
15
15
[id="osd-new-changes-and-updates_{context}"]
16
16
== New changes and updates
17
17
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.
Copy file name to clipboardExpand all lines: rosa_release_notes/rosa-release-notes.adoc
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,8 @@ Egress lockdown is a Technology Preview feature.
24
24
====
25
25
26
26
* **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).
0 commit comments