3 ms·
I'm quite curious about the URL service when deploying the server onto Kubernetes. How is the public `waypoint.run` able to access deployments in a Kubernetes c
by MrSaints 6y ago
I'm quite curious about the URL service when deploying the server onto Kubernetes. How is the public `waypoint.run` able to access deployments in a Kubernetes cluster? I know it uses Horizon. But, are the requests somehow proxied through the deployed Waypoint server?
- mitchellh 6y agoWe talk a bit about how this works here: https://www.waypointproject.io/docs/url https://www.waypointproject.io/docs/url Our entrypoint reaches back out to the URL service. This feature is optional. That’s how it works. On our roadmap page you can see that we are planning various improvements to continue to make this more secure as well.
- mfer 6y agoIs the source for waypoint.run open source? Can we run our own? I've not had a chance to dig for the source and it wasn't obvious when I skimmed the project.
- mitchellh 6y agoYes it is: https://github.com/hashicorp/horizon https://github.com/hashicorp/horizon and https://github.com/hashicorp/waypoint-hzn https://github.com/hashicorp/waypoint-hzn Not we haven’t tried to make that easier to self-run, but we didn’t purposely make it difficult either. It just wasn’t a priority for an initial launch. We’ll continue to improve this going forward.