cds

cds copied to clipboard

I want to be able to run cds in the cloud inside a kubernetes cluster. I want to be able to run local hatcheries on windows and osx machines outside the cluster.

There are two solutions:

1. configure the api-server with the external hostname
2. configure the local hatcheries with the internal service name, add a host file entry, and 2b. configure the api server to run explicitly on port 443 or figure out how to get an ingress to work on a non-standard port (something the nginx-ingress builders are categorically against)

I went with option 1, but now I'm seeing a TON of traffic hitting my nginx-ingress. I have a separate ingress for my dev environment and since there's almost no traffic hitting it regularly it is good for troubleshooting development work. But now with cds in the picture the log output is always cluttered.

Yes, I can filter the log output, but I really shouldn't be routing internal traffic through the proxy.

I found that even if I go with the hotfile route, that makes the cdsctl client problematic. (I couldn't create the initial account unless I registered the account using cdsctl from inside the kubernetes cluster).

I'm sure there's a lot of work to do to make this happen, but being able to reference both an ingress and a service name separately is important. If I've missed out on how to do this, I apologize. I'm still putting together my POC environment and documentation.