Closed p-v-a closed 3 years ago
Actually it's service with a name 'gangway' that were causing this issue, as per https://kubernetes.io/docs/concepts/containers/container-environment/#cluster-information
Found this issue in one of commit discussion few years back.
If deployment named just gangway, then kubernetes will inject its standard environment variables, causing GANGWAY_PORT variable to be something like below, which in turn cause deployment fails to start.
This can be easily avoided by choosing different name for the deployment, however might be good idea to mention that somewhere.