Ah, there we are. That worked! (Even on the v1.5.2 that ships with Centos 7.)
I set the subdomain to "pod" and now I see the following: [centos@ip-172-31-93-54 ~]$ kubectl exec -it custom-django-app-1796634124-7jmd4 /bin/bash root@custom-django-app-1796634124-7jmd4:/django-apps/challenge1# hostname -f custom-django-app-1796634124-7jmd4.pod.default.svc.<ourdomain> Thanks much for the help! DR ----- Original Message ----- From: kubernetes-users@googlegroups.com To:"Kubernetes user discussion and Q&A" <kubernetes-users@googlegroups.com> Cc: Sent:Fri, 8 Sep 2017 09:43:37 -0700 Subject:Re: [kubernetes-users] FQDN's for pods? We don't set the FQDN at all unless you specify the `subdomain` field in Pod.spec. That could be a bug, but the assumption is that the FQDN is "about" DNS lookup-ability. We could have that conversation, though. On Fri, Sep 8, 2017 at 8:39 AM, David Rosenstrauch <dar...@darose.net> wrote: > On 2017-09-06 2:42 pm, David Rosenstrauch wrote: >> >> On 2017-09-06 2:36 pm, Matthias Rampke wrote: >>> >>> TL;DR when you set the cluster domain, this should Just Work™ in >>> Kubernetes 1.7+ but not before >> >> >> That's good news! I'll start to look into us upgrading to a newer >> version. > > > > Hmmm ... some bad news. I built a new cluster using k8s v1.7.5, and I'm > still seeing the same issue: > > [centos@ip-172-31-95-205 ~]$ kubectl exec -it nginx-4217019353-9w7f5 > /bin/bash > root@nginx-4217019353-9w7f5:/# hostname -f > nginx-4217019353-9w7f5 > root@nginx-4217019353-9w7f5:/# cat /etc/hosts > # Kubernetes-managed hosts file. > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > fe00::0 ip6-mcastprefix > fe00::1 ip6-allnodes > fe00::2 ip6-allrouters > 10.240.101.2 nginx-4217019353-9w7f5 > > Any idea what might be the problem / how I might go about fixing? > > Thanks, > > > DR > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
