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
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.
Is your feature request related to a problem? Please describe.
No, actually my problem here is about a missing feature actually.
Feature Description
The feature request i mention is that, ability to create Kubernetes Service object for clusters which only use Consul agents as client.
Use Case(s)
Assume that you are using a central Consul cluster outside of Kubernetes, on virtual machines. But you also have 100+ Kubernetes clusters. You are actively using sync-catalog to register/deregister Kubernetes services into Consul. You also have couple of custom operators which interact with Consul through Consul client which is located on each of the nodes in Kubernetes.
We are planning to remove Consul clients from worker nodes inside Kubernetes since we have lots of Kubernetes clusters. This will benefit our Consul clusters from resource consumption point of view. But without the ability of creating Service object for client-only Consul installations through Helm, any custom solution which uses Consul client will fail.
As you see in here, this condition blocks that behavior if our installation is not on server mode.
The text was updated successfully, but these errors were encountered:
Hi @bilalcaliskan -
Thanks for filing this issue and raising it to our attention and sorry for the late reply.
We are currently working on a large change to the architecture of consul-k8s which will remove the client agents altogether. I believe that your feature request would be entirely covered by our changes that are landing soon, namely in removing clients and allowing the use of externalServers with syncCatalog you should be able to accomplish what you described!
Stay tuned, but feel free to reach out here, or on the linked issue #1438
if you have additional feedback or questions.
Cheers,
~Kyle
Community Note
Is your feature request related to a problem? Please describe.
No, actually my problem here is about a missing feature actually.
Feature Description
The feature request i mention is that, ability to create Kubernetes Service object for clusters which only use Consul agents as client.
Use Case(s)
Assume that you are using a central Consul cluster outside of Kubernetes, on virtual machines. But you also have 100+ Kubernetes clusters. You are actively using sync-catalog to register/deregister Kubernetes services into Consul. You also have couple of custom operators which interact with Consul through Consul client which is located on each of the nodes in Kubernetes.
We are planning to remove Consul clients from worker nodes inside Kubernetes since we have lots of Kubernetes clusters. This will benefit our Consul clusters from resource consumption point of view. But without the ability of creating Service object for client-only Consul installations through Helm, any custom solution which uses Consul client will fail.
As you see in here, this condition blocks that behavior if our installation is not on server mode.
The text was updated successfully, but these errors were encountered: