consul-k8s
consul-k8s copied to clipboard
hashicorp
Kubernetes version 1.22 on EKS consul client not able to resolve server nodes running on EC2
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Overview of the Issue
Reproduction Steps
Logs
Expected behavior
Environment details
Additional Context
So consul pods donot come up and throws error
unable to login: error="Unexpected response code: 500 (rpc error making call: Post "https://kubernetes.default.svc/apis/authentication.k8s.io/v1/tokenreviews": dial tcp: lookup kubernetes.default.svc on
And we are not able to resolve kubernetes.default.svc from only consul pods but we can resolve from normal ubuntu pods
Hi @vaibhavgulati! Thank you for filing this issue and I apologize that things are not working for.
So that we're able to better help you, could you please follow the bug template and include additional information in your issue such as your values.yaml, environment details, steps to reproduce along with what version of consul you're using, and logs of errors?
Thanks!
Yes surely I share the values file as well. But the same is working in lower kubernetes version lower than 1.22 Consul client in kubernetes cluster and consul server on EC2 machines. Can you please try once? I'll share values file in the meantime.
Hi @vaibhavgulati ! Now that you mention it, one thing that you will for sure run into is #1145. Right now we do not have support for Kubernetes versions higher than 1.21 due to the changes in secrets/tokens in Kubernetes. We are actively looking into this and plan to have support soon. While it may not be the exact issue you're running into (yet) I wanted to let you know in advance that you will eventually run into a blocker until we add support! For now I'd recommend using Kube 1.21
Okay thanks
On Tue, 5 Jul 2022 at 10:20 PM, Kyle Schochenmaier @.***> wrote:
Hi @vaibhavgulati https://github.com/vaibhavgulati ! Now that you mention it, one thing that you will for sure run into is #1145 https://github.com/hashicorp/consul-k8s/issues/1145. Right now we do not have support for Kubernetes versions higher than 1.21 due to the changes in secrets/tokens in Kubernetes. We are actively looking into this and plan to have support soon. While it may not be the exact issue you're running into (yet) I wanted to let you know in advance that you will eventually run into a blocker until we add support! For now I'd recommend using Kube 1.21
— Reply to this email directly, view it on GitHub https://github.com/hashicorp/consul-k8s/issues/1319#issuecomment-1175273871, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACSMQYUBKZ45H3HETFUDOGTVSRRWRANCNFSM52UES2UA . You are receiving this because you were mentioned.Message ID: @.***>
-- Regards , Vaibhav Gulati
Hi there, I wanted to check if this is resolved? I am facing an issue in prod migration to new version
On Tue, 5 Jul 2022 at 11:43 PM, Vaibhav Gulati < @.***> wrote:
Okay thanks
On Tue, 5 Jul 2022 at 10:20 PM, Kyle Schochenmaier < @.***> wrote:
Hi @vaibhavgulati https://github.com/vaibhavgulati ! Now that you mention it, one thing that you will for sure run into is #1145 https://github.com/hashicorp/consul-k8s/issues/1145. Right now we do not have support for Kubernetes versions higher than 1.21 due to the changes in secrets/tokens in Kubernetes. We are actively looking into this and plan to have support soon. While it may not be the exact issue you're running into (yet) I wanted to let you know in advance that you will eventually run into a blocker until we add support! For now I'd recommend using Kube 1.21
— Reply to this email directly, view it on GitHub https://github.com/hashicorp/consul-k8s/issues/1319#issuecomment-1175273871, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACSMQYUBKZ45H3HETFUDOGTVSRRWRANCNFSM52UES2UA . You are receiving this because you were mentioned.Message ID: @.***>
-- Regards , Vaibhav Gulati
Closing as the PR for supporting 1.24 is now merged. We should see a release sometime later towards the end of this week.
@david-yu - we are using EKS 1.22 is there any chance consul will work in it ?
