3.11 Release Notes Feedback Tracker

[ahardin-rh]

Comment with your feedback for the 3.11 Release Notes

[sspeiche]

1. Do we want to call out that kubectl is now available? https://docs.google.com/presentation/d/1jWBoqz4arjYaAyI7ar3vpu62uhyBNmfWXb_yhhBnAYw/edit#slide=id.g29a6e6ca02_0_324 @mpbarrett ?

2. This image is a little fuzzy, might be good to get a higher fidelity one /cc @robszumski

[mcurry-rh]

1. In section "ROUTER (HAPROXY) ENHANCEMENTS"

• missing period in "Performance", column 2.
• indentation issue in "Performance", column 3, last command
• missing closing single-quote in "Performance", column 3, step Tweaked formatting on README #1, 2nd command

2. In "HA NAMESPCE-WIDE EGRESS IP"

Replace:

As a cluster administrator, you can assign specific, static IP addresses to projects, so that traffic is externally easily recognizable. This is different from the default egress router, which is used to send traffic to specific destinations.

With:

Basic active/backup HA for project/namespace egress IPs was added by allowing a namespace to have multiple egress IPs hosted on different cluster nodes.

To an existing project/namespace, add 2 or more egress IPs to its netnamespace:
# oc patch netnamespace myproject -p '{"egressIPs":["10.0.0.1","10.0.0.2"]}'

Add the first egress IP to a node in the cluster:
# oc patch hostsubnet node1 -p '{"egressIPs":["10.0.0.1"]}'

Add the second egress IP to a different node in the cluster:
# oc patch hostsubnet node2 -p '{"egressIPs":["10.0.0.2"]}'

The first listed egress IP will be used by default (if available) until that node stops responding, upon which other nodes will switch to using the next listed egress IP, etc. This solutions requires ≥2 IPs.

If/When the original IP eventually comes back, nodes will switch back to using the original egress IP.

3. In the "FULLY-AUTOMATIC NAMESPCE-WIDE EGRESS IP" section:

• Add the following before the description sentence: "In this release, a "fully automatic" HA option was also added."
• Add the following "how-to" information, after the two description sentences:

Patch one of the cluster nodes with the egressCIDRs:
# oc patch hostsubnet node1 -p '{"egressCIDRs":["10.0.0.0/24"]}'

Create a project/namespace and add a single egress IP to its netnamespace:
# oc patch netnamespace myproject -p '{"egressIPs":["10.0.0.1"]}'

[robszumski]

Make some Operator related edits here already: #12270

[sichvoge]

Made some edits to the Prometheus Cluster Monitoring section here: #12284

[mbearer]

• Should

HA NAMESPCE-WIDE EGRESS IP

_ say NAMESPACE or NAMESPCE?

• Space missing in this sentence:

The Node Problem Detector continues to be in Technology Previewfor this release and is not for production workloads.

• (.) missing in row 7 of the 4.0 Deprecated Features table

Can this sentence be simplified/clarified a bit:

You can now control the use of the local ephemeral storage feature on your nodes in order to prevent users from exhausting node local storage with their pods and other pods that happen to be on the same node.

Section: Service Catalog Access Control

"The broker now confirms to the Open Service Broker specification, which means..."

Typo - this should be conforms. @ahardin-rh I will fix this, just wanted to make an official note here. Thanks.

[vikram-redhat]

3.11 is released. Closing this.