-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gloo pod is failing when all the upstreams are static and configured with consul integration #8425
Comments
Some additional detail on the issue observered here. This requires a least the following conditions:
We use Consul integration as default discovery mechanism. Discovery is turned off, as we don't want those auto-discovered upstreams - the side effect is there are no upstreams, until we add our own later after Gloo chart installation. From checking the OSS code, we observe that the SDS container seems to no be Ready as the Gloo container has not opened its GRPC port yet. This is why we only see the issue it if mTLS is enabled. This seems to be due to the startup order where Gloo container only opens the GPRC port after it checks for healthy endpoints. If we set Also, we set In summary, installing with the settings in original description, in a namespace other than |
Currently the only way to workaround this is to either:
This was not an issue in previous versions of Gloo. |
Further analysis, by process of elimination of versions, shows that the bug was introduced in 1.13.0-beta10. This version introduces some new settings for Consul. We also now using settings under However, these settings do not seem to directly affect the reproducibility of the issue in this ticket. However they may be relate given the features added in that beta release.
|
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs. |
Gloo Edge Version
1.13.x (beta)
Kubernetes Version
v1.24.0
Describe the bug
I am trying to install gloo chart (version v1.13.0) on kubernetes in a namespace other than 'gloo-system'. However I could see the sds scontainer in the gloo pod is not getting ready. In my values.yaml file, I have disabled the service discovery and also i have provided a consul integration details. However, the above issue is not happening when I install version v1.12.56 or previous versions.
Seems like it is broken from gloo versions >=1.13.0 onwards.
appreciate if you can help thank you.
Steps to reproduce the bug
helm upgrade --install gloo -n my-namespace --create-namespace --wait --debug --values values.yaml gloo-1.13.0.tgz
the following is my values.yaml file
you could observe only 2 out 3 containers in the gloo pod is started.
the kubectl output is as follows
glooctl check
gives the following resultsNot the issue is reproducible only if you use a namespace other than 'gloo-system'. In the test i am using 'my-namespace'. if we use the namespace gloo-system , the gloo pod is runs without any issues.
Expected Behavior
i should expect gloo pod should be started.
Additional Context
No response
The text was updated successfully, but these errors were encountered: