You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you enable tracing with a long cluster name then configuration will fail
To Reproduce
Two ways with different results:
Upgrade from 0.40.1 to 0.50.0-ea7 in a configuration with tracing enabled and long cluster name. Result is Ambassador in a CrashLoopBackoff
Deploy fresh 0.50.0-ea7 and then enabled tracing. Ambassador starts (assuming initially configured without tracing), but once tracing is enabled Ambassador configuration remains unchanged.
Expected behavior
No error, tracing works (given it works in Ambassador 0.40.1)
Versions (please complete the following information):
Ambassador: 0.50.0-ea7
Kubernetes environment [e.g. Minikube, bare metal, Google Kubernetes Engine]: bare metals
flands
changed the title
Regression: Ambassador 0.50.0-ea7 tracing does not work with long names
Regression: Ambassador 0.50.0-ea7 tracing does not work with long cluster names
Dec 9, 2018
Describe the bug
If you enable tracing with a long cluster name then configuration will fail
To Reproduce
Two ways with different results:
Upgrade from 0.40.1 to 0.50.0-ea7 in a configuration with tracing enabled and long cluster name. Result is Ambassador in a CrashLoopBackoff
Deploy fresh 0.50.0-ea7 and then enabled tracing. Ambassador starts (assuming initially configured without tracing), but once tracing is enabled Ambassador configuration remains unchanged.
Expected behavior
No error, tracing works (given it works in Ambassador 0.40.1)
Versions (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: