I am getting the following error messages from the admin console and emissary pod logs:
Chain context mismatch: Host tracker-v2-governance-apex-host cannot combine with foo.bar.baz.com
Chain context mismatch: Host tracker-v2-governance-apex-host cannot combine with foo.bar.baz.com
Chain context mismatch: Host tracker-v2-governance-host cannot combine with region.v1.foo.bar.baz.com
Chain context mismatch: Host tracker-v2-governance-host cannot combine with region.v1.foo.bar.baz.com
The emissary pods are also running near their memory limit (%70) and crashing frequently especially when any configuration change is applied to them. Talked with @cindymullins-dw on slack and she mentioned to post the issue here.
For my configuration I am trying to serve the same service on two endpoints. Here is a simplified version of my config:
Sorry, but this is very specific to my environment. Let me know if I should work more on reproducing this on minikube.
Expected behavior
No crashes.
Versions (please complete the following information):
Ambassador: v2.2.2
Kubernetes environment VKE (Vultr managed k8s)
Version v1.23.5
Additional context
Cindy asked me to verify that the TLS secrets are in the same namespace -> they are. She also linked me to this SO question but not sure what to do to fix it.
Describe the bug
I am getting the following error messages from the admin console and emissary pod logs:
The emissary pods are also running near their memory limit (%70) and crashing frequently especially when any configuration change is applied to them. Talked with @cindymullins-dw on slack and she mentioned to post the issue here.
For my configuration I am trying to serve the same service on two endpoints. Here is a simplified version of my config:
And I get this log on a crash, sorry if this is excessive but don't know if this will help.
To Reproduce Steps to reproduce the behavior:
Sorry, but this is very specific to my environment. Let me know if I should work more on reproducing this on minikube.
Expected behavior
No crashes.
Versions (please complete the following information):
Additional context
Cindy asked me to verify that the TLS secrets are in the same namespace -> they are. She also linked me to this SO question but not sure what to do to fix it.
More than willing to upgrade to the newer emissary as the LOC that is causing the issue doesn't seem to exist in newer versions -> https://github.com/emissary-ingress/emissary/blob/dddd983be480b02465da4f396a29ec9ce75557fd/python/ambassador/envoy/v2/v2listener.py#L89
Thank you very much for your help.