-
Notifications
You must be signed in to change notification settings - Fork 704
Closed
Labels
area/httpproxyIssues or PRs related to the HTTPProxy API.Issues or PRs related to the HTTPProxy API.area/ingressIssues or PRs related to the Ingress API.Issues or PRs related to the Ingress API.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/acceptedDenotes an issue that has been triaged and determined to be valid.Denotes an issue that has been triaged and determined to be valid.
Milestone
Description
What steps did you take and what happened:
- Created Ingress with
example.comand*.example.comentries pointing toservice-a - Created HTTPPRoxy with
subdomain.example.compointing toservice-b
The requests to subdomain.example.com, returned response from service-a. Upon manually removing the wildcard entry from Ingress, requests to subdomain.example.com returned response from service-b.
Anything else you would like to add:
Slack thread: https://kubernetes.slack.com/archives/C8XRH2R4J/p1634816914004100
I was trying to create a minimal reproduction in order to report it, but it seemed to have worked properly.
Creating issue on @stevesloka request, to confirm that this area is tested properly.
Environment:
- Contour version: 1.18.2
- Kubernetes version: (use
kubectl version): v1.22.2 - Kubernetes installer & version: minikube v1.23.2
Metadata
Metadata
Assignees
Labels
area/httpproxyIssues or PRs related to the HTTPProxy API.Issues or PRs related to the HTTPProxy API.area/ingressIssues or PRs related to the Ingress API.Issues or PRs related to the Ingress API.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/acceptedDenotes an issue that has been triaged and determined to be valid.Denotes an issue that has been triaged and determined to be valid.