Edge Console Showing Mappings for all values of `ambassador_id`
See original GitHub issueDescribe the bug
We have multiple AES deployments, each with their own ambassador_id
. When viewing the Edge Console for each of the deployments, the Mappings
associated with all of the Ambassador deployments are shown rather than just the ones for the Ambassador deployment I am looking at.
To Reproduce Steps to reproduce the behavior:
- Create two Ambassador deployments/services with different
ambassador_id
values - Create a mapping for each of the Ambassador deployments, specifying the
ambassador_id
in thespec
- Access the Edge Stack dashboard for either of the Ambassador deployments
- Notice that both
Mappings
are shown and theambassador_id
value is disregarded.
Expected behavior
I would expect the Mappings
shown to be filtered by the ambassador_id
such that only the ones applied to the Ambassador deployment I am looking at will show up in the UI.
Versions (please complete the following information):
- AES: 1.5.2
- Kubernetes environment: GKE
- Version 1.16
Here is an example screenshot showing the YAML with two ambassador_id
values appearing in the same UI
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Edge Console Showing Mappings for all values of `ambassador_id ...
Create a mapping for each of the Ambassador deployments, specifying the ambassador_id in the spec; Access the Edge Stack dashboard for either of...
Read more >Advanced Mapping configuration | Edge Stack
Ambassador Edge Stack must have one or more mappings defined to provide access to any services at all. The name of the mapping...
Read more >Getting started with Ambassador Edge Stack and Consul on ...
Standing up a development sandbox that mirrors your production environment is made fast and simple with the K8s Initializer from Ambassador ...
Read more >Quick and Dirty Token / API Key Authentication in Ambassador
Using Header-based Routing, we can only allow incoming requests with a matching header:value . --- apiVersion: getambassador.io/v2 kind: Mapping
Read more >Kubernetes Ambassador - Signal Sciences Help Center
In this example, Signal Sciences is integrated with Ambassador Edge Stack, ... With this configuration, the agent will pull the values from the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is unquestionably a bug. We’ll get it dealt with.
The Edge Policy Console has been replaced by Ambassador Cloud for 2.x and 3.x. We’d love to know how you find the Ambassador Cloud UI with regards to viewing your mappings by
ambassasdor_id
.