[kubernetes-users] Re: gcloud --node-taints issue

[rrm via Kubernetes user discussion and Q]

There is a note at the top of the page containing a link with instructions for 
enabling the v1beta1 API surface:

Note: This feature uses gcloud beta commands. To use gcloud beta commands, you 
must configure gcloud to use the v1beta1 API

On Thursday, November 2, 2017 at 1:56:28 PM UTC-7, randal.d...@monsanto.com 
wrote:
> I am trying to taint nodes in a gke node pool similar to this:
> 
>   gcloud beta container node-pools create pool-node --cluster cgs 
> --machine-type n1-standard-16 --node-labels 'capability=impute' --tags impute 
> --num-nodes 1 --preemptible --enable-autoscaling 
> --node-taints=reserved=impute:NoSchedule --max-nodes=50
> 
> I can use kubectl to mark them tainted - similar to something I found in the 
> news group
> 
>  kubectl taint nodes -l capability=impute reserved=impute:NoSchedule
> 
> But I was thinking the documentation implied that --node-taints would take 
> care of this. Is this an issue with the scaling or preemptible option? Is 
> this the correct way to use this feature?
> 
> Thanks in advance
> rdm

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

[kubernetes-users] Launching a new pod within a worker

['Axel Magnuson' via Kubernetes user discussion and Q]

Hi All,


I am considering using Kubernetes for an application that would require 
worker pods to spawn additional (custom) docker containers that have 
runtime parameters set by the worker. Ideally, these additional containers 
would be added to the existing container's pod. At the very least, the new 
containers should be co-located on the same physical node. However, I have 
so far failed to find any documentation on how to accomplish this (under 
either of my constraints).

   - Is this a use case that Kubernetes supports?
   - If so, what would be the best way to accomplish this?
   - Where can I find documentation on this subject?

Many thanks in advance. I am new to Kubernetes and have been striking out 
in my search.

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

[kubernetes-users] How to authenticate to a Kubernetes cluster created on AWS w/ kops

[bg]

I have several Kubernetes cluster on GKE, and recently created a cluster on 
AWS. When working against a GKE cluster, I run this command:

gcloud container clusters get-credentials my-cluser --zone us-central1-a --my 
project

I'd like to know how I should be authenticating with a kubernetes cluster on 
AWS provided I created the cluster with kops.

I notice that the cluster and the context were added to my ~/.kube/config file, 
presumably in the `kops create cluster` or the `kops update cluster` commands.

More specifically, I ask this because I have a CI server that is responsible 
for authenticating against a cluster and new deploying new version of 
deployments, so I need to find a way to make this very automated.

Thanks in advance!

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

[Rodrigo Campos]

Cool. Take into account that daemon set it is created to guarantee having
exactly one pod per node. For example, if you had more nodes, more pods for
a daemonset will be added. And the same if some crash or you reduce.

If that fits better what you want (sorry I didn't understood before), then
don't hesitate to use that. It should be really similar to a deployment
(the pod spec is the same, etc.)

On Tuesday, December 5, 2017,  wrote:

> As I said before, using multiple times the command "kubectl apply -f
> my-deployment.yaml" (changing from time to time the image version inside
> the yaml) I noticed that Kubernetes never deploys 2 pod in a same node.
> I tested this behavior many times so yes it's working as I need :)
> If I had problems I would use (as an emergency plan) the Daemon Set as you
> advised me
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" 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" 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.

Re: [kubernetes-users] Auth info "user" doesn't exist

