Closed msnelling closed 3 years ago
j-mie
commented
4 years ago @AustinCorridor Are there any plans on releasing an operator for this? We're using the ingress controller at the moment and although it's not ideal it's much more preferable to manually adding a sidecar to each of our deployments using an Argo Ingress.
If there aren't any plans for an Operator - are there any alternate plans - because repeating a bunch of sidecars in deployments is going to suck :(
TownLake
commented
4 years ago We don't have short-term plans for releasing an Operator, but that's not because we don't plan to - we're still trying to figure out the best way to help teams deploy the sidecar model at scale. Releasing an Operator is a good option and one that we're evaluating.
maxpain
commented
4 years ago Any news?
TownLake
commented
4 years ago Not yet - still getting through some other packaging goals, but will update here when we have news. Thanks for the patience.
abelinkinbio
commented
3 years ago We recently released multi-instance cloudflared with this use case in mind. Check it out and let us know what you think: https://blog.cloudflare.com/highly-available-and-highly-scalable-cloudflare-tunnels/
We also made a tutorial to get started: https://developers.cloudflare.com/cloudflare-one/tutorials/many-cfd-one-tunnel
adyanth
commented
2 years ago Something like this might help? Still very much in alpha, but i use it for my homelab.
Given that the Ingress controller project seems dead and that the recommended way to use Argo tunnels with Kubernetes is with the sidecar model, providing an Operator to automatically inject the sidecar would make integrating Argo tunnels into Kubernetes trivial.
For example, an Operator that watched for deployments with specific annotations and then updated the deployment so that it also starts the cloudflared tunnel container.
Other projects doing something similar...