doc: PendingReleaseNotes for update netNamespaceFilePath PR #13809
Conversation
iPraveenParihar
force-pushed
the
update/pendingReleaseNotes
branch
from
3672b4e to
b8a0ccd
Compare
PendingReleaseNotes.md
Outdated
| @@ -5,6 +5,7 @@ | |||
| - The removal of `CSI_ENABLE_READ_AFFINITY` option and its replacement with per-cluster | |||
| read affinity setting in cephCluster CR (CSIDriverOptions section) in [PR](https://github.com/rook/rook/pull/13665) | |||
| - Allow setting the Ceph `application` on a pool | |||
| - updating `netNamespaceFilePath` for all clusterIDs in rook-ceph-csi-config configMap [PR](https://github.com/rook/rook/pull/13613) | |||
There was a problem hiding this comment.
Can you also describe the impact of the breaking change? Users need to find how to know if they are impacted, and what is the impact for them. Is there any action they need to take if they are impacted?
Signed-off-by: Praveen M <m.praveen@ibm.com>
iPraveenParihar
force-pushed
the
update/pendingReleaseNotes
branch
from
b8a0ccd to
10dea45
Compare
| - updating `netNamespaceFilePath` for all clusterIDs in rook-ceph-csi-config configMap in [PR](https://github.com/rook/rook/pull/13613) | ||
| - Issue: The netNamespaceFilePath isn't updated in the CSI config map for all the clusterIDs when `CSI_ENABLE_HOST_NETWORK` is set to false in `operator.yaml` | ||
| - Impact: This results in the unintended network configurations, with pods using the host networking instead of pod networking. |
There was a problem hiding this comment.
I need help understanding this pending release note. This is listed as a breaking change, but there are no instructions for users to follow to keep their cluster from breaking. Is this actually a breaking change?
There was a problem hiding this comment.
i think nothing was required from the user point and we never supported moving from multus/pod network to host networking or vice-versa, @iPraveenParihar can you please check this and confirm?
There was a problem hiding this comment.
@BlaineEXE actually this was an issue that I believed users should be aware of if they were using Pod networking.
There was a problem hiding this comment.
i think nothing was required from the user point and we never supported moving from multus/pod network to host networking or vice-versa
I thought there was a period of time where we had CSI_ENABLE_HOST_NETWORK: false as the default value for all Rook users? Am I misremembering?
If that was the default, then we need to have supported users setting that value back to true so they could get in line with the latest recommendations.
There was a problem hiding this comment.
It was enabled briefly three years ago (see #8085), but I'm not sure we need to worry about that too much since it was for such a short time and users would have had serious issues if they didn't already convert back to host networking.
doc: PendingReleaseNotes for update netNamespaceFilePath PR (#13613)
Checklist: