Skip to content
This repository was archived by the owner on Jul 11, 2023. It is now read-only.

Add root path to ingress in ingress_backend_e2e #4756

Merged

Conversation

nshankar13
Copy link
Contributor

Signed-off-by: nshankar13 nshankar@microsoft.com

Description: This PR addresses an issue where an ingress without a root path does not work for some non-kind distributions like AKS: kubernetes/ingress-nginx#8518. Adding a wildcard path in addition to the status/200 path resolved the issue.

The ingress error happens intermittently.

Testing done: Tested locally on AKS cluster.

Affected area:

Functional Area
New Functionality [ ]
CI System [ ]
CLI Tool [ ]
Certificate Management [ ]
Control Plane [ ]
Demo [ ]
Documentation [ ]
Egress [ ]
Ingress [X]
Install [ ]
Networking [ ]
Observability [ ]
Performance [ ]
SMI Policy [ ]
Security [ ]
Sidecar Injection [ ]
Tests [X]
Upgrade [ ]
Other [ ]

Please answer the following questions with yes/no.

  1. Does this change contain code from or inspired by another project? No

    • Did you notify the maintainers and provide attribution?
  2. Is this a breaking change? No

  3. Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)?

@nshankar13 nshankar13 force-pushed the add_root_path_ingress_e2e branch from 78add0b to 5d69245 Compare May 24, 2022 19:42
Signed-off-by: nshankar13 <nshankar@microsoft.com>
@shashankram shashankram merged commit 15f0a18 into openservicemesh:main May 25, 2022
nshankar13 added a commit to nshankar13/osm that referenced this pull request May 25, 2022
Addresses an issue where an ingress without a root path does
not work for some non-kind distributions like AKS:
kubernetes/ingress-nginx#8518.

Adding a wildcard path in addition to the status/200 path resolves
the issue.

Signed-off-by: nshankar13 <nshankar@microsoft.com>
jaellio pushed a commit that referenced this pull request May 26, 2022
Addresses an issue where an ingress without a root path does
not work for some non-kind distributions like AKS:
kubernetes/ingress-nginx#8518.

Adding a wildcard path in addition to the status/200 path resolves
the issue.

Signed-off-by: nshankar13 <nshankar@microsoft.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants