[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] The atomic command and setting hostname for containers
- From: Clayton Coleman <ccoleman redhat com>
- To: Jan Pazdziora <jpazdziora redhat com>
- Cc: atomic-devel projectatomic io
- Subject: Re: [atomic-devel] The atomic command and setting hostname for containers
- Date: Wed, 20 Apr 2016 11:06:39 -0400
Yes, https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/dns#a-records-and-hostname-based-on-pod-annotations---a-beta-feature-in-kubernetes-v12
On Wed, Apr 20, 2016 at 11:02 AM, Jan Pazdziora <jpazdziora redhat com> wrote:
> On Wed, Apr 20, 2016 at 10:53:57AM -0400, Clayton Coleman wrote:
>> Kubernetes injects a specific hostname that corresponds to the DNS
>> name assigned by Kube (in some cases).
>
> So what is the workflow when the container has to be run with
> hostname ipa.example.com, otherwise all sorts of things in the
> container start to fail?
>
> Is there a way to link the hostname to the pod/container so that Kube
> sets the DNS record upfront, so that when starting the container,
> the hostname gets found based on that DNS record?
>
> --
> Jan Pazdziora | adelton at #ipa*, #brno
> Sr. Principal Software Engineer, Identity Management Special Projects, Red Hat
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]