docs: Document adding domain annotation before helm install

[deis]

docs: Document adding domain annotation before helm install

[arschles]

fwiw, it's not necessary to edit before helm install. you can run kubectl --namespace=deis edit rc deis-router and make the change there.

[technosophos]

Is that a better user experience?

[bacongobbler]

I've been doing the following on my hosts in order to get the router working. From my host:

$ cat /etc/hosts
10.245.1.3     example.com
10.245.1.3     deis.example.com
10.245.1.3     go.example.com
10.245.1.3     wooden-ferryman.example.com

Where 10.245.1.3 is the ip address hosting the router as described by kubectl get nodes. deis register http://deis.example.com works after that.

One could do the same with dnsmasq to use wildcards, but this is what I've been using to test the router :)

[arschles]

@technosophos not necessarily, just making note here of another option for editing the router manifest. Also, @bacongobbler IMO your strategy is the easiest way to get started on a local cluster, because no router configs necessary (afaik, router ships configured with example.com).

[krancour]

Editing up front is nicer, imo, but it's good that you're not totally screwed if you forget.

The steps are correct @technosophos laid out look good. And what @bacongobbler suggests also works and is also what router's own docs suggest. (Which I am happy to change if we don't like it.)

I know it's not great that this needs to be customized/configured for each installation, but I see no getting around at ATM. Even in deis v1.x, we required deisctl config platform set domain=<whatever> prior to installation. Platform domain is info we can't do without. :-/

[technosophos]

Here's what I am going to suggest in the docs:

• Set up example.com by default. Focus on this.
• Suggest modifying via kubectl or helm chart. Frame this more as an "advanced option"