We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Ambassador does not allow 2 mappings with the same name with different/same config in different namespaces. An error pops up saying -
CONFIGURATION ERRORS httpbin.ingress2.1: <Mapping httpbin.ingress2.1> defines Mapping httpbin, which is already defined by httpbin.ingress1.1
To Reproduce Steps to reproduce the behavior:
Create namespaces:
kubectl create ns ingress1 kubectl create ns ingress2
kubectl create ns ingress1
kubectl create ns ingress2
and then create the following mappings:
apiVersion: getambassador.io/v2 kind: Mapping metadata: name: httpbin namespace: ingress2 spec: host_rewrite: hb.com prefix: /hb2/ service: http://hb.com
and
apiVersion: getambassador.io/v2 kind: Mapping metadata: name: httpbin namespace: ingress1 spec: host_rewrite: httpbin.org prefix: /hb/ service: http://httpbin.org
Expected behavior Both mappings should work fine
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered:
concaf
Successfully merging a pull request may close this issue.
Describe the bug
Ambassador does not allow 2 mappings with the same name with different/same config in different namespaces. An error pops up saying -
To Reproduce
Steps to reproduce the behavior:
Create namespaces:
kubectl create ns ingress1
kubectl create ns ingress2
and then create the following mappings:
and
Expected behavior
Both mappings should work fine
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: