Open scp-mb opened 2 years ago
Hi @scp-mb, is there a reason not to use an alphanumeric string in this case? If this is a limitation with Envoy, there's not much we can do in the short term besides guarding against numeric-only values.
No hard requirement, but as part of working around #289 I shortened the release name to just match our internal work item number.
I presume the envoy configmap is generated by the routingmanager
pod? If so, would a fix not be as simple as just adding quotes around the value within the yaml to force it to be interpreted as a string?
Fair enough. Will log a bug on our side to investigate
As per title, envoy pods do not start correctly using just numbers with the
kubernetes-route-as
header, e.g. with the annotationrouting.visualstudio.io/route-on-header=kubernetes-route-as=6514
on a pod the following log entry is seen during startup of the envoy pods (note: there is also another service already set up underreview-1496
in these logs, that one works fine and can be ignored).Some information has been redacted where required
And the configmap for the relevant envoy pod: