-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow named ports for IPBlocks on ingress (#92)
<!-- Thanks for sending a pull request! Here are some tips for you: 1. Ensure you have added the unit tests for your changes. 2. Ensure you have included output of manual testing done in the Testing section. 3. Ensure number of lines of code for new or existing methods are within the reasonable limit. 4. Ensure your change works on existing clusters after upgrade. --> **What type of PR is this?** <!-- Add one of the following: bug cleanup documentation feature --> bug **Which issue does this PR fix**: #81 **What does this PR do / Why do we need it**: Allows named ports when using IPBlocks (ingress rules only) **If an issue # is not available please add steps to reproduce and the controller logs**: **Testing done on this change**: <!-- output of manual testing/integration tests results and also attach logs showing the fix being resolved --> Manually applied Cx config and policyendpoint looks fine ``` Spec: Ingress: Cidr: 172.17.0.0/16 Ports: Port: 80 Protocol: TCP Cidr: 192.168.8.106 Ports: Port: 443 Protocol: TCP Pod Isolation: Ingress Pod Selector: Match Labels: App: target Pod Selector Endpoints: Host IP: 192.168.98.89 Name: target Namespace: default Pod IP: 192.168.125.203 Policy Ref: Name: allow-web-traffic Namespace: default ``` Using allow all in ingress rule ``` Spec: Ingress: Cidr: 0.0.0.0/0 Ports: Port: 80 Protocol: TCP Port: 443 Protocol: TCP Cidr: ::/0 Ports: Port: 80 Protocol: TCP Port: 443 Protocol: TCP Pod Isolation: Ingress Pod Selector: Match Labels: App: target Pod Selector Endpoints: Host IP: 192.168.98.89 Name: target Namespace: default Pod IP: 192.168.116.203 Policy Ref: Name: allow-web-traffic Namespace: default ``` **Automation added to e2e**: <!-- List the e2e tests you added as part of this PR. If no, create an issue with enhancement/testing label --> 1. NP allowing ingress from IPBlock + 2 named ports 2. NP allowing ingress from all CIDRs + 2 named ports **Will this PR introduce any new dependencies?**: <!-- e.g. new K8s API --> No **Will this break upgrades or downgrades. Has updating a running cluster been tested?**: No **Does this PR introduce any user-facing change?**: <!-- If yes, a release note update is required: Enter your extended release note in the block below. If the PR requires additional actions from users switching to the new release, include the string "action required". --> Yes ```release-note Allow for using named ports when using IPBlocks for the ingress source. ``` By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
- Loading branch information
Showing
3 changed files
with
229 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters