OCPBUGS-87204: Enable endpoint validation when hostNetwork is used on cloud providers#1464
OCPBUGS-87204: Enable endpoint validation when hostNetwork is used on cloud providers#1464rikatz wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughThis PR adds the exported ENDPOINT_ADDRESS_VALIDATION environment variable and, in desiredRouterDeployment, sets it to "true" for non-default ingress controllers using HostNetwork on specific cloud platforms (AWS, Azure, GCP, AlibabaCloud, IBMCloud, PowerVS, OpenStack). Unit tests cover expected presence/absence, env var sorting, and deploymentConfigChanged detection. An e2e test creates a host-network ingresscontroller, verifies the router Deployment gets ENDPOINT_ADDRESS_VALIDATION="true", and verifies the default router does not. Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error, 3 warnings)
✅ Passed checks (11 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.12.2)Command failed Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@rikatz: This pull request references Jira Issue OCPBUGS-87204, which is valid. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
… cloud providers When a custom ingress controller is deployed, and it is intentionally using hostNetwork, some extra validations must be added so a user doesn't use the router to bypass network restrictions. This change makes CIO enforce the new endpoint-address-validation flag on custom ingress controllers deployed on cloud environments.
|
/payload-job-with-prs prow/e2e-aws-operator openshift/router#788 #1464 |
|
/payload-job-with-prs prow/e2e-aws-operator openshift/router#788 #1464 |
|
@rikatz: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/hold This should not be merged, if we decide to go with the current approach of openshift/router#788 (no flag anymore, validate any fqdn endpoint) |
|
I am closing this, given the approach will be directly on router to filter invalid IPs |
|
@rikatz: This pull request references Jira Issue OCPBUGS-87204. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@rikatz: Closed this PR. DetailsIn response to this:
Instructions 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. |
When a custom ingress controller is deployed, and it is intentionally using hostNetwork, some extra validations must be added so a user doesn't use the router to bypass network restrictions.
This change makes CIO enforce the new endpoint-address-validation flag on custom ingress controllers deployed on cloud environments.
This PR is related with openshift/router#788 and should be merged after it