00
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
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 wrote:
> On
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
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.
David – what Kubernete version are you running?
We're running v1.5.2.
TL;DR when you set the cluster domain, this should Just Work™ in Kubernetes
1.7+ but not before
David – what Kubernete version are you running? I just went down a rabbit
hole because our /etc/hosts did not look like this code[0] suggests it
should. Turns out, there was a bug before 1.7[1] that
On 2017-09-05 6:19 pm, 'Tim Hockin' via Kubernetes user discussion and
Q wrote:
We do not have a mechanism to express what you want to express, then.
You control the cluster suffix and the subdomain, and the pod name,
but even with all of those in play, the hostname comes out as
`..svc.`, I am
As Matthias said, you can use the --cluster-domain if you want to. That is
usually set at installation.
That may be the simplest thing, and maybe fits better in your organization
using your domain for the cluster.
But if the license check is doing that, I bet that you can use LD_PRELOAD
to hack
I believe I tried that. IIRC, that does successfully result in dns
lookups returning fqdn's containing our domain suffix.
But what I'm trying to accomplish isn't DNS-based. Rather, I'm trying
to make "hostname -f" in a pod return a fqdn that contains our domain
suffix. IIUC, "hostname -f"
On 2017-09-05 11:08 pm, Quinn Comendant wrote:
Perhaps use a wrapper for hostname that returns a simulated hostname
if called from your special program:
#!/bin/bash
if [[ $(ps -o comm= $PPID) == '/your/app/here' ]]; then
echo "imitation.hostname.ourdomain.com"
else
/bin/hostname "$@"
fi
On 2017-09-05 6:19 pm, 'Tim Hockin' via Kubernetes user discussion and
Q wrote:
We do not have a mechanism to express what you want to express, then.
You control the cluster suffix and the subdomain, and the pod name,
but even with all of those in play, the hostname comes out as
`..svc.`, I am
This is set via the `--cluster-domain` flag on the kubelet, as well as in
the kubedns deployment.
/MR
On Tue, Sep 5, 2017 at 10:17 PM David Rosenstrauch
wrote:
> On 2017-09-05 5:39 pm, Matthias Rampke wrote:
> > If it's checking the domain suffix, everything should work if
Perhaps use a wrapper for hostname that returns a simulated hostname if called
from your special program:
#!/bin/bash
if [[ $(ps -o comm= $PPID) == '/your/app/here' ]]; then
echo "imitation.hostname.ourdomain.com"
else
/bin/hostname "$@"
fi
--
You received this message because you are
We do not have a mechanism to express what you want to express, then.
You control the cluster suffix and the subdomain, and the pod name,
but even with all of those in play, the hostname comes out as
`..svc.`, I am pretty sure. I am open to
proposals on how to allow what you want.
On Tue, Sep 5,
On 2017-09-05 5:39 pm, Matthias Rampke wrote:
If it's checking the domain suffix, everything should work if you set
the cluster domain to a subdomain of yours instead of cluster.local
– then the name will be of the form
..pod.., no? We use this in all our
clusters, but we make a custom
On 2017-09-05 5:04 pm, Brandon Philips wrote:
That won't do what he wants, I don't think.
$ kubectl run -i -t busybox --image=busybox --restart=Never -n
team-tectonic --overrides='{ "apiVersion": "v1", "spec": {"hostname":
"hello", "subdomain": "example"}}'
If you don't see a command prompt,
We don't have any mechanism to set the FQDN, other than this, for now.
On Tue, Sep 5, 2017 at 2:04 PM, Brandon Philips
wrote:
> That won't do what he wants, I don't think.
>
> $ kubectl run -i -t busybox --image=busybox --restart=Never -n team-tectonic
>
If it's checking the domain suffix, everything should work if you set the
cluster domain to a subdomain of yours instead of cluster.local – then the
name will be of the form ..pod.., no? We
use this in all our clusters, but we make a custom distribution, so how to
do this will depend on how you
That won't do what he wants, I don't think.
$ kubectl run -i -t busybox --image=busybox --restart=Never -n
team-tectonic --overrides='{ "apiVersion": "v1", "spec": {"hostname":
"hello", "subdomain": "example"}}'
If you don't see a command prompt, try pressing enter.
/ # hostname -f
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-records-and-hostname-based-on-pods-hostname-and-subdomain-fields
?
On Tue, Sep 5, 2017 at 1:41 PM, David Rosenstrauch wrote:
> Is it possible to make Kubernetes assign fully-qualified domain names to
>
Is it possible to make Kubernetes assign fully-qualified domain names to
pods at launch? I know Docker supports this using the "-h" flag (e.g.,
"docker run -h host1234.ourdomain.com ...") but I don't see a
corresponding way to trigger that functionality in containers launched
by k8s.
We
20 matches
Mail list logo