On 07/04/2019 23:04, Feilong Wang wrote:
Hi Ionut,
That's an interesting topic. I'm not sure if you can setup a FQDN hostname with current design that the hostname is generated by Heat.
Heat has Designate resources availible, so it could be as simple as adding a OS::Designate::RecordSet resource, with the heat generated name. Let me know if there is interest in this, and I can have a look at adding it. - Graham
On 6/04/19 12:44 AM, Ionut Biru wrote:
Hello,
I was wondering if there is a way to set up the domain for template to use in order to have a FQDN hostname for all the vms that are part from the cluster Currently the name is: k8s-cluster-coreos-somerandomtext-minion-0 but i want something like k8s-cluster-coreos-somerandomtext-minion-0.mydomain.net <http://k8s-cluster-coreos-somerandomtext-minion-0.mydomain.net>
I'm trying to resolve this:
helm install stable/wordpress Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp: lookup k8s-cluster-coreos-7pctbrnuykc6-minion-0 on 8.8.8.8:53 <http://8.8.8.8:53>: no such host
-- Cheers & Best regards, Feilong Wang (王飞龙) -------------------------------------------------------------------------- Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington --------------------------------------------------------------------------