[Simone D'Andreta]

I thought so, but the error message is not very clear so I was guessing 
that perhaps the parameters' names have changed between 1.3 and 1.5 but I 
couldn't find any proof of that in the docs.
The reason why I was going to upgrade my client is that with v 1.3. I hit a 
configmap limit, Too long: must have at most 262144 characters
. So I researched and found out that the issue was solved with 1.5 
version.. I guess I need to find a way to split the configmaps into 
smallest ones.. any suggestions?
Thank you,
Simone


Il giorno martedì 5 dicembre 2017 14:06:19 UTC+1, Peter Idah ha scritto:
>
> Hi Simone,
>
> Ah yes it's probably a client/server version issue; quoting the versioning 
> design docs – "a client should be skewed no more than one minor version 
> from the master, but may lead the master by up to one minor version. For 
> example, a v1.3 master should 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
>
> On Tue, Dec 5, 2017 at 12:29 PM, Simone D'Andreta  > wrote:
>
>> Hi Peter,
>> the user is present in my local kubeconfig file, I use it also to connect 
>> to other clusters.
>> I am pretty sure the user is properly set in the API server, as it is 
>> working fine with older versions of kubectl client.
>> Also note that the application is not using any kubeconfig file, but 
>> reading the parameters from the command line. 
>> Could it be that 1.5 client version has some incompatibilities with 1.3 
>> server version?
>> Thanks for your reply,
>> Simone 
>>
>> Il giorno martedì 5 dicembre 2017 13:18:12 UTC+1, Peter Idah ha scritto:
>>>
>>> Hello Simone,
>>>
>>> the --user flag refers to the name of the kubeconfig user you want to 
>>> use, i.e the user needs to be set in your kubeconfig file.
>>>
>>> Take a look at your local kubeconfig file (by default it should be here  
>>> ~/.kube/config) and see if you can find the user `user` or run this command 
>>> to list currently configured users –
>>>  kubectl config view -o json | jq -r '.users[].name' 
>>>
>>> Rgds,
>>> Peter
>>>
>>> On Tue, Dec 5, 2017 at 10:41 AM, Simone D'Andreta  
>>> wrote:
>>>
 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 output is this error:

 error: auth info "user" does not exist

 I can reproduce the same error locally, that means if I run the same 
 command against the same server from my laptop, I get the same error.

 Note that this works fine with versions 1.4 and below. 
 The server version is 1.3.

 Thanks for helping me here.

 Simone


 -- 
 You received this message because you are subscribed to the Google 
 Groups "Kubernetes user discussion and Q" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to kubernetes-use...@googlegroups.com.
 To post to this group, send email to kubernet...@googlegroups.com.
 Visit this group at https://groups.google.com/group/kubernetes-users.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Sign-up  to receive updates on my upcoming 
>>> book – DevOps 101  now! – 
>>> http://www.DevOps101.com 
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Kubernetes user discussion and Q" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to kubernetes-use...@googlegroups.com .
>> To post to this group, send email to kubernet...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Sign-up  to receive updates on my upcoming 
> book – DevOps 101  now! – 
> http://www.DevOps101.com 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

Re: [kubernetes-users] Auth info "user" doesn't exist

[Peter Idah]

Hi Simone,

Ah yes it's probably a client/server version issue; quoting the versioning
design docs – "a client should be skewed no more than one minor version
from the master, but may lead the master by up to one minor version. For
example, a v1.3 master should 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

On Tue, Dec 5, 2017 at 12:29 PM, Simone D'Andreta  wrote:

> Hi Peter,
> the user is present in my local kubeconfig file, I use it also to connect
> to other clusters.
> I am pretty sure the user is properly set in the API server, as it is
> working fine with older versions of kubectl client.
> Also note that the application is not using any kubeconfig file, but
> reading the parameters from the command line.
> Could it be that 1.5 client version has some incompatibilities with 1.3
> server version?
> Thanks for your reply,
> Simone
>
> Il giorno martedì 5 dicembre 2017 13:18:12 UTC+1, Peter Idah ha scritto:
>>
>> Hello Simone,
>>
>> the --user flag refers to the name of the kubeconfig user you want to
>> use, i.e the user needs to be set in your kubeconfig file.
>>
>> Take a look at your local kubeconfig file (by default it should be here
>> ~/.kube/config) and see if you can find the user `user` or run this command
>> to list currently configured users –
>>  kubectl config view -o json | jq -r '.users[].name'
>>
>> Rgds,
>> Peter
>>
>> On Tue, Dec 5, 2017 at 10:41 AM, Simone D'Andreta 
>> wrote:
>>
>>> 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 output is this error:
>>>
>>> error: auth info "user" does not exist
>>>
>>> I can reproduce the same error locally, that means if I run the same
>>> command against the same server from my laptop, I get the same error.
>>>
>>> Note that this works fine with versions 1.4 and below.
>>> The server version is 1.3.
>>>
>>> Thanks for helping me here.
>>>
>>> Simone
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Kubernetes user discussion and Q" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to kubernetes-use...@googlegroups.com.
>>> To post to this group, send email to kubernet...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/kubernetes-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Sign-up  to receive updates on my upcoming
>> book – DevOps 101  now! –
>> http://www.DevOps101.com 
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" 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.
>



-- 
Sign-up  to receive updates on my upcoming book
– DevOps 101  now! – http://www.DevOps101.com


-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

Re: [kubernetes-users] Auth info "user" doesn't exist

[Simone D'Andreta]

Hi Peter,
the user is present in my local kubeconfig file, I use it also to connect 
to other clusters.
I am pretty sure the user is properly set in the API server, as it is 
working fine with older versions of kubectl client.
Also note that the application is not using any kubeconfig file, but 
reading the parameters from the command line. 
Could it be that 1.5 client version has some incompatibilities with 1.3 
server version?
Thanks for your reply,
Simone 

Il giorno martedì 5 dicembre 2017 13:18:12 UTC+1, Peter Idah ha scritto:
>
> Hello Simone,
>
> the --user flag refers to the name of the kubeconfig user you want to use, 
> i.e the user needs to be set in your kubeconfig file.
>
> Take a look at your local kubeconfig file (by default it should be here  
> ~/.kube/config) and see if you can find the user `user` or run this command 
> to list currently configured users –
>  kubectl config view -o json | jq -r '.users[].name' 
>
> Rgds,
> Peter
>
> On Tue, Dec 5, 2017 at 10:41 AM, Simone D'Andreta  > wrote:
>
>> 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 output is this error:
>>
>> error: auth info "user" does not exist
>>
>> I can reproduce the same error locally, that means if I run the same 
>> command against the same server from my laptop, I get the same error.
>>
>> Note that this works fine with versions 1.4 and below. 
>> The server version is 1.3.
>>
>> Thanks for helping me here.
>>
>> Simone
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Kubernetes user discussion and Q" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to kubernetes-use...@googlegroups.com .
>> To post to this group, send email to kubernet...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Sign-up  to receive updates on my upcoming 
> book – DevOps 101  now! – 
> http://www.DevOps101.com 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

Re: [kubernetes-users] Auth info "user" doesn't exist

[Peter Idah]

Hello Simone,

the --user flag refers to the name of the kubeconfig user you want to use,
i.e the user needs to be set in your kubeconfig file.

Take a look at your local kubeconfig file (by default it should be here
~/.kube/config) and see if you can find the user `user` or run this command
to list currently configured users –
 kubectl config view -o json | jq -r '.users[].name'

Rgds,
Peter

On Tue, Dec 5, 2017 at 10:41 AM, Simone D'Andreta  wrote:

> 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 output is this error:
>
> error: auth info "user" does not exist
>
> I can reproduce the same error locally, that means if I run the same
> command against the same server from my laptop, I get the same error.
>
> Note that this works fine with versions 1.4 and below.
> The server version is 1.3.
>
> Thanks for helping me here.
>
> Simone
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" 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.
>



-- 
Sign-up  to receive updates on my upcoming book
– DevOps 101  now! – http://www.DevOps101.com


-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

[kubernetes-users] Auth info "user" doesn't exist

[Simone D'Andreta]

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 output is this error:

error: auth info "user" does not exist

I can reproduce the same error locally, that means if I run the same 
command against the same server from my laptop, I get the same error.

Note that this works fine with versions 1.4 and below. 
The server version is 1.3.

Thanks for helping me here.

Simone


-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.

Re: [kubernetes-users] How to force Kubernetes to update deployment with a pod in every node

[mderosa83]

As I said before, using multiple times the command "kubectl apply -f 
my-deployment.yaml" (changing from time to time the image version inside the 
yaml) I noticed that Kubernetes never deploys 2 pod in a same node. 
I tested this behavior many times so yes it's working as I need :)
If I had problems I would use (as an emergency plan) the Daemon Set as you 
advised me

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" 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.