Let the K8S cluster decide on ipFamily usage#1651
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: macwinnie The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @macwinnie. Thanks for your PR. I'm waiting for a pulp member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Hi Team =)
We also ran into the No-Startup issue in our IPv6 only K8s cluster, I read about in #1380 – and the solution is as simple as letting the cluster decide on ipFamily usage.
I did not find any reason why the Pulp operator should keep requiring
ipFamilyPolicy: SingleStackor should be locked in withIPv4family – and would be happy to contribute these changes into the project =)All the best,
Martin