hould work with v1.1, v1.2, and v1.3 nodes, and
> should work with v1.2, v1.3, and v1.4 clients."
>
>
> https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew
>
> Rgds,
> Peter
>
>
nfigured users –
> kubectl config view -o json | jq -r '.users[].name'
>
> Rgds,
> Peter
>
> On Tue, Dec 5, 2017 at 10:41 AM, Simone D'Andreta <simone@gmail.com
> > wrote:
>
>> Hello,
>> I have a weird issue happening with Kubectl client version 1.
Hello,
I have a weird issue happening with Kubectl client version 1.5 and above. I
have a docker app which runs a script that execute the following line:
kubectl --server=https://internal-elb-aws...(hidden..)
--certificate-authority=ca.pem --user=user --token=hidden get namespaces
and the
an try, if this is only for a POC and not will be used
> in the final solution, is using postStart hook that just overrides/appends
> to /etc/resolv.conf.
>
> This las option might be more hackish but easier to just try.
>
> On Wednesday, September 27, 2017, Simone D'Andreta <s
uted doesn't seem supported. Not sure it's something useful
> besides your setup, either :-/
>
> You can probably patch kubedns or something, but not sure it's worth the
> effort.
>
> On Wednesday, September 27, 2017, Simone D'Andreta <simone@gmail.com
&g
external will help.
>
> As not even able to ping, not sure what you mean. The service has nothing
> to do with the domain you want to ping, right? Or is that a typo?
>
> On Tuesday, September 26, 2017, Simone D'Andreta <simone@gmail.com
> > wrote:
>
>> It creates r
> guess something like that might be possible to do. And use different
> domains on apps that need to query different consul clusters?
>
> On Tuesday, September 26, 2017, Simone D'Andreta <simone@gmail.com
> > wrote:
>
>> I am afraid it won't work. I will be able
..
Il giorno martedì 26 settembre 2017 10:21:13 UTC+2, Simone D'Andreta ha
scritto:
>
> Hi Rodrigo,
> ideally we would need this per pod, but I can give it a try with creating
> a service per namespace.
> Thanks for the hint, I will let you know how it goes.
> Simone
>
k?
>
> On Monday, September 25, 2017, Simone D'Andreta <simone@gmail.com
> > wrote:
>
>> I need to be able to overwrite the resolv.conf per pods. If I tweak the
>> kube-dns configmap, I will have additional nameservers per node, not per
>> pods.
>>
Without seeing the error that is a wild guess. I
> can't stop you from doing this, but I strongly encourage you to
> re-read and internalize what I wrote about multiple nameserver
> records.
>
> On Fri, Sep 22, 2017 at 6:19 AM, Simone D'Andreta
> <simone@gmail.com >
servers in parallel, and
> take the first response. If one resolver can answer a query and
> another can't (NXDOMAIN), your app will sometimes get an address and
> will sometimes fail. This actually happens.
>
>
> On Thu, Sep 21, 2017 at 6:33 AM, Simone D'Andreta
>
Bad news, my idea doesn't work. Could you explain me more about the
volumeMount? I know how to mount but I don't know how I can effectively add
a nameserver on that file.
Thanks
Simone
Il giorno giovedì 21 settembre 2017 10:26:48 UTC+2, Simone D'Andreta ha
scritto:
>
> Hi Tim,
&g
what
> would happen if you tried to volumeMount a file over /etc/resolv.conf
> - might be worth a shot.
>
> On Wed, Sep 20, 2017 at 3:15 AM, Simone D'Andreta
> <simone@gmail.com > wrote:
> > Hello,
> > I wanted to know if there is a way to override DNS settin
Hello,
I wanted to know if there is a way to override DNS settings for pods (not
per cluster). I tried to use HostAliases but it only creates an A record
for that entry. I basically need a NS record cause I need to point to
different Consul clusters and then Consul must be able to do service
14 matches
Mail list logo
