Skip to content
New issue

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

Host - mapping associating not working. #63

Open
pbabilas opened this issue Mar 15, 2022 · 0 comments
Open

Host - mapping associating not working. #63

pbabilas opened this issue Mar 15, 2022 · 0 comments

Comments

@pbabilas
Copy link

Hi,
I've tried to make my configuration in edge-stack like here:
https://www.getambassador.io/docs/edge-stack/latest/topics/running/host-crd/

But despite my label selector, all hosts gets all mappings.

mappings:

apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  generation: 1
  labels:
    host-nb_outlet: nb_outlet
  name: isearch-wasiol
  namespace: test-edgestack
spec:
  ambassador_id:
  - --apiVersion-v3alpha1-only--default
  precedence: 2
  prefix: /wasiol
  rewrite: ""
  service: isearch.test-edgestack
  timeout_ms: 0
  hostname: a2d461472a026efc.ci.merce.cloud

---

apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  generation: 1
  labels:
    host-raccoon: raccoon
  name: iuploader-wasiol
  namespace: test-edgestack
spec:
  ambassador_id:
  - --apiVersion-v3alpha1-only--default
  precedence: 2
  prefix: /wasiol
  rewrite: ""
  service: iuploader.test-edgestack
  timeout_ms: 0
  hostname: a3e23aacf7a776c2.ci.merce.cloud

and host:

apiVersion: getambassador.io/v2
kind: Host
metadata:
  name: raccoon
  namespace: test-edgestack
spec:
  ambassador_id:
  - --apiVersion-v3alpha1-only--default
  hostname: a3e23aacf7a776c2.ci.merce.cloud
  requestPolicy:
    insecure:
      action: Route
      additionalPort: -1
  selector:
    matchLabels:
      host-raccoon: raccoon
---
apiVersion: getambassador.io/v2
kind: Host
metadata:
  name: nb-outlet
  namespace: test-edgestack
spec:
  ambassador_id:
  - --apiVersion-v3alpha1-only--default
  hostname: a2d461472a026efc.ci.merce.cloud
  requestPolicy:
    insecure:
      action: Route
      additionalPort: -1
  selector:
    matchLabels:
      host-nb_outlet: nb_outlet

Here the mapping for one domains:
foo
foo

Is there any misconfiguration been done? or it's just not working?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant