Re: [kubernetes-users] Kubernetes memory leak on Master node.

[Rodrigo Campos]

It seems newer versions fixed a leak. Don't know which component is that is
leaking for you, though.

But, for example, this is one that have been fixed in a newer version:
https://github.com/kubernetes/kubernetes/pull/65339

See the changelog here for all 1.10.x minors:
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.10.md

If anything seems like your case, I'd try upgrading. But please let us know
if it's fixed in released versions or not yet :-)

On Friday, September 14, 2018, Yakov Sobolev  wrote:

> We are running Kubernetes 1.10.2 and we noticed memory leak on the master
> node. It is known issue? What is the remedy?
> We are running several clusters on VMs and confirmed memory leak on all of
> them. Only out-of-the box components are running on master nodes.
>
> --
> 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] Kubernetes Engine ImagePullBackOff for all images across all clusters

[Rodrigo Campos]

Can you pull from your laptop? Are you sure GKE is the problem? I'd try to
isolate that, first. If GKE is the problem, probably a ticket to Google
support may help.

If not, maybe the repository cleans old images, etc. Have you tried others
images? Other repos? Etc, etc.


On Tuesday, September 11, 2018, Blake Acheson 
wrote:

> Kubernetes engine cannot pull any images from the container registry.
> Receiving the error "unknown blob".
>
> This is happening on services that haven't been changes in months. Started
> at 9pm ET.
>
> --
> 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] one cluster for all, or one for PROD or other for QA/UAT

[Rodrigo Campos]

It has been asked several times, there are really lengthy answers with
different trade offs.

I use different, I value testing Kubernetes upgrades in my stag/qa envs.

On Monday, August 27, 2018, Gabriel Sousa 
wrote:

> hello
>
> what is the best ?
> one kubernetes cluster for all env ?
> or seperate PROD of UAT/QA ?
>
> --
> 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] If Master Nodes fails on Multi Master HA Setup then will the new jobs runs on the failed Master's worker node.

[Rodrigo Campos]

What do you mean with "those jobs"? Which ones?

Multi-master avoids having a problem if a master fails (or repairs quickly
the situation), so I'd say yes.

It also depends on how you manage etcd, to have concensus and that stuff.
But yeah, it won't be an issue

On Monday, August 27, 2018, Basanta Kumar Panda 
wrote:

> Hi,
> Few Clarifications on the HA setup on K8S Multi Master setup.
> Just want to know what will happens to the Worker nodes of the Master
> which failed due to the some reason .
> will jobs runs on those worker nodes through another Master node.
>
>
> Regards,
> Basanta
>
> --
> 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] kubelet + containers health check frequency

[Rodrigo Campos]

Do you mean the liveness check? Sure, see the docs. IIRC, it's there :)

If a pod crashes, it will be restarted immediately, I think.

On Tuesday, August 21, 2018, Aymen  wrote:

> Hello All,
>
> I'm trying to reduce kubernetes reaction time in case of a pod or
> container failure (container process crash)
>
> I'm wondering if it is possible to reduce the frequency used for kubelet
> to check that containers are running and healthy
>
> Cheers,
> Aymen
>
> --
> 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] Save the kubernetes container logs on the host node where the pod is deployed.

[Rodrigo Campos]

You can write to stdout and see the logs of the crashed container with
kubectl logs (or kubectl logs --previous or something like that was the
flag called).

Usually writing to stdout is a good practice:-)

On Monday, August 20, 2018, Ashish r  wrote:

> Hello all,
>
> I have implemented a 3 Master kubernetes cluster that works perfectly
> fine. I have been deploying some apps to test out the network. Assume I
> have deployed an application app1. There is only 1 replica of this pod on
> one of the kubernetes worker nodes. I am also writing the logs of the app
> to a file on the container . If for some reason, the container dies (the
> application service running inside the container died) the kubernetes
> master will bring up another pod/container. But I would like to view the
> logs of the container that has died so as to understand the root cause of
> the issue.
>
> I have give through this documentation but it only mentions about saving
> the log file on the container.
> https://kubernetes.io/docs/concepts/cluster-administration/logging/
> But I would atleast like to store it on my worker node or the master so
> that I do not loose the logs.
>
> I am looking for better ways of doing this. Any suggestion is highly
> appreciated and please let me know if I need to provide any additional
> information. Thanks in advance.
>
>
> Cheers,
> Ashish
>
> --
> 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] [Statefulset]Setting environment variables specific to each HOSTNAME loading from certain PATH mounted to container

[Rodrigo Campos]

On Friday, August 17, 2018, ilter P  wrote:

> Hi Rodrigo,
>
> Thanks for the reply
> First of all this is stable external image and I dont want to maintain my
> version.
> Secondly, the values that I would like to get are created during my
> deployment (ingress external host urls) and I can only map them during
> container initializing.
>
> What i tried in 1st option is trying to create environment variable with
> the value of executing the command $(eval cat )
>
> Here is the block I am trying in statefulset
> - name: KAFKA_ADVERTISED_LISTENERS
> value: INSIDE://$(POD_IP):9092,OUTSIDE://$(eval cat
> /opt/conf/ext-url):9093
>
>
So, it's the $(pod_ip) part working?
If so, why not have the file /opt/conf/ext-url be an env var? Is that file
coming from a configMap volume? Or how is it created?


> And ext-url is mounted via dynamic configMaps
> - name: cm-vol
> configMap:
>   name: kafka-0
>   items:
>   - key: kafka-ext-host
> path: ext-host
>

Why not use an env variable from the configMap? If that is what you want in
an env var, you can just have it. Instead of using it as a volume, use it
as an env var.

What am I missing?


>
> Note: I went to this direction after observing that reading from dynamic
> configMap is not working
> valueFrom:
> configMapKeyRef:
>   key: kafka-ext-host
>  name: $(POD_NAME) . --> Kubernetes giving error to here
>

Yeah, that won't work


>
> So the question is that, can I use "cat " command to environment
> variable ?
>

Not as part of the yaml. But if you have it mounted as the item you want,
you may just have it as an env var.

And if it's not the case, the hack I mentioned in my previous mail I think
should work.


>
> I hope it is little bit clear now :) Sorry for the mess
>

Thanks!

-- 
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] [Statefulset]Setting environment variables specific to each HOSTNAME loading from certain PATH mounted to container

[Rodrigo Campos]

Sorry, what is thing number 1 you tried? Is that in the yaml or where? Not
sure what you mean

As a hack, can't you change your docker file to do on startup (CMD): export
var=$(...); ./your-app ? Does it work?

Probably, he simplest thing might be for the app to read the proper
variable using it's host name. I think that would be the best, bit you can
try the hack above in the meantime or to experiment :-)

On Friday, August 17, 2018, ilter P  wrote:

> Hi,
>
> I have statefulset which has specific configuration for each host.
> I created different Configmap with each hostname and mounted them under
> the path with the hostnames as following:
> /$(HOSTNAME)/
> Now I need to pass this into a configuration file like:
>
> Variable inside the conf file**
>
> OUTSIDE://**
>
> *I tried following options:*
>
> *1- OUTSIDE://$(eval cat ) . --> did not work*
> *2- exported another env variable from initContainer --> did not work*
>
> *Is there a way to set environment variables by using a command as:*
> *- name: ENV_VARIABLE*
> *  valueFrom:*
> *command:*
> *  - sh*
> *  - export X=`cat `*
>
> *Please help*
>
> *Thanks*
>
> --
> 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] Is there a way to not start the pod creation if no slave nodes available to run the jobs .

[Rodrigo Campos]

This is probably related to "Build queue hangs after timer task error". It seems
he started a new thread now that he knows the reason of the jenkins build
hanging out.

But I might be wrong and may be something completely different.

Never used the Jenkins plugin, but I thought it created slaves on demand.
Probably it can be limited to some max amount. And I don't know how it bodes
with cluster-autoscaler, but depending your use case that can help too.

On Fri, Aug 10, 2018 at 09:35:34PM +, Agrawal, Punit wrote:
> +1 to Tims answer. Curious as to what are you trying to solve here ? Could 
> you explain your use case?
> 
> punit agrawal 
> dev-ops lead 
> new product development, ebay 
> 
> On 8/10/18, 2:31 PM, "'Tim Hockin' via Kubernetes user discussion and Q" 
>  wrote:
> 
> Well, we're not "starting" the pods, we're queuing them up for when
> nodes become available.  Would you rather they get rejected
> immediately?  what if a node comes online 3 seconds after that
> rejection?
> On Fri, Aug 10, 2018 at 2:28 PM Basanta Kumar Panda
>  wrote:
> >
> > Hi ,
> >
> > Here is one of the Scenario
> > 1. K8S Master is up with 2 slave nodes and is configured to jenkins 
> master.
> > 2. Both the slave nodes are down.
> > 3. Job triggered from jenkins and the job is waiting/hanging.
> >
> > bash-4.2kubectl get nodes
> > NAME   STATUS ROLES AGE   VERSION
> > Server1   Ready,SchedulingDisabled   34d   
> v1.9.1+2.1.5.el7
> > Server2   Ready,SchedulingDisabled   29d   
> v1.9.1+2.1.5.el7
> > Server3   Ready,SchedulingDisabled   master34d   
> v1.9.1+2.1.5.el7
> >
> > bash-4.2$ kubectl get pods -o wide -w
> > NAME READY STATUSRESTARTS   
> AGE   IPNODE
> > kube-lv7dz   0/1   Pending   0 0s
> > kube-lv7dz   0/1   Pending   0 0s
> > kube-lv7dz   0/1   Terminating   0 4m
> 
> > kube-lv7dz   0/1   Terminating   0 4m
> 
> > kube-7mztq   0/1   Pending   0 0s
> > kube-7mztq   0/1   Pending   0 0s
> >
> > Here pods are waiting to be scheduled on the slave nodes and since no 
> slave nodes are available, jobs are waiting/hanging.
> > is there a way to not start the pod creation as no nodes available to 
> run the jobs ?
> >
> > Regards,
> > Basanta
> >
> > --
> > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fgroup%2Fkubernetes-usersdata=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777sdata=XqT8%2BJyKObWAQQ83CWnPLAczjkaiamhK8%2BrVifpN%2B6g%3Dreserved=0.
> > For more options, visit 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptoutdata=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777sdata=pUxWISpiOReuO8SUYZ7q7k0LXAqjJ%2B0gkbcptXWgsWc%3Dreserved=0.
> 
> -- 
> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fgroup%2Fkubernetes-usersdata=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777sdata=XqT8%2BJyKObWAQQ83CWnPLAczjkaiamhK8%2BrVifpN%2B6g%3Dreserved=0.
> For more options, visit 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptoutdata=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777sdata=pUxWISpiOReuO8SUYZ7q7k0LXAqjJ%2B0gkbcptXWgsWc%3Dreserved=0.
> 
> 
> -- 
> 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 

Re: [kubernetes-users] Build queue hangs after timer task error

[Rodrigo Campos]

Oh, thanks to clarify  there was no way to guess that.

And can you see the logs on Kubernetes on why the pod is not created?
kubectl describe pod  at least?


On Friday, August 10, 2018, Basanta Kumar Panda 
wrote:

> Here is the scenario:
> Basically My Jenkin master is configured with K8S dynmic plugin and Mesos
> dynamic plugin .
> While running one of the mesos job .. job hanging because the pod creation
> is failing on mesos .. and on jenkins log I can see this error ..
>
> Aug 07, 2018 11:37:51 PM SEVERE hudson.triggers.SafeTimerTask run
> Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@7dffefc4
> failed
>  Now triggered few of the jobs to be executed on K8S Cluster  and all the
> jobs are hanging / waiting ..
> Killed mesos job  then K8S jobs started executing ..
> So is there any dependency with jenkins with the error pointed above..
>
>
> On Thursday, August 9, 2018 at 7:30:53 AM UTC+5:30, Rodrigo Campos wrote:
>>
>> Can you please elaborate?
>>
>> What job? How are you running it? I don't even understand how Kubernetes
>> is involved in this. Can you explain me more? I really don't follow
>>
>> On Wednesday, August 8, 2018, Basanta Kumar Panda 
>> wrote:
>>
>>> builds  of all other jobs hangs after timer task  error ..
>>> Aug 07, 2018 11:37:51 PM SEVERE hudson.triggers.SafeTimerTask run
>>> Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@7dffefc4
>>> failed
>>>
>>>
>>> On Wed, Aug 8, 2018 at 6:20 PM, Rodrigo Campos 
>>> wrote:
>>>
>>>> Can you please elaborate? What do you mean with build task?
>>>>
>>>>
>>>> On Wednesday, August 8, 2018, Basanta Kumar Panda 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Build queue hangs after timer task error is there any solution..
>>>>> Regards,
>>>>> Basanta
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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.
>>>>>
>>>> --
>>>> 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.
>>>>
>>>
>>> --
>>> 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.
>>>
>> --
> 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] Build queue hangs after timer task error

[Rodrigo Campos]

Can you please elaborate?

What job? How are you running it? I don't even understand how Kubernetes is
involved in this. Can you explain me more? I really don't follow

On Wednesday, August 8, 2018, Basanta Kumar Panda 
wrote:

> builds  of all other jobs hangs after timer task  error ..
> Aug 07, 2018 11:37:51 PM SEVERE hudson.triggers.SafeTimerTask run
> Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@7dffefc4
> failed
>
>
> On Wed, Aug 8, 2018 at 6:20 PM, Rodrigo Campos 
> wrote:
>
>> Can you please elaborate? What do you mean with build task?
>>
>>
>> On Wednesday, August 8, 2018, Basanta Kumar Panda 
>> wrote:
>>
>>> Hi,
>>>
>>> Build queue hangs after timer task error is there any solution..
>>> Regards,
>>> Basanta
>>>
>>>
>>>
>>> --
>>> 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.
>>
>
> --
> 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] How to monitor/alert on container/pod death or restart

[Rodrigo Campos]

It really depends on the monitoring solution. Usually this metrics are
exported and you can just predicate on them, in the language they provide.

In my case, I'm using a hosted solution (signalfx) that gives you a daemon
set and sends that metric to them. You can then predicate. We have alerts
when restarts increase significantly, the number of pods ready, cpu used on
average for each app, etc.

Does this help?

On Wednesday, August 8, 2018, David Rosenstrauch  wrote:

> As we're getting ready to go to production with our k8s-based system,
> we're trying to pin down exactly how we're going to do all the needed
> monitoring/alerting for it.  We can easily collect many of the metrics we
> need (using kube-state-metrics to feed into prometheus, and/or Datadog) and
> alert off of those.
>
> However, there's other important k8s-related info about our system that we
> need to be able to access, monitor, and alert on, most notably things like:
>
> * If a container crashes and is restarted by k8s
>
> * If k8s kills a container and restarts it (e.g., due to exceeding cpu or
> memory limits, or due to repeated failure of liveness check)
>
> * If k8s kills a container but cannot restart it
>
> * If an entire pod crashes and is restarted by k8s
>
> etc.
>
>
> How would would go about gaining access to those k8s-related events in an
> automated fashion, and setting up monitoring/alerting off of those?
>
> Thanks,
>
> DR
>
> --
> 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] Build queue hangs after timer task error

[Rodrigo Campos]

Can you please elaborate? What do you mean with build task?

On Wednesday, August 8, 2018, Basanta Kumar Panda 
wrote:

> Hi,
>
> Build queue hangs after timer task error is there any solution..
> Regards,
> Basanta
>
>
>
> --
> 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] pod migration if the node goes down

[Rodrigo Campos]

Feel free to search the documentation for the default values.

But in my experience, it was never an issue (we don't have one replica of
anything, though. So a single node going down is pretty tolerable)

On Monday, August 6, 2018, Niranjan Kolly  wrote:

> Hi MR,
>
> What about any application which are running(like nginx) , what if the
> node goes down and how quick master would spin those pods in the available
> nodes(for load distribution)
> How to tweak the timeout in the contol manager.
>
>
> Thanks,
> Niranjan
>
> On Mon, Aug 6, 2018 at 1:12 PM, 'Matthias Rampke' via Kubernetes user
> discussion and Q  wrote:
>
>> It takes a few minutes to declare a node lost, this is configurable via
>> kube-controller-manager flags.
>>
>> There are a few things you can do on a pod that prevents them being put
>> on the same node, such as declaring a hostPort.
>>
>> How will Cassandra react when a pod disappears and another one appears
>> (the is no "pod migration", only replacement)? I think this is a fairly
>> complex problem; research how others have solved this. A common pattern is
>> to name a thing that manages some technology in Kubernetes an Operator,
>> googling "cassandra operator kubernetes" I see several candidates but I
>> haven't used any so I can't say which one works best for you.
>>
>> /MR
>>
>> On Mon, Aug 6, 2018, 09:06 Niranjan Kolly 
>> wrote:
>>
>>> Hi,
>>>
>>> I have a K8 cluster with 3 master and 3 slave on centOS VM.
>>>
>>> we have installed KONG and cassandra with 3 replica each. As a part of
>>> the resiliency we brought down one node , but still the "kubectl get pods"
>>> command shows the pods running in that node showing up.
>>>
>>> As a K8 feature the master should spin the pods in the available node.
>>> How to do this configuration, but the master is not doing until we delete
>>> the pod manually.
>>>
>>> Please help me how to setup this.
>>>
>>>
>>> --
>>> Regards
>>> NiranjanKolly
>>>
>>> --
>>> 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.
>>
>
>
>
> --
> Regards
> NiranjanKolly
>
> --
> 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] Re: Getting data in and out of a job

[Rodrigo Campos]

I'm not sure what would work for you. A configmap created for that job only? Or
a secret, that can have binary data?

Or just an URL for input and log to stdout the output? Or use an S3 bucket for
input/output?

Not sure I understand the no cleanup part. If you want the output, then you want
the files in some place, right? So they can't be deleted until you processed or
something, at least. Sorry, but not sure I follow :)

On Fri, Aug 03, 2018 at 10:29:26AM -0700, Daniel Russel wrote:
> Hi-- Any good solutions for job input and output? I'm running into the same 
> problem and was looking at spinning up a temp minio (https://www.minio.io/) 
> instance (without persistent store) or something along those lines, but 
> simpler solutions would be nicer. Mostly the goal is to avoid having to 
> separately clean up data/persistent storage afterwards.
> 
> On Monday, May 21, 2018 at 8:55:17 PM UTC-7, bimar...@google.com wrote:
> >
> > I am setting up a go application that will create jobs. For each job 
> > execution, I need to pass a blob of parameter data into the job container, 
> > and get a blob back out. I'd like to avoid a requirement for database 
> > access in the job.
> >
> > Volumes seem awfully complicated, and, anyway, I don't see a 
> > straightforward way to get a files on and off of a GCE PD volume. I suppose 
> > I'm missing something simple, or that there's some other volume type that 
> > would be more appropriate.
> >
> 
> -- 
> 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] History of kubectl edit

[Rodrigo Campos]

Nope :-(

On Tuesday, May 22, 2018,  wrote:

> Hi,
>
> I recently a silly mistake of making some changes to a cluster via
> 'kubectl edit' without saving the previous states of the ingress I edited.
> Is there any location that old versions of objects are saved or the history
> of changes made so that I can revert the changes I made?
>
> Thanks,
> Karl
>
> --
> 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] Looking for service pool managing solution

[Rodrigo Campos]

Not sure it's simpler, nor what you mean with tags.

But yeah, you can create pods via the API, count, or use quota limits if
you prefer, too.

Let's simplify it: try and report back ;)

Seriously, I think that would be the easiest and fastest thing to do.

On Thursday, May 17, 2018,  wrote:

> Let's simplify it:
> can I write 5 different pod yamls, put in it a kind of "tag" and write an
> API request (request should have "tag" value) that will run ONE random pod
> from those 5?
>
> --
> 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] Looking for service pool managing solution

[Rodrigo Campos]

On Thursday, May 17, 2018,  wrote:

> So:
> I have 3 types of devices. Each device has assigned container - to access
> device you have to connect to container and from there you can use device.


What do you mean with device?


> Containers have special environment variable describing to which device it
> is assigned, e.g. B4 - which means: device type B, number 4.
>
> Now we are lending access to device by manually passing access to chosen
> container, but my need is to automate it: developer sends request: I need
> device type A. System checks if there is any resource available and gives
> access to developer. When developer is done, he sends request: ok, I'm
> done. Ramp down the container. And next user can request for it.


You can easily create pods based on a yaml. And use the Kubernetes API or
kubectl to create them or delete.

IIUC, that is what you need, right?

-- 
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] Looking for service pool managing solution

[Rodrigo Campos]

Can you please elaborate? I don't follow what you mean with "type A,
unique variable: xxx".

On Thu, May 17, 2018 at 12:35 PM,   wrote:
> Hi Rodrigo,
> I cannot find an example for one thing:
> Let's say I have 3 pods defined:
> type: A, unique_variable: 111
> type: A, unique_variable: 222
> type: A, unique_variable: 333
>
> Now: how can I use API or Kubectl to create random pod of type A?
>
>
> Kind regards,
> Tomasz
>
> --
> 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] Looking for service pool managing solution

[Rodrigo Campos]

For what I understand, yes. Go ahead and try it out and read the docs.

Each container/pod can specify it's requirements regarding could/mem, and
k8s will allocate them while they exist automatically on some node. Or you
can even make sure some containers/pods will be run on some type of nodes
(like the ones with SSD, etc.)

So, yes, it should. Have fun! :-)

On Thursday, May 17, 2018,  wrote:

> Greetings,
> I am looking for a software to manage a pool of application, using API and
> database system. Let me show You my problem:
> I have 3 types of services: A, B and C. Each one requires outside
> resource, so we distinguish each instance. e.g.: I have 6 A-type virtual
> machines { A1, A2,.., A6}, 3 B-type: {B1,B2,B3} and 10 C-type. Each
> instance has its own internal setup, mostly IPs to remote resources. Now I
> want my managing system to solve usecases:
> 1. One of Jenkinses (I could have few) needs to test something using
> A-type instance. He sends API request and gets details to about random from
> that type and uses it. When he is done, the instance isfreed and returned
> using API.
> 2. A software developers needs some manual tests and asks for C-type
> instance. He sends an API request and gets details on one of those
> instances.
> 3. Only one "user" (Jenkins or human) can be using given instance at any
> time.
> 4. I need to be able to check who/what is using any of the instances at
> any time (can also be API query).
> 5. There needs to be security logs - when who requested what, what he got
> in
> return.
>
>
> I am looking for a system to solve this problem, one of my Colleagues
> hinted me to use Kubernetes - since the "instance" can be containers with
> uniqe configuration it might be possible, but could anyone comment: does
> Kubernetes satisfies all my needs? Or maybe something else?
>
> --
> 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] Slow response times using default Ingress on GKE

[Rodrigo Campos]

For debug sake, I think it's better to confirm than to assume. And there
can be differences, for sure. But do what you want, of course :-)

On Friday, May 11, 2018, Dave Jensen <da...@jensen47.com> wrote:

> I attempted to file an issue but was denied because we're bronze for
> support. We are a Spark customer but I also cannot find a way to set up the
> 1:1 Office Hours.
>
> However, now that there is *at least* one other person having this issue
> (see Marshall above), I feel like it would be nice for this to be handled a
> public forum. It means there is a defect somewhere ... possibly a
> documentation defect.
>
> Rodrigo, if I'm not mistaken, I essentially accessed the service via
> NodePort when I portforwarded to the service. I have been trying to setup
> Contour as a Load Balancer with limited success.
>
> Manually setting up a load balancer on GCP is uh, seems like busy work
> that will result in the same setup. When I apply my ingress yaml, a GCP
> Load Balancer is created for me. I *could *copy all of those settings but
> then I'll just have a copy of the same setup.
>
> On Fri, May 11, 2018 at 1:50 PM 'Kenneth Massada' via Kubernetes user
> discussion and Q <kubernetes-users@googlegroups.com> wrote:
>
>> Dave, are you able to use our support center to file a case
>> https://cloud.google.com/support/, if you have already could you share
>> the number with us, I'll make sure we get someone to follow up.
>>
>>
>> On Friday, May 11, 2018 at 1:29:08 PM UTC-7, Rodrigo Campos wrote:
>>
>>> Have you tried what I suggested?
>>>
>>> Also, isn't it possible to open a ticket on google cloud support about
>>> gke? (Never used Google cloud, don't know if it's free or what)
>>>
>>> On Friday, May 11, 2018, Dave Jensen <djen...@gmail.com> wrote:
>>>
>> > Have you tried using the service nodeport? You can do that and send
>>>> traffic to one node, this will be round robin to all pods anyways. To see
>>>> if it happens too.
>>>>
>>>> I just tried a portforward to the service (instead of a single pod) and
>>>> it's blazing fast.
>>>>
>>>> Either the GCP LB is bad or the ingress-gce is bad. It's just super
>>>> frustrating because no matter what channel I take, there is no support. I
>>>> realize this is the Kubernetes mailing list but there is no dedicated GCP
>>>> mailing list all the GCP docs point here. Given our super simple setup ...
>>>> by following tutorials, something is wrong.
>>>>
>>>> On Tuesday, May 1, 2018 at 4:08:48 PM UTC-7, Dave Jensen wrote:
>>>>>
>>>>> Hello fa...,
>>>>>
>>>>> We followed the tutorial [3] and it technically works but it does not
>>>>> perform to expectations.
>>>>>
>>>>> Dave
>>>>>
>>>>> On Sunday, April 22, 2018 at 11:15:59 AM UTC-7, fa...@google.com
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hello Dave,
>>>>>>
>>>>>> Since your question is technical, you may get help from community
>>>>>> experts and enthusiasts at serverfault.com. Make sure you include
>>>>>> proper tags when you ask your question. For example, if using Google 
>>>>>> Cloud
>>>>>> Kubernetes Engine [1] you may tag it as [google-kubernetes-engine], and
>>>>>> [kubernetes]; but if using a Kubernetes cluster on Compute Engine, you 
>>>>>> may
>>>>>> tag it as [kubernetes], and [google-compute-engine].
>>>>>>
>>>>>> On the other hand, while I was checking the Ingress prerequisites
>>>>>> [2], I understood that “Google Kubernetes Engine deploys an ingress
>>>>>> controller on the master” for you, and like this tutorial [3] it creates
>>>>>> the load balancer. According to the prerequisites, and this github page
>>>>>> [4],  it is still in beta, and you may check the limitations and
>>>>>> expectations [5] with latency on the same page.
>>>>>> That said, and if you suspect a defect with the Ingress Controller/
>>>>>> Google Cloud Load Balancer you may open a report through issue tracker 
>>>>>> [6].
>>>>>> But after verifying the correct settings with the community, and 
>>>>>> reviewing
>>>>>> the above as not an expected behavior.  I hope that helps.
>>>>>>
>>>

Re: [kubernetes-users] Slow response times using default Ingress on GKE

[Rodrigo Campos]

Have you tried what I suggested?

Also, isn't it possible to open a ticket on google cloud support about gke?
(Never used Google cloud, don't know if it's free or what)

On Friday, May 11, 2018, Dave Jensen  wrote:

> > Have you tried using the service nodeport? You can do that and send
> traffic to one node, this will be round robin to all pods anyways. To see
> if it happens too.
>
> I just tried a portforward to the service (instead of a single pod) and
> it's blazing fast.
>
> Either the GCP LB is bad or the ingress-gce is bad. It's just super
> frustrating because no matter what channel I take, there is no support. I
> realize this is the Kubernetes mailing list but there is no dedicated GCP
> mailing list all the GCP docs point here. Given our super simple setup ...
> by following tutorials, something is wrong.
>
> On Tuesday, May 1, 2018 at 4:08:48 PM UTC-7, Dave Jensen wrote:
>>
>> Hello fa...,
>>
>> We followed the tutorial [3] and it technically works but it does not
>> perform to expectations.
>>
>> Dave
>>
>> On Sunday, April 22, 2018 at 11:15:59 AM UTC-7, fa...@google.com wrote:
>>>
>>>
>>> Hello Dave,
>>>
>>> Since your question is technical, you may get help from community
>>> experts and enthusiasts at serverfault.com. Make sure you include
>>> proper tags when you ask your question. For example, if using Google Cloud
>>> Kubernetes Engine [1] you may tag it as [google-kubernetes-engine], and
>>> [kubernetes]; but if using a Kubernetes cluster on Compute Engine, you may
>>> tag it as [kubernetes], and [google-compute-engine].
>>>
>>> On the other hand, while I was checking the Ingress prerequisites [2], I
>>> understood that “Google Kubernetes Engine deploys an ingress controller on
>>> the master” for you, and like this tutorial [3] it creates the load
>>> balancer. According to the prerequisites, and this github page [4],  it is
>>> still in beta, and you may check the limitations and expectations [5] with
>>> latency on the same page.
>>> That said, and if you suspect a defect with the Ingress Controller/
>>> Google Cloud Load Balancer you may open a report through issue tracker [6].
>>> But after verifying the correct settings with the community, and reviewing
>>> the above as not an expected behavior.  I hope that helps.
>>>
>>> [1] https://console.cloud.google.com/kubernetes
>>> [2] https://kubernetes.io/docs/concepts/services-networking/ingr
>>> ess/#prerequisites
>>> [3] https://cloud.google.com/kubernetes-engine/docs/tutorials/
>>> http-balancer
>>> [4] https://github.com/kubernetes/ingress-gce/blob/master/BETA_L
>>> IMITATIONS.md#glbc-beta-limitations
>>> [5] https://github.com/kubernetes/ingress-gce/blob/master/BETA_L
>>> IMITATIONS.md#latency
>>> [6] https://cloud.google.com/support/docs/issue-trackers
>>
>> --
> 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] AWS Multi-AZ node/pod spreading

[Rodrigo Campos]

On Wed, May 09, 2018 at 07:35:23AM -0700, a...@unbotify.com wrote:
> Hi all,
> 
> I'm building a K8s cluster with KOps. With 3 IGs, one in each AZ. Nodes are 
> automatically tagged with failure-domain tags - 
> e.g.```failure-domain.beta.kubernetes.io/region=us-east-1,failure-domain.beta.kubernetes.io/zone=us-east-1a```
>  and so for each AZ.
> I'v added the cluster-autoscaler with auto discovery based on:
> https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/examples/cluster-autoscaler-autodiscover.yaml
> 
> then created a few hundreds of dummy containers just to see it scale out, but 
> once it started scaling up the underlying ASG, it was completely uneven (one 
> ASG went to maximum and one other was added a couple of nodes, while the 
> third did nothing). Pods were distributed accordingly (this is a new cluster 
> so nothing else runs there).

I haven't used the cluster-autoscaler, so sorry if this doesn't really help. But
I think as a workarround (or might even be better for some scenarios), you can
just have one ASG (and on IG in kops, that matches that very same ASG).

But, the trick is to make that ASG/IG have several subnets, one in every AZ you
want. Then, the ASG (is documented by aws, not just by chance) will spread the
nodes it creates in the different AZs. And it will do it evenly. And if one AZ
fails, then it will move the nodes to another. And then if it recovers, it will
move the nodes again so it's even.

We are using that ASG feature (with kops) and it works fine.

And I guess that if you have only one ASG, cluster-autoscaler will only increase
the nodes numbers and AWS will do the spreding things as capacity is available
and that stuff.

-- 
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] Best practices for subversion updates on prod environment with kubernetes cluster in daemon set configuration

[Rodrigo Campos]

Adding Kubernetes users again :)

On Thursday, April 26, 2018, Rodrigo Campos <rodrig...@gmail.com> wrote:

> On Thursday, April 26, 2018, <mderos...@gmail.com> wrote:
>
>>
>> Il 25/04/2018 01:27, Rodrigo Campos ha scritto:
>>
>>> I don't understand why can that happen if the code is in the container
>>> image. Unless you change it while it is running, there should be no chance
>>> to misalign anything. What am I missing?
>>>
>>
>> We're working with continuous delivery approach so we would like to have
>> the chance to execute svn up on prod env without the obligation to create a
>> new image for every deploy
>
>
> Really different things, though.
>
> And, as I said in previous emails, you lose several advantages of
> immutability of containers.
>
> For example, we are using zendesk/samson (project on GitHub) and when a
> merge is done, Travis runs the tests and if they pass, a new docker image
> is created and it gets deployed via Samson.
> Automatically. And if something fails (like liveness probes or something)
> it rollbacks to the previous image.
> This is pretty much what containers deploy look like in the common case:
> your code is in the container. You just create new containers images.
>
> If you are managing all of this yourself, then you need to do it yourself
> and handle all these problems that other tools solve for you.
>

-- 
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] Best practices for subversion updates on prod environment with kubernetes cluster in daemon set configuration

[Rodrigo Campos]

On Tuesday, April 24, 2018, <mderos...@gmail.com> wrote:

> Il giorno lunedì 23 aprile 2018 16:52:20 UTC+2, Rodrigo Campos ha scritto:
> > Sorry, there are different parts that I don't follow. Why daemon set?
>
> No problem.
> So why daemon set? Because I have a cluster with 6 nodes (but in the
> future this number could be greater) and to ensure that every node will
> contain a single pod I use a daemonset deploy (as you advised me in this
> discussion: https://groups.google.com/forum/#!topic/kubernetes-
> users/t1cR-v6NCpM)


Okay, if you are sure about that, then it seems fine. Just checking =)


> And fundamentally why not rebuild ok SVN changes? You can automate that.
> Take into account that if you don't have different images with the code,
> you can't use Kubernetes to rollback either. Or you should check in some
> other way which pod had which svn revision at any moment in time, and also
> handle if an SVN up fails or fails in some pods only. OIW, it can add more
> problems than it solves to do that, consider it carefully.
>
> To be honest I don't think that automate svn updates is a reliable
> solution.
> Let me give an example:
> - I commit some file --> revision 123 and I have to deploy those changes
> on prod
> - I create a docker image where I update the code to revision 123
> - Then I deploy the image with a rolling update to kubernetes cluster
> - In the following days I work to the code, committing the files to make
> them available to the team. Now the svn revision is 200. But a deploy on
> prod is not scheduled
> - For a memory problem, on prod env, kubernetes kills a pod and restarts
> it automatically. If any automatic code update mechanism is activated when
> the pod is started, it will lead to the situation where a pod will have
> code of revision 200 and all the others will remain to revision 123


Exactly. But that will only happen if you manage SVN files outside of the
docker build. As long as the container files are contained there, this
can't happen. This is exactly why I was advising not to manage files
updates outside of the container.

Or am I missing something?



> > That being said, you can use a sidecar container to update the SVN code
> in a shared volume. That sounds like a good approach (in most Kubernetes
> examples shown with a webserver and git, but it's the same). And you should
> be able to handle restarts and that stuff fine.
>
> In fact from what I have read on the internet this approach should be the
> most correct solution.
> The question is: do I have to create a single persistent disk that will be
> mounted (read only I assume) on every pod (via daemonset.yml) ?
> Or is it possible to create one persistent disk for every pod, where each
> one is mounted on a single pod in r/w mode?


Why not an emptydir?

-- 
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] Best practices for subversion updates on prod environment with kubernetes cluster in daemon set configuration

[Rodrigo Campos]

Sorry, there are different parts that I don't follow. Why daemon set?

And fundamentally why not rebuild ok SVN changes? You can automate that.
Take into account that if you don't have different images with the code,
you can't use Kubernetes to rollback either. Or you should check in some
other way which pod had which svn revision at any moment in time, and also
handle if an SVN up fails or fails in some pods only. OIW, it can add more
problems than it solves to do that, consider it carefully.

That being said, you can use a sidecar container to update the SVN code in
a shared volume. That sounds like a good approach (in most Kubernetes
examples shown with a webserver and git, but it's the same). And you should
be able to handle restarts and that stuff fine.

On Monday, April 23, 2018,  wrote:

> Thanks for these suggestions!
> But do these solutions use persistent disk?
> In my case the persistent disk is a necessary requirement because in
> certain rare situations the pods restart. Therefore it is necessary to use
> a persistent disk so that the code does not change in case of reboot..
>
> Just to clarify the scenario under analysis:
> - the image that I'm using is a debian with svn installed and configured
> - so inside the image there is all my project code (besides apache, php,
> etc)
> - after a deploy I could execute a 'svn update' on every pod (using a
> multi-terminals app like Terminator) but the problem is that if a pod
> restarts, the code will return to the original revision when the image was
> created
>
> So I'm searching a solution where I could use a daemonset configuration
> with a hostPath section where to indicate, in some way, a persistent disk
> (previously created) and the path where to mount it
>
> --
> 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] Kubernetes Lifecycle Hooks

[Rodrigo Campos]

Can someone ban this? Or what is the proper procedure to follow?

Thanks!

On Tuesday, April 17, 2018, Sunil Bhai  wrote:

> Pls check this repo
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> https://github.com/waterplaclid/k8s-podmon.git
>
> On Tuesday, April 17, 2018 at 2:17:00 AM UTC+5:30, gei...@gmail.com wrote:
>
>> I would like to take particular actions when a K8 Pod, or the node its
>> running on, crashes/restarts/etc -- basically notify another part of the
>> application that this has happened. I also need this to be guaranteed to
>> execute. Can a kubernetes PreStop hook accomplish this? From my
>> understanding, these are generally used to gracefully shutdown containers
>> when a pod is deleted and the hook handler is guaranteed to run. It seems
>> like most people use them in scenarios where they are shutting things down
>> themselves.
>>
>> Will the hooks also run when a node unexpectedly crashes? If not, is
>> there a kubernetes solution for what I'm trying to accomplish?
>>
>> --
> 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] Kubernetes Lifecycle Hooks

[Rodrigo Campos]

IIUC, no.

Node crashes will not execute a preStop hook and there is no way for
Kubernetes to guarantee that.

But what are you trying to solve, really?
Or, in other words, how would you solve it without Kubernetes? Probably the
same solution applies to Kubernetes?

On Monday, April 16, 2018,  wrote:

> I would like to take particular actions when a K8 Pod, or the node its
> running on, crashes/restarts/etc -- basically notify another part of the
> application that this has happened. I also need this to be guaranteed to
> execute. Can a kubernetes PreStop hook accomplish this? From my
> understanding, these are generally used to gracefully shutdown containers
> when a pod is deleted and the hook handler is guaranteed to run. It seems
> like most people use them in scenarios where they are shutting things down
> themselves.
>
> Will the hooks also run when a node unexpectedly crashes? If not, is there
> a kubernetes solution for what I'm trying to accomplish?
>
> --
> 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] ClusterIP service not distributing requests evenlyamong pods in Google Kubernetes Engine

[Rodrigo Campos]

And how are you running the requests? Against which IP and which port?

On Fri, Apr 13, 2018 at 10:17:04AM -0700, cristian.coch...@gmail.com wrote:
> 
> OK, I changed my pods to respond almost immediately so that I can test with a 
> statistically significant number of requests (10,000), and I am still 
> observing the same behavior, only 1 pod receives all 10k requests. Can anyone 
> explain why this happens? I am including the service and deployment manifests 
> below:
> 
> cpp-btm-calculator-svc.yaml:
> 
> apiVersion: v1
> kind: Service
> metadata:
>   labels:
> app: cpp-btm-calculator
>   name: cpp-btm-calculator
> spec:
>   ports:
>   - port: 3006
> protocol: TCP
> targetPort: 3006
>   selector:
> app: cpp-btm-calculator
>   sessionAffinity: None
>   type: ClusterIP
> 
> 
> cpp-btm-calculator-depl.yaml:
> 
> 
> apiVersion: apps/v1beta1
> kind: Deployment
> metadata:
>   labels:
> app: cpp-btm-calculator
>   name: cpp-btm-calculator-depl
> spec:
>   replicas: 4
>   selector:
> matchLabels:
>   app: cpp-btm-calculator
>   strategy:
> rollingUpdate:
>   maxSurge: 1
>   maxUnavailable: 1
> type: RollingUpdate
>   template:
> metadata:
>   labels:
> app: cpp-btm-calculator
> spec:
>   containers:
>   - image: us.gcr.io/my-project/cpp-btm-calculator:v1.1.2
> name: cpp-btm-calculator
> imagePullPolicy: IfNotPresent
> resources: {}
> env:
>   - name: PORT
> value: "3006"
>   - name: LOG_CONFIG
> value: cpp-btm-calculator-logging.config
> 
> 
> 
> > > 
> > > On Friday, April 13, 2018 at 10:59:46 AM UTC-4, Tim Hockin wrote:
> > > > Without a statistically significant load, this is random.  What you are 
> > > > seeing satisfies that definition.
> > > > 
> > > > 
> > > > The real reason is that round-robin is a lie.  Each node in a cluster 
> > > > will do it's own RR from any number of clients.
> > > >
> 
> -- 
> 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] ClusterIP service not distributing requests evenly among pods in Google Kubernetes Engine

[Rodrigo Campos]

Why are obviously not evenly distributed? How are pods asgined to nodes?

And also, how do you noticed, exactly, that they are not "evenly
distributed"?

On Friday, April 13, 2018,  wrote:

>
> I have a ClusterIP service in my cluster with 4 pods behind it. I noticed
> that requests to the service are not evenly distributed among pods. After
> further reading I learned that the kube-proxy pod is responsible for
> setting up the iptables rules that forward requests to the pods. After
> logging into the kube-proxy pod and listing the nat table rules, this is
> what I got:
>
> Chain KUBE-SVC-4F4JXO37LX4IKRUC (1 references)
> target prot opt source   destination
> KUBE-SEP-6X4IVU3LDAAZJUPD  all  --  0.0.0.0/00.0.0.0/0
> /* default/btm-calculator: */ statistic mode random probability
> 0.250
> KUBE-SEP-TXRPWWIIUWW3MNFH  all  --  0.0.0.0/00.0.0.0/0
> /* default/btm-calculator: */ statistic mode random probability
> 0.282
> KUBE-SEP-HW6SF2LJM4S7X5ZN  all  --  0.0.0.0/00.0.0.0/0
> /* default/btm-calculator: */ statistic mode random probability
> 0.500
> KUBE-SEP-TTJKD52QZSH2OH4O  all  --  0.0.0.0/00.0.0.0/0
> /* default/btm-calculator: */
>
> The comments seem to suggest that the load is balanced according to the
> static mode random probability with an uneven probability distribution. Is
> this how it's supposed to work? Every piece of documentation that I read
> about load balancing by a ClusterIP service indicates that it should be
> round robin. Obviously this is not the case here.
> Is there a way to set a ClusterIP to perform round robin load balancing?
>
> Thank you,
> Cristian
>
> --
> 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] Kubernetes engine not cleaning up after itself (firewall rules + load balancers)

[Rodrigo Campos]

Have you tried deleting the services before and that stuff?

On Thursday, April 12, 2018,  wrote:

> When deleting deployments and clusters kubernetes engine is leaving behind
> a mess of orphaned load balancers and firewall rules.
>
> --
> 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] How to access LDAP server (not container) by application deployed in container

[Rodrigo Campos]

On Fri, Apr 06, 2018 at 04:56:11AM -0700, nvnvashi...@gmail.com wrote:
> Hello Experts,
> 
> I have my application running in docker swarm, where the application is using 
> the LDAP and MySQL server (not container) very well and everything is working 
> fine. Initially I had source file (config file PHP), which was used in order 
> to reach this LDAP server.
> 
> Now I would like to migrate all stuff over openshift (built over Kubernetes).
> 
> Does any have idea, how to access LDAP server (not container) from the 
> application (container)?

Just the way you were doint it before? If you can route, you should be able to
connect.

What is the issue you forsee?

-- 
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 can i configure a clusterIP ?

[Rodrigo Campos]

What docs have you follow and where it didn't work? So we can better guide
you

On Wednesday, April 4, 2018, Gabriel Sousa 
wrote:

> how can i configure a clusterIP ?
>
> --
> 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] independent custom kubernetes - best solution to Publish services ?

[Rodrigo Campos]

On Wed, Apr 04, 2018 at 09:33:28AM -0700, Gabriel Sousa wrote:
> 
> Now i know what i have to do, 
> 
> Create a cluster with 3 masters and will use pacemaker/virtual ip and use 
> nodeport to Publish services .

Really, can you please elaborate?

> 
> can i have only 3 masters without workers ?

Yes

-- 
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] Network Policy to limit open connections per pod

[Rodrigo Campos]

Just curious, but why not change the contrack limit?

On Wednesday, March 28, 2018,  wrote:

> Is there anything similar to a network policy that limits x open
> connections per pod?
>
> During a 100k TPS load test, a subset of pods had errors connecting to a
> downstream service and we maxed out the nf_conntrack table (500k) which
> affected the rest of the pods on each node that had this issue - which
> happened to be 55% of the cluster.
>
> Besides handling this at the application level, I wanted to protect the
> cluster as a whole so that not one deployment can affect the entire cluster
> in this manner.
>
> Thanks for any help.
>
> -Jonathan
>
> --
> 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] Access Kubernetes Dashboard ui from browser

[Rodrigo Campos]

On Tuesday, March 27, 2018, jw  wrote:

> I am new to K8S. Follow https://get.k8s.io/ created a Kubernetes cluster
> in Google cloud (gce instances). I tries to access dashboard UI from
> browser but without success. The cluster-info looks like this:
>
> kubectl cluster-info
> Kubernetes master is running at https://
> GLBCDefaultBackend is running at https:///api/v1/
> namespaces/kube-system/services/default-http-backend/proxy
> Heapster is running at https:///api/v1/namespaces/kube-system/
> services/heapster/proxy
> KubeDNS is running at https:///api/v1/namespaces/kube-system/
> services/kube-dns/proxy
> kubernetes-dashboard is running at https:///api/v1/
> namespaces/kube-system/services/kubernetes-dashboard/proxy
> Metrics-server is running at https:///api/v1/
> namespaces/kube-system/services/metrics-server/proxy
> Grafana is running at https:///api/v1/namespaces/kube-system/
> services/monitoring-grafana/proxy
> InfluxDB is running at https:///api/v1/namespaces/kube-system/
> services/monitoring-influxdb/proxy
>
> The Kubernetes version is 1.9. When I typed https:///ui on
> browser, I am getting:
>

Why this URL and not the one for Kubernetes dashboard that you posted some
lines above?

-- 
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] StatefulSets and availability zones in AWS

[Rodrigo Campos]

AWS also offers EFS volumes (https://aws.amazon.com/efs/) that are
basically NFS volumes that can be accessed within a region (so there should
be no problem if one AZ is down or whatever).

Pricing is quite different, but it might be a better fit as you don't need
to handle any of the complexity.

And regarding Kubernetes, you can use a NFS volume and that should do the
trick (NFS instead of EBS)

Also, please share your experience if you do try it :-)

On Friday, March 23, 2018, Vivek  wrote:

> Hey team,
>
> I have an application container that I wish to run on Kubernetes in an AWS
> environment, backed by EBS volumes.
>
> I’m currently thinking that the application will be created by a
> StatefulSet with a single PersistentVolume attached (EBS underlying).
>
> I had originally thought that if the AWS availability zone went down,
> Kubernetes would automatically spin up the node again in a different AZ,
> attaching to the same volume. That said, I then realized that EBS volumes
> only exist within the same AZ as the instance to which they are attached.
>
> From the AWS documentation, It seems the proper way to duplicate an EBS
> across AZs is to create a volume snapshot and then spin up another volume
> and attach that new volume to a new instance in another AZ.
>
> That said, I’m not sure if StatefulSets in Kubernetes have the necessary
> logic to accomplish this. Questions:
>
> - Is there a way that I can specify for StatefulSets to create a
> persistent volume from a snapshot in the event that the original volume
> does not exist for a pod?
> - Alternatively: does anyone see an easier architecture that I might opt
> for instead, given these application constraints?
>
> Disclaimer: I’m fairly new to Kubernetes, so I’m sure that I have made
> some obvious logic errors!
>
> Regards,
> Vivek
>
> --
> 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] What is kubernetes containers, nodes, services, and apps?

[Rodrigo Campos]

Have you tried the doc on the kubernetes website? It aims to explain
exactly that: https://kubernetes.io/docs/home/

But please don't hesitate to ask back whatever is not clear, or submit a PR
:-)


On Sunday, February 18, 2018,  wrote:

> I'm trying to get my head around kubernetes. I've been watching a few
> YouTube videos on what is kubernetes and they're mentioning things like
> containers, nodes, services, and apps but I still need  to understand what
> those are in relations to kubernetes. Any explanation, documentation,
> and/or videos show that what these are is much appreciated. I assumed
> kubernetes is gearing towards enterprise website versus personal or mom and
> pop business website, correct? When would I need to use kubernetes?
>
> --
> 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] Is it Possible to do MSSQL replication on Kubernetes?

[Rodrigo Campos]

I have never done it. But  vitess might be interesting, if it's not an
overkill for your scenario: http://vitess.io/

Let us know what you end up doing :)

On Tuesday, February 6, 2018,  wrote:

> Hi There!
>
> We need to do MSSQL replication on Kubernetes.
>
> I don't know whether K8s support this feature or not.
>
> If it is supported, Please show me the way to do.
>
> Thanks!!
>
> --
> 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] livenessProbe failed won't set pod status Ready=False

[Rodrigo Campos]

Oh, now I see.

But if you uncomment the readiness probe, even if the readiness probe has
an initial delay, it works as expected. Right?


On Sunday, February 4, 2018, Colstuwjx  wrote:

>
>> Sorry, my mistake, it seems that the ready=True is due to
>>> `initialDelaySeconds` has been set `30s`, and within the 30 seconds, the
>>> nginx POD would be `Ready`.
>>>
>>
>>  Are you really really sure that is the case?
>>
>> Can you send a yaml and kubectl commands/output to reproduce?
>>
>
> the nginx pod definition listed below:
>
>
> 
>
>
>  and the kubectl output is:
>
>
> 
>
>
> seems it's unhealthy, and Ready=True. And after some minutes, I can see
> the POD restarted and it entered Ready=False ( I guess that the POD lives
> greater than 30s,  therefore it became Ready=False)
>
>
>
> 
>
>
> Thanks.
>
> --
> 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] livenessProbe failed won't set pod status Ready=False

[Rodrigo Campos]

On Saturday, February 3, 2018, Colstuwjx  wrote:

> Sorry, my mistake, it seems that the ready=True is due to
> `initialDelaySeconds` has been set `30s`, and within the 30 seconds, the
> nginx POD would be `Ready`.
>

 Are you really really sure that is the case?

Can you send a yaml and kubectl commands/output to reproduce?

-- 
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] destoryed pod containers trigger

[Rodrigo Campos]

On Wed, Jan 31, 2018 at 06:38:36AM -0800, Colstuwjx wrote:
> >
> >> But, what if we want to trigger the detail exited reason for the exited 
> >> containers? Is there any parameters configure that?
> >
> > Have you checked the terminationGracePeriod? I think it will do just that.
> 
> I'm afraid not, I need to check the exited container, such as some 
> container with wrong configurations, and determine the root cause.
> After  the `terminationGracePeriod `, the unhealthy container would be 
> deleted, and we can't do things like `docker inspect 
> ` to trigger that case.

Ohh, sorry, my bad. I didn't understood that.

And sorry again, not sure how to do that. I've never looked into that myself :-/

-- 
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] destoryed pod containers trigger

[Rodrigo Campos]

On Wednesday, January 31, 2018, Colstuwjx  wrote:

> Hi team,
>
> As I known, kubernetes will kill the POD while the readiness probe failed
> over than `FailureThreshold` limit, and the unhealthy containers will be
> deleted by kubelet.
>

I think only the liveness probe will do that.



> But, what if we want to trigger the detail exited reason for the exited
> containers? Is there any parameters configure that?
>

Have you checked the terminationGracePeriod? I think it will do just that.

-- 
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 add the Docker Parameter "--security-opt" to Kubernetes Deployment ?

[Rodrigo Campos]

Oh, sorry, I really don't know about windows :-(

On Sunday, January 21, 2018, Thomas Asanger  wrote:

> Hi Rodrigo,
>
> This Option is starting the container under the service account on our
> W2016 Host as configured in the json file.
> To get our Application working, it must be running under this gMSA (Group
> Managed Service Accounts)
>
> Here is a good explaination about gMSA and how to run it with docker:
> https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-
> containers/manage-serviceaccounts
> and this:
> https://blogs.msdn.microsoft.com/containerstuff/2017/01/30/
> create-a-container-with-active-directory-support/
>
> But unfortunately I dont know how to apply the gMSA Credentials with
> Kubernetes.
> The application works fine if we start the container with docker and the
> security-opt Parameter so it seems working basically.
>
> Cheers, Thomas
>
>
>
> Am Freitag, 19. Januar 2018 11:49:03 UTC+1 schrieb Thomas Asanger:
>>
>> Hi All,
>>
>> I need to start a Windows Container with Kubernetes on a W2016 Server
>> with a given group managed service account.
>> The Kubernetes Setup itself seems working, also the Docker installation.
>> Starting the Windows Container directly with docker works also fine.
>>
>> This is the Docker start Command :
>>
>> docker run -d -p 8000:9000 --security-opt "credentialspec=file://svc1505
>> .json ."
>>
>> The Parameter --security-opt applies the credentials stored in the file 
>> "svc1505.json"
>> as wanted.
>> This is an example content of the json credentials file:
>> {"CmsPlugins":["ActiveDirectory"],"DomainJoinConfig":{"DnsName":"
>> contoso.com","Guid":"244818ae-87ca-4fcd-92ec-
>> e79e5252348a","DnsTreeName":"contoso.com","NetBiosName":"
>> DEMO","Sid":"S-1-5-21-2126729477-2524075714-30947929
>> 73","MachineAccountName":"WebApplication1"},"ActiveDirectory
>> Config":{"GroupManagedServiceAccounts":[{"Name":"
>> WebApplication1","Scope":"DEMO"},{"Name":"WebApplication1","Scope":"
>> contoso.com"}]}}
>>
>> How is it possible to run this container with the needed Credentials
>> under Kubernetes ?
>>
>> The Kubernetes Security context seems to related to linux only, is this
>> right ?
>>
>> spec:
>>   securityContext:
>> runAsUser: 1000
>> fsGroup: 2000
>>
>>
>> Cheers, Thomas
>>
>> --
> 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] How to add the Docker Parameter "--security-opt" to Kubernetes Deployment ?

[Rodrigo Campos]

If one of the available options on deployment (see the API doc for
completeness) doesn't do that, then you probably can't use that option.

But what is that you want (sorry, I don't know what that docker option
does)? Do you want some json file available in the container fs when it
runs? In that case, take a look at secrets (or configmaps) that do exactly
that :)

On Friday, January 19, 2018, Thomas Privat  wrote:

> Hi All,
>
> I need to start a Windows Container with Kubernetes on a W2016 Server with
> a given group managed service account.
> The Kubernetes Setup itself seems working, also the Docker installation.
> Starting the Windows Container directly with docker works also fine.
>
> This is the Docker start Command :
>
> docker run -d -p 8000:9000 --security-opt "credentialspec=file://
> svc1505.json ."
>
> The Parameter --security-opt applies the credentials stored in the file 
> "svc1505.json"
> as wanted.
> This is an example content of the json credentials file:
> {"CmsPlugins":["ActiveDirectory"],"DomainJoinConfig":{"DnsName":"
> contoso.com","Guid":"244818ae-87ca-4fcd-92ec-e79e5252348a","DnsTreeName":"
> contoso.com","NetBiosName":"DEMO","Sid":"S-1-5-21-2126729477-2524075714-
> 3094792973","MachineAccountName":"WebApplication1"},"
> ActiveDirectoryConfig":{"GroupManagedServiceAccounts":[
> {"Name":"WebApplication1","Scope":"DEMO"},{"Name":"
> WebApplication1","Scope":"contoso.com"}]}}
>
> How is it possible to run this container with the needed Credentials under
> Kubernetes ?
>
> The Kubernetes Security context seems to related to linux only, is this
> right ?
>
> spec:
>   securityContext:
> runAsUser: 1000
> fsGroup: 2000
>
>
> Cheers, Thomas
>
> --
> 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] Limit numer connection

[Rodrigo Campos]

No, It shouldn't be any problems. You can stress test.

Or maybe my email is too late? :)

On Wednesday, January 10, 2018, Nicolas  wrote:

> Hi all,
>
> there is a connection limit of single server/IP ? We have container
> Kubernet with a internal service that connect at an external server. (about
> 50 connection/minute or 4M connection/day ).There is a limit of number
> connection or connection / seconds?
>I would like to know this before going in production ;-)
>
> Many Thanks
>
> --
> 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] Re: How to achieve Nginx,PHP-FPM,PHP Module and MySQL in Kubernetes

[Rodrigo Campos]

What do you mean? Sorry, I didn't understand (and the thread seems broken,
so I can just read your mail and what you quote)

On Friday, January 12, 2018,  wrote:

> On Wednesday, 15 March 2017 04:58:41 UTC-3, Prabhurs  wrote:
> > Hi Team, I am new to Kubernetes... I have setup kubernetes with 1 master
> and 3 slave node. I have created mysql and nginx pod and its running on
> different nodes successfully... Now i want to deploy my application... It
> has nginx,php-fpm,PHPmodule and MySQL combination. How can I achieve this
> in Kubernetes, Could you please anyone help me...
>
> up!
>
> --
> 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.

[kubernetes-users] Re: Perform external HTTP requests during lifecycle hook

[Rodrigo Campos]

Moving to kubernetes-users

On Thu, Jan 04, 2018 at 01:37:12AM -0800, Rémi Bèges wrote:
> Hi,
> 
> I would like to perform external HTTPS request during the postStart and 
> preStop events, in order to notify a remote API. Is this possible ?
> 
> Also, I would need to pass an identification token and a container token, 
> to validate the request and identify which job/pod/container is being 
> started/ended. Is it possible to access environment variable inside the 
> handlers ?

If you use a script in the container and specify it in the postStart and preStop
events?

Note that in some circumstances (like a node crash, for example) some will not
be called. So, you would find problems if that is a hard-dependency (like with
any system, bare metal too, that may just "freeze").



Thanks a lot,
Rodrigo

-- 
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] Kubernetes Volume storage questions

[Rodrigo Campos]

The first are clustered filesystems, you don't need that complication.

EBS is just a block device, probably the same is true for VMware.

But feel free to read about them, it's a subject on its own and not at all
Kubernetes specific

On Tuesday, January 2, 2018, DK  wrote:

> Thanks, what are the benefits (if any) to choosing GlusterFS/Ceph over
> VsphereVolume/AWSElasticBlockStore? For a database like Postgres.
>
> --
> 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] Kubernetes Volume storage questions

[Rodrigo Campos]

Or just a pvc (a volume claim) that by default in one cluster is ebs and
the other is the one for VMware?

Take a look into PVC doc, it might be just what you want :-)

On Tuesday, January 2, 2018, DK  wrote:

> Hi,
>
> My Kubernetes cluster will be running on VmWare and in future on Amazon's
> AKS also.
>
> What should I be looking for regards Volume drivers?
>
>- Cepth, GlusterFS seem to be popular options.
>- RexRay seems to be popular in Docker with a FlexRay K8s option
>
> Or should I be looking at switching between VsphereVolume and
> AWSElasticBlockStore depending on the cluster??
> Should I have separate yaml files depending on where the cluster is hosted?
>
> I'm initially looking at storage for PostGres and some application
> specific property files
>
>
> --
> 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] Kubernetes service type for background app

[Rodrigo Campos]

Services are just to expose.

So you can just a deployment and decide (or autoscale) the replicas :)

On Tuesday, January 2, 2018, Mario Rodriguez  wrote:

> good question, I thought you always needed a Service when running an app
> in k8s.
>
> On Monday, January 1, 2018 at 10:51:48 PM UTC-6, Tim Hockin wrote:
>>
>> Why do you need a Service at all?
>>
>> On Jan 1, 2018 8:43 PM, "Mario Rodriguez"  wrote:
>>
>>> Hi, I'm in the middle of creating an K8s app that doesn't expose any
>>> HTTP endpoints, is just a background app that pulls messages from a message
>>> bus and takes some action based on the incoming message. No other apps will
>>> interact directly with this background app, only thru posting messages into
>>> the message bus.
>>>
>>> Scaling is a requirement and most likely will always need to run more
>>> than one replica.
>>>
>>>
>>> What is the recommended Service type in Kubernetes to handle this type
>>> of workload ?
>>>
>>> --
>>> 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.
>>>
>> --
> 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] Mysql kubernetes deployment and management

[Rodrigo Campos]

How do you install and run MySQL?

What errors do you see when connecting, exactly?

And what do you see in the MySQL pods logs?

Sorry, but try to read your email from a person who doesn't know how you
deploy, how it fails, etc. And you will see that is actually pretty hard
for us to say something with the info provided. So, please try to add as
much detail and everything you tried and exact output of each command you
tried.


Thank!

On Thursday, December 28, 2017,  wrote:

> I have noticed an issue with deploying and managing mysql on kubernetes .
> Although this is a test environment I noticed that when I deploy a mysql 5
> image to the cluster all works well for about 3 weeks .I try to access my
> db and I find out that I can't.
> I keep seeing errors like unable to access the db .Meanwhile it is
> actually running in the cluster .The database files seem to be there
> because if I delete the deployment and try to reinstall it again it says
> can't initialize db because data directory already exists. This has
> happened to me three times where I uninstall and reinstall again 3 weeks
> later I see the same issues come up .I have no idea what the issue is .Any
> thoughts or suggestions would be appreciated .
>
> --
> 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] why can i see the process that in a container in the host?

[Rodrigo Campos]

It's about docker. When you run a docker container you are really running a
process (with cgroups to limit cpu, namespaces to isolate visibility, etc.
But it's just a process)

On Tuesday, December 19, 2017,  wrote:

> hi all,
>
> i got confused that when i create a pod like mysql, i can see the mysqld
> process in the host, any one can tell me why that happens?
> thanks.
>
> --
> 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] How to put in communication two clusters in Kubernetes

[Rodrigo Campos]

On Wednesday, December 13, 2017, Gmail  wrote:

>
> Can't you use an internal load balancer to communicate?
>
>
> I noticed that if I create a load balancer service or an ingress service,
> Kubernetes will create a public ip address.
> So when you say *internal* load balancer, what are you referring to?
> Because I tried to use a nodeport service to communicate between cluster
> and didn't work
>

My reference was to this:
https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing

Shouldn't that do the trick?

-- 
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 put in communication two clusters in Kubernetes

[Rodrigo Campos]

Sorry, not follow the price argument. You are only charged for the nodes
you use on a Kubernetes cluster (no Masters, no matter cluster size).

So, I really don't why it makes a difference the number of clusters

On Wednesday, December 13, 2017,  wrote:

> I think that the situation is more complicated if we start looking at
> machine prices.
> Let me use some real data:
> 1) I have to use a db machine like gcloud n1-standard-16 ---> kubernetes
> cluster with 1 node for 500$/month
> 2) I have to use 9 web server like n1-standard-2 ---> kubernetes cluster
> with 9 nodes for 480$/month
>
> So with about 1000$/month I have the configuration that currently supports
> the web traffic of my company.
>
> If I wanted to use a single cluster I should choose nodes like
> n1-standard-16.
> Wanting not to exceed the $1000 limit, I could create a cluster with 2
> nodes.
> So I'll have: a node for db and a node for 9 (web) pod
>
> So the real question could be: in terms of performance, scalability and
> stability which is the better solution between: (9 nodes with 1 pod) vs (1
> node with 9 pods)
>
> If two alternatives are comparable I could use a single cluster :)
>
>
>
>
>
>
>
>
>
>
> Il giorno martedì 12 dicembre 2017 23:00:10 UTC+1, David Rosenstrauch ha
> scritto:
> > On 2017-12-12 4:38 pm, Marco De Rosa wrote:
> > > The main reason is that the "web" cluster has hardware features
> > > different from the "db" cluster and I didn't find a way to have a
> > > cluster with for example one node better, in cpu and/or ram, than
> > > others.
> > > So 2 clusters to put in communication with the doubt that I have
> > > described above.
> > > The alternative could be create a single cluster with n nodes sized in
> > > such a way as to support web traffic and database work.
> > > So a situation where I have for example 4 nodes: in 3 nodes 6 web-pods
> > > plus the last node as pure db machine.
> > > But this solution is quite complicated in terms of how precisely to
> > > size the web pods, the db and the overall characteristics of the
> > > cluster..
> > > So the idea to create two different clusters
> >
> >
> > FYI, this could probably be easily accomplished on a single cluster,
> > using node labels and node selectors.
> >
> > Let's say you had 2 types of nodes:  machines with big disks, and
> > machines with lots of memory.  Then let's say that you have 2 different
> > types of containers - one that runs a memory cache, and one that runs a
> > log file processing system.  What you could do is label the nodes as,
> > say, either "type=hidisk" or "type=himem", as appropriate.  And then you
> > could set a node selector on the caches to only run on nodes with
> > "type=himem", and a node selector on the log processors to only run on
> > nodes with "type=hidisk".
> >
> > HTH,
> >
> > DR
>
> --
> 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] Re: Removing RabbitMQ by using Kubernete Services

[Rodrigo Campos]

Basically, it's not possible to do it with just a service. Service does not
queue nor persist, so those guarantees that you just mention are not
possible with just a service.

The idea of the service is to expose pods to other pods or the internet, so
you can connect easily (and not worry about pods IP changing, etc.).
Nothing else.

So, queuing and persistency are out of scope. They are really a different
thing services and rabbitmq :-(

On Monday, December 11, 2017,  wrote:

> Thanks.
>
> We are using RabbitMQ for queuing jobs and celery workers that are in
> docker service as consumers of those jobs.
>
> --
> 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] how to pass kubernetes pods arguments like Docker arguments from command line

[Rodrigo Campos]

Don't know about springboot, etc. But yes, pods connect to databases, and
basically do any other network connection, without any issues. Just like
any other process can.

On Sunday, December 10, 2017, Henry Hottelet <hotte...@gmail.com> wrote:

> Rodrigo,
>
> I am going to do a remote test with Docker, however it has to be mapped to
> a public IP address.  At that point, the REST service, is mapped to a
> remote IP and port, which means that at that point, it doesn't matter if
> Cassandra runs in docker or not.
>
> However the question, still remains about whether springboot and datastax
> driver can run inside a docker container and target a remote ip and port.
>
> I would have to do some stand alone tests to find out.
>
> Do you know if anyone else is running Pods that target a remote database
> service?
>
> -Henry
>
> On Sunday, December 10, 2017 at 12:23:57 PM UTC-5, Rodrigo Campos wrote:
>>
>> Okay, so that's not at all related with what I've said...
>>
>> I'm quite sure that port is fine regarding docker Kubernetes, don't know
>> about your driver. Wild guess: might be just not using SO_REUSE or
>> something like that in your local machine what you think it's the issue.
>>
>> Good luck with that
>>
>> On Sunday, December 10, 2017, Henry Hottelet <hott...@gmail.com> wrote:
>>
>>> Rodrigo,
>>>
>>> I have decided to go down another path, and consider Dynamic changes to
>>> IPaddress and Port numbers via REST interface calls remotely into a Docker
>>> image.
>>>
>>> Although configuring Pods at definition time, with arguments might be
>>> cool, I have gone down another path, and am considering configuring
>>> connection settings being dynamic at runtime via a configure interface.
>>>
>>> Preliminary tests, are showing me that Docker has a conflict with
>>> Datastax driver on port 9042, with local IPaddress of 127.0.0.1 due to port
>>> binding issues on a local machine.
>>>
>>> I am investigating further to help determine if these restrictions can
>>> be lifted for DataStax driver support inside a docker container, which is
>>> limiting me using Pods at all.
>>>
>>> I hope Datastax can help lift this restriction, however, I see it as a
>>> current limitation on Docker and Datastax driver, and have opened an issue
>>> with Datastax. (https://groups.google.com/a/l
>>> ists.datastax.com/forum/#!topic/java-driver-user/QohK0Sd86-4)
>>>
>>> If you were curious on how to recreate the problem with Docker and
>>> DataStax driver:
>>> docker run --name cassandra -m 2g -p 127.0.0.1:9042:9042 -p
>>> 127.0.0.1:9160:9160 -d cassandr
>>> docker run --name spring-boot-web -p 8080:8080 -p 127.0.0.1:9042:9042
>>> -p 9160:9160 docker.io/joethecoder2/spring-boot-web TCP4-LISTEN:9042
>>> TCP4:172.17.0.2:9042
>>>
>>> I have hit a deadend, at this point for using Docker and Datastax
>>> driver, and I was hoping that they would work together, however the fall
>>> back path is to use SpringBoot without Docker or Kubernetes Pods.
>>>
>>> Is anyone else currently using Data query calls from within Docker with
>>> a database driver to an outside ip address and port?
>>>
>>> -Henry
>>>
>>>
>>> On Saturday, December 9, 2017 at 11:29:58 AM UTC-5, Rodrigo Campos wrote:
>>>>
>>>> Google??? And, also, what is the point of that phrasing?
>>>>
>>>> Someone was trying to help, maybe there was some miscommunication and
>>>> the suggested solution was not what better fits you now. That's all, right?
>>>>
>>>> On Thursday, December 7, 2017, Henry Hottelet <hott...@gmail.com>
>>>> wrote:
>>>>
>>>>> *How to pass arguments to Kubernetes POD were succesfull, however
>>>>> Google states, that templates are needed for configurability.*
>>>>>
>>>>> https://stackoverflow.com/questions/47700482/kubernetes-pod-
>>>>> arguments-are-not-displayed-in-service-under-args-without-
>>>>> error/47703631#47703631
>>>>>
>>>>>
>>>>> On Thursday, December 7, 2017 at 11:27:23 AM UTC-5, Tim Hockin wrote:
>>>>>>
>>>>>> You want a template expander before you get to kubectl.  Otherwise,
>>>>>> the thing that is running isn't reflected by any versionable artifact.
>>>>>>
>>>>>> Because templating is a high-opinion space, we 

Re: [kubernetes-users] how to pass kubernetes pods arguments like Docker arguments from command line

[Rodrigo Campos]

Okay, so that's not at all related with what I've said...

I'm quite sure that port is fine regarding docker Kubernetes, don't know
about your driver. Wild guess: might be just not using SO_REUSE or
something like that in your local machine what you think it's the issue.

Good luck with that

On Sunday, December 10, 2017, Henry Hottelet <hotte...@gmail.com> wrote:

> Rodrigo,
>
> I have decided to go down another path, and consider Dynamic changes to
> IPaddress and Port numbers via REST interface calls remotely into a Docker
> image.
>
> Although configuring Pods at definition time, with arguments might be
> cool, I have gone down another path, and am considering configuring
> connection settings being dynamic at runtime via a configure interface.
>
> Preliminary tests, are showing me that Docker has a conflict with Datastax
> driver on port 9042, with local IPaddress of 127.0.0.1 due to port binding
> issues on a local machine.
>
> I am investigating further to help determine if these restrictions can be
> lifted for DataStax driver support inside a docker container, which is
> limiting me using Pods at all.
>
> I hope Datastax can help lift this restriction, however, I see it as a
> current limitation on Docker and Datastax driver, and have opened an issue
> with Datastax. (https://groups.google.com/a/lists.datastax.com/forum/#!
> topic/java-driver-user/QohK0Sd86-4)
>
> If you were curious on how to recreate the problem with Docker and
> DataStax driver:
> docker run --name cassandra -m 2g -p 127.0.0.1:9042:9042 -p 
> 127.0.0.1:9160:9160
> -d cassandr
> docker run --name spring-boot-web -p 8080:8080 -p 127.0.0.1:9042:9042 -p
> 9160:9160 docker.io/joethecoder2/spring-boot-web TCP4-LISTEN:9042 TCP4:
> 172.17.0.2:9042
>
> I have hit a deadend, at this point for using Docker and Datastax driver,
> and I was hoping that they would work together, however the fall back path
> is to use SpringBoot without Docker or Kubernetes Pods.
>
> Is anyone else currently using Data query calls from within Docker with a
> database driver to an outside ip address and port?
>
> -Henry
>
>
> On Saturday, December 9, 2017 at 11:29:58 AM UTC-5, Rodrigo Campos wrote:
>>
>> Google??? And, also, what is the point of that phrasing?
>>
>> Someone was trying to help, maybe there was some miscommunication and the
>> suggested solution was not what better fits you now. That's all, right?
>>
>> On Thursday, December 7, 2017, Henry Hottelet <hott...@gmail.com> wrote:
>>
>>> *How to pass arguments to Kubernetes POD were succesfull, however Google
>>> states, that templates are needed for configurability.*
>>>
>>> https://stackoverflow.com/questions/47700482/kubernetes-pod-
>>> arguments-are-not-displayed-in-service-under-args-without-
>>> error/47703631#47703631
>>>
>>>
>>> On Thursday, December 7, 2017 at 11:27:23 AM UTC-5, Tim Hockin wrote:
>>>>
>>>> You want a template expander before you get to kubectl.  Otherwise, the
>>>> thing that is running isn't reflected by any versionable artifact.
>>>>
>>>> Because templating is a high-opinion space, we do not (currently) have
>>>> one that is built-in.
>>>>
>>>> On Dec 7, 2017 10:12 AM, "Henry Hottelet" <hott...@gmail.com> wrote:
>>>>
>>>>>
>>>>> Is there not a way to pass arguments from command line to the Pod
>>>>> specification?  There should be, because this is not the first time that a
>>>>> Docker argument is needed when calling a Pod instance, whether dynamic or
>>>>> staticly defined.
>>>>>
>>>>> I could have Pod1.yaml, Pod2.yaml, and have an Ipaddress, and Port
>>>>> number for reach separate Pod that is defined.
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, December 7, 2017 at 11:03:28 AM UTC-5, Tim Hockin wrote:
>>>>>>
>>>>>> Kubectl is not a templating system, which is what you are asking
>>>>>> for.  Create/Apply are declarative plumbing, suitable to things you would
>>>>>> check in to source control.  There are porcelain commands, eg. kubectl 
>>>>>> run,
>>>>>> which are closer to docker run, but less suitable to source control.
>>>>>>
>>>>>> On Dec 7, 2017 9:56 AM, "Henry Hottelet" <hott...@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> A problem:
>>>>>>>
>>>>>

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

[Rodrigo Campos]

Oh, I thought you wanted on different hosts but not as many pods as hosts.
If you want that's daemonset guarantees that (even if more nodes are
created later, etc.)

And what Kubernetes version are you using? There is some kind of support to
upgrade them in recent versions IIRC (not used that more than once, I
think). Maybe a newer version will solve all :)

On Thursday, December 7, 2017,  wrote:

> Today during a deploy I get a pod with 2 containers -,-
> I can confirm that the best solution to make sure you have only one pod
> per node is using the DaemonSet.
> Unfortunately using the approach to reapply the deployment yaml does not
> guarantee that after deployment each node has only a single pod.
> Anyway now everything is working properly
> Bye ;-)
>
> --
> 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] How to authenticate to a Kubernetes cluster created on AWS w/ kops

[Rodrigo Campos]

Awesome :)

On Wednesday, December 6, 2017, bg  wrote:

> Worked like a charm. Thank you very much!
>
> --
> 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] How to authenticate to a Kubernetes cluster created on AWS w/ kops

[Rodrigo Campos]

There is a similar command for kops, see:
https://github.com/kubernetes/kops/blob/master/docs/cli/kops_export_kubecfg.md

That should do the trick.

On Tuesday, December 5, 2017, bg  wrote:

> 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.
>

-- 
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] How to force Kubernetes to update deployment with a pod in every node

[Rodrigo Campos]

It's working as you need? :)

On Monday, December 4, 2017,  wrote:

> thank you all for the support ;-)
>
> --
> 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] How to force Kubernetes to update deployment with a pod in every node

[Rodrigo Campos]

The scheduler makes the decision trying to spread the pods on nodes as you
say. But that is just a "signal", other things are taken into account (pods
availability zone, in case of AWS, for example, to spread across AZs too)
node's resources, etc.

So, the default will try to do that, taking into account other variables
too. But it is not a hard requirement to not have 2 pods on a single node,
so it can (and will) happen.

You can force that requirement in several ways, using the hostPort option
for example. This is, I think, the simplest. But also using some other
functionality the default sched provides (like pod affinity, etc that has
been said) and you can even write your own sched for that deployment.

But scheduling is hard and unless you have a hard requirement that can't
ever happen, I think you probably want just the default.

The default is quite reasonable, maybe with more resources it's more likely
to happen what you want (or tuning the deployment options to first kill the
pod and then create a new one). But the default in my experience, works
just fine.

Also, take into account that if you add the hard requirement, some not nice
side effects might happen. For example, if two pods can never run in the
same node, then if some node crashes you better still have enough nodes to
run all the pods in different nodes, or some pods won't be scheduled. This,
of course, is not a problem if you really want them not ever to run on the
same node.

On Monday, December 4, 2017,  wrote:

> Hi all!
>
> I would like to know if there is a way to force Kubernetes, during a
> deploy, to use every node in the cluster.
> The question is due some attempts that I have done where I noticed a
> situation like this:
>
> - a cluster of 3 nodes
> - I update a deployment with a command like: kubectl set image
> deployment/deployment_name my_repo:v2.1.2
> - Kubernetes updates the cluster
>
> At the end I execute kubectl get pod and I notice that 2 pods have been
> deployed in the same node.
> So after the update, the cluster has this configuration:
>
> - one node with 2 pods
> - one node with 1 pod
> - one node without any pod (totally without any workload)
>
>
> Thanks for any suggestion
>
> --
> 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] How to permanently delete a deployment

[Rodrigo Campos]

Are you sure isn't there another deployment creating it? Or replica
controller or replica set?

On Friday, December 1, 2017,  wrote:

> On Friday, December 1, 2017 at 3:07:15 PM UTC-6, bqu...@newgistics.com
>  wrote:
> > I want to delete the instance of tiller running in my cluster. Really, I
> want to redeploy tiller. However, tiller won't go away. How can I remove
> tiller?
> >
> > Tiller is running as a daemon-set running in a single pod on one node.
> >
> > What I have tried so far..
> > Use kubectl commands:
> > kubectl -n "kube-system" delete deployment tiller-deploy
> > kubectl -n "kube-system" delete service tiller-deploy
> >
> > Results: tiller pod recreates itself
>
> I apologize.  tiller is not running as a daemon-set.  This is misleading.
> I agree, delete deployment should work.  However, when I execute delete
> deployment, a new tiller pod get immediately created
>
> --
> 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] ERROR Does not have minimum availability

[Rodrigo Campos]

What is the error exactly you are seeing?
Have you tried specifying a number of replicas?

On Friday, December 1, 2017, Montassar Dridi 
wrote:

> Why I keep getting this error Does not have minimum availability for a
> deployment as sample as this
> apiVersion: apps/v1beta1
> kind: Deployment
> metadata:
>   name: backup-deployment
>   labels:
> app: backup
> spec:
>   selector:
> matchLabels:
>   app: backup
>   template:
> metadata:
>   labels:
> app: backup
> spec:
>   containers:
>   - name: backup
> image: debian:jessie
> ports:
> - containerPort: 80
>
> --
> 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] How to make a container(s) to able to reach to ClusterIP:port or Service's Publilc IP:NodePort?

[Rodrigo Campos]

On Thursday, November 30, 2017, Kyunam Kim  wrote:

> How do I make a container aware of the service's IP:NodePort or
> ClusterIP:port address?
> Let's say, I can access my application at http://public-ip:port/myapp
> from the external world.
> I want a container(s) to be able to reach to http://public-ip:port
> Or
> to reach to ClusterIP:port.
>
> What k8s' capability do I use to make this happen?
>

Sorry, not sure I follow. Does it work for you using the service name? (Or
service+namespace)?

Unless you prohibited it in some way (like with network policy, but that is
probably not the case) that should work.

So, I might be missing something, sorry 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] What is the best-practice for exposing your public-facing services when running on AWS?

[Rodrigo Campos]

Not sure what you really mean. You use a load balancer that exposes the
kubernetes service typically. You can also use an ingress controller.

But why involve, and how, api gateway?

And ELB have a security group, you just enable what is reasonable there if
you want. Or just use service type load balancer and Kubernetes will do it
for you (sg and that).

On Sunday, November 26, 2017,  wrote:

> Hi All,
>
> I'm new to working with k8s, and I was wondering what do you think is the
> best practice when hosting on AWS for exposing your public-facing services?
> do you hold your backends and APIs on the same cluster and use AWS API
> Gateway to channel the request to the services? do you add another public
> subnet where you put your public-facing services on it? do you do both? do
> you do anything else?
>
> Thanks
>
> --
> 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] Unexpected Behavior When Scaling Application

[Rodrigo Campos]

If I have to bet, I'd bet it's the application.

But okay, that is what you see. But else do you see in Kubernetes? Logs of
kube-proxy, etc.?

How do you keep the users logged in the application? Is there any container
restart when this happens?

Are you using GKE? And how do you connect, via a public load balancer?

Tell us more about the app and your setup

On Wednesday, November 22, 2017,  wrote:

> Hi there,
>
> I’ve deployed an application to a Google Cloud Kubernete Cluster. The
> application is built using the Python web-framework Flask and uses a
> CloudSQL Postgres database for persistence. The script I used to deploy the
> application is this: https://gist.github.com/tnolan8/
> 85e91394d9ec1327f930808c71081aba -> the gist is actually slightly
> outdated and instead of a ReplicationController I’m now using a Deployment.
>
> When I have a single VM in my instance group for my Cluster and a singular
> pod deployed with the lb service running everything works fine, the
> application works just as intended. However when I scale to having two VMs
> in my instance group for my Cluster and keep only the one pod, so it’s
> essentially still only running on the one machine, I get unexpected
> behavior. For example, when logging into the application instead of
> actually logging in it will redirect to the homepage but 1/3 times it will
> actually log in.
>
> I don’t think it’s something to do with the application itself. Everything
> works okay locally and on a singular VM instance. I’ve tried looking
> through logs using StackDriver but I’m not really even sure what I should
> be looking for, there’s some weird disconnect occurring and I really can’t
> figure out why.
>
> Has anyone ever seen something like this? Any thoughts on what I could try
> to debug it or thoughts on what might actually be causing it?
>
> Much Appreciated,
>
> Tom.
>
> --
> 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: Private message regarding: Private message regarding: [kubernetes-users] Get current user name in pod yaml file

[Rodrigo Campos]

No problem! Hope it works :)

On Saturday, November 11, 2017, lppier <madst...@gmail.com> wrote:

> Yup I can do that. Was just wondering .. thanks for your help!
>
> On Friday, 10 November 2017 22:25:42 UTC+8, Rodrigo Campos wrote:
>>
>> Oh, sorry, Kubernetes users was removed. Adding it back
>>
>> On Friday, November 10, 2017, Rodrigo Campos <rodr...@gmail.com> wrote:
>>
>>> So they will create the deployment and you want that user executing that?
>>>
>>> Then i think this will work: just a template and modify those variables
>>> in the fly, and then send the modified yaml.
>>>
>>> There are some tools for that, but if the case is so simple I'd use just
>>> a shell script (with sed or awk).
>>>
>>> Does that solve it?
>>>
>>> On Friday, November 10, 2017, lppier <madst...@gmail.com> wrote:
>>>
>>>> Say I am the linux user with the name "pier"
>>>> The volume mount in my pod fileis :
>>>>
>>>> hostPath:
>>>>   path: /nfs/data1/home/pier
>>>>
>>>>
>>>> As I have multiple users, I don't want user mounting
>>>> /nfs/data1/home/pier all the time, but rather
>>>>
>>>> /nfs/data1/home/
>>>>
>>>> Of course, it would not be too difficult to ask them to edit the pod
>>>> yaml themselves. Just wondering whether I can do it for them by using their
>>>> linux username in the pod file.
>>>>
>>>>
>>>> On Friday, 10 November 2017 12:16:29 UTC+8, Rodrigo Campos wrote:
>>>>>
>>>>> Not sure what you mean, probably the answer is "no". But I  don't
>>>>> understand what you want.
>>>>>
>>>>> Do you want to replace $USER with what, exactly? The user running what?
>>>>>
>>>>> What are you trying to do?
>>>>>
>>>>> It seems like you are mixing things that do not have anything to do
>>>>> with each other. But, I might be wrong, can you please elaborate?
>>>>>
>>>>> On Friday, November 10, 2017, lppier <mads...@gmail.com> wrote:
>>>>>
>>>>>> Yes, I meant dynamically, like I would $USER in linux. Is it possible?
>>>>>>
>>>>>>
>>>>>> On Friday, 10 November 2017 10:55:58 UTC+8, Rodrigo Campos wrote:
>>>>>>>
>>>>>>> On Thursday, November 9, 2017, lppier <mads...@gmail.com> wrote:
>>>>>>>
>>>>>>>> In my pod yaml file, I need to mount the user's current directory
>>>>>>>> for use within the container.
>>>>>>>>
>>>>>>>> - hostPath:
>>>>>>>> path: /nfs/data1/home/cys
>>>>>>>>
>>>>>>>>
>>>>>>>> where cys is the user.
>>>>>>>> How can I grab the current linux user in the pod spec? I can't seem
>>>>>>>> to find any info on this.
>>>>>>>>
>>>>>>>
>>>>>>> What do you mean with "current user"? The user running the pod? That
>>>>>>> can be specified in the yaml statically. I can't think of anything 
>>>>>>> dynamic,
>>>>>>> so not sure what you mean :-/
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> 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: Private message regarding: [kubernetes-users] Get current user name in pod yaml file

[Rodrigo Campos]

Oh, sorry, Kubernetes users was removed. Adding it back

On Friday, November 10, 2017, Rodrigo Campos <rodrig...@gmail.com> wrote:

> So they will create the deployment and you want that user executing that?
>
> Then i think this will work: just a template and modify those variables in
> the fly, and then send the modified yaml.
>
> There are some tools for that, but if the case is so simple I'd use just a
> shell script (with sed or awk).
>
> Does that solve it?
>
> On Friday, November 10, 2017, lppier <madst...@gmail.com
> <javascript:_e(%7B%7D,'cvml','madst...@gmail.com');>> wrote:
>
>> Say I am the linux user with the name "pier"
>> The volume mount in my pod fileis :
>>
>> hostPath:
>>   path: /nfs/data1/home/pier
>>
>>
>> As I have multiple users, I don't want user mounting /nfs/data1/home/pier
>> all the time, but rather
>>
>> /nfs/data1/home/
>>
>> Of course, it would not be too difficult to ask them to edit the pod yaml
>> themselves. Just wondering whether I can do it for them by using their
>> linux username in the pod file.
>>
>>
>> On Friday, 10 November 2017 12:16:29 UTC+8, Rodrigo Campos wrote:
>>>
>>> Not sure what you mean, probably the answer is "no". But I  don't
>>> understand what you want.
>>>
>>> Do you want to replace $USER with what, exactly? The user running what?
>>>
>>> What are you trying to do?
>>>
>>> It seems like you are mixing things that do not have anything to do with
>>> each other. But, I might be wrong, can you please elaborate?
>>>
>>> On Friday, November 10, 2017, lppier <mads...@gmail.com> wrote:
>>>
>>>> Yes, I meant dynamically, like I would $USER in linux. Is it possible?
>>>>
>>>>
>>>> On Friday, 10 November 2017 10:55:58 UTC+8, Rodrigo Campos wrote:
>>>>>
>>>>> On Thursday, November 9, 2017, lppier <mads...@gmail.com> wrote:
>>>>>
>>>>>> In my pod yaml file, I need to mount the user's current directory for
>>>>>> use within the container.
>>>>>>
>>>>>> - hostPath:
>>>>>> path: /nfs/data1/home/cys
>>>>>>
>>>>>>
>>>>>> where cys is the user.
>>>>>> How can I grab the current linux user in the pod spec? I can't seem
>>>>>> to find any info on this.
>>>>>>
>>>>>
>>>>> What do you mean with "current user"? The user running the pod? That
>>>>> can be specified in the yaml statically. I can't think of anything 
>>>>> dynamic,
>>>>> so not sure what you mean :-/
>>>>>
>>>>>
>>>> --
>>>> 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] Pod Presets and init containers

[Rodrigo Campos]

I don't find any reason mentioned in the proposal:
https://github.com/kubernetes/community/blob/master/contributors/design-proposals/service-catalog/pod-preset.md

It seems like an useful question to ask on service catalog sig? Probably
with a concrete use case :)

On Thursday, November 9, 2017, Warren Strange 
wrote:

>
> Here is a small gist that demonstrates the issue:
>
> https://gist.github.com/wstrange/b9c1adc2139dab8f9b554a9d21b30bdd
>
> running
> kubectl logs test -c init
>
> does not show the env var being set. But I can see it in the test
> container.
>
> Unless I am missing something, this looks like a bug?
>
>
> On Wednesday, November 8, 2017 at 7:49:15 PM UTC-7, Warren Strange wrote:
>>
>>
>> I am trying to use a pod preset to mount a volume.
>>
>> My pod containers are getting enriched with the podpreset volume mounts,
>> but the init container is not.
>>
>> bug or feature?
>>
>>
>> --
> 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] Two Cluster in single node

[Rodrigo Campos]

I've never done that, but I guess you can do it. Go ahead and report back :)

On Tuesday, November 7, 2017,  wrote:

> I am working to configure two kubernetes cluster setup(including binaries
> installation) in a single machine, so far, I configured Ethernet adapter to
> provide 2 ips, is that possible to go, having two instances, of all the
> services? and having two working clusters in a single machine??
>
> --
> 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] Container termination force pod termination?

[Rodrigo Campos]

On Fri, Oct 27, 2017 at 05:17:48PM -0400, David Rosenstrauch wrote:
> I'm trying to make sure that as I'm deploying new services on our cluster,
> that failures/restarts get handled in a way that's most optimal for
> resiliency/uptime.
> 
> 
> I'm simplifying things a bit, but if a piece of code running inside a
> container crashes, there's more or less 2 possibilities:  1) bug in the code
> (and/or it's trying to process data that causes an error), or 2) problems

It can be a "random" issue (like a network burp, etc.), or also exceeding memory
limits of the container and gets restarted (that happens when X event is
processed in the container and uses tons of mem), etc, etc. Which will, most
probably, work if restarted.

> with the hardware/network (full disk, bad disk, network outage, etc.)  If

As Tim said, network outage is handled (like if the node <--> master network is
not working) just fine. Full disk should be handled fine since a few versions of
kubernetes now, as there is accounting of inodes and space used by containers,
so it can be reclaimed too.

> the issue is #1, then it doesn't matter whether you restart the container or
> the pod.  But if the issue is #2, then restarting the pod (i.e., on another
> host) would fix the problem, while restarting the container probably
> wouldn't.
> 
> So I guess this is sort of alluding to a bigger question, then:  does k8s
> have any ability to detect if a host is having hardware problems and, if so,
> avoid scheduling new pods on it, move pods off of it if their containers are
> crashing, etc.

I know of https://github.com/kubernetes/node-problem-detector, that I think
tries to solve exactly that. But I have not used that myself.

So I guess the answer is "yes" :-)



Thanks,
Rodrigo

-- 
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] Multiple version of software on same namespace

[Rodrigo Campos]

On Mon, Oct 30, 2017 at 03:34:00AM -0700, rgoncal...@gmail.com wrote:
> I'm trying to figure out what's the best approach to deploy multiple versions 
> of the same software in kubernetes without relying on namespaces. According 
> to the docs: 
> 
> "It is not necessary to use multiple namespaces just to separate slightly 
> different resources, such as different versions of the same software: use 
> labels to distinguish resources within the same namespace."
> 
> The only way (that I know of) to separate multiple versions of same software 
> on the same namespace is naming services in accordance to software version, 
> adjust the selector field and tag pods appropriately. This has maintenance 
> overhead and I'm required to reference services with a different name 
> according to the desired version. I don't think this is a solution.

Why not? What is the problem you want to solve?

> 
> I don't see any other way besides using namespaces. What am I missing 
> something?

I think services is the way to do it, with labels on deplyoments, but I might be
missing the details of what you want to do. Can you pelase elaborate?

-- 
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] Container termination force pod termination?

[Rodrigo Campos]

On Fri, Oct 27, 2017 at 1:34 PM, David Rosenstrauch  wrote:
> Was speaking to our admin here, and he offered that running a health check
> container inside the same pod might work.  Anyone agree that that would be a
> good (or even preferred) approach?

Not sure what you mean, but IIUC, it won't get the pod scheduled to
another node.

-- 
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] Container termination force pod termination?

[Rodrigo Campos]

(google groups is taking days when I use my non-gmail email, so I'm
sending via gmail again)


On Fri, Oct 27, 2017 at 6:17 PM, David Rosenstrauch  wrote:
> I'm trying to make sure that as I'm deploying new services on our cluster,
> that failures/restarts get handled in a way that's most optimal for
> resiliency/uptime.
>
>
> I'm simplifying things a bit, but if a piece of code running inside a
> container crashes, there's more or less 2 possibilities:  1) bug in the code
> (and/or it's trying to process data that causes an error), or 2) problems

It can be a "random" issue (like a network burp, etc.), or also exceeding memory
limits of the container and gets restarted (that happens when X event is
processed in the container and uses tons of mem), etc, etc. Which will, most
probably, work if restarted.


> with the hardware/network (full disk, bad disk, network outage, etc.)  If

As Tim said, network outage is handled (like if the node <--> master network is
not working) just fine. Full disk should be handled fine since a few versions of
kubernetes now, as there is accounting of inodes and space used by containers,
so it can be reclaimed too.


> the issue is #1, then it doesn't matter whether you restart the container or
> the pod.  But if the issue is #2, then restarting the pod (i.e., on another
> host) would fix the problem, while restarting the container probably
> wouldn't.
>
> So I guess this is sort of alluding to a bigger question, then:  does k8s
> have any ability to detect if a host is having hardware problems and, if so,
> avoid scheduling new pods on it, move pods off of it if their containers are
> crashing, etc.

I know of https://github.com/kubernetes/node-problem-detector, that I think
tries to solve exactly that. But I have not used that myself.

So I guess the answer is "yes" :-)



Thanks,
Rodrigo

-- 
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] Container termination force pod termination?

[Rodrigo Campos]

I don't think it is configurable.

But I don't really see what you are trying to solve, maybe there is another
way to achieve it? If you are running a pod of a single container, what is
the problem that the container is restarted when is appropriate instead of
the whole pod?

I mean, you would need to handle the case where some container in the pod
crashed or is stalled, right? The liveness probe will be done periodically,
but until the next check is done, it can be hunged or something. So even if
the whole pod is restarted, that problem is still there. And restarting the
whole pod won't solve that. So probably my guess is not correct about what
you are trying to solve.

So, sorry, but can I ask again what is the problem you want to address? :)

On Friday, October 27, 2017, David Rosenstrauch  wrote:

> Was speaking to our admin here, and he offered that running a health check
> container inside the same pod might work.  Anyone agree that that would be
> a good (or even preferred) approach?
>
> Thanks,
>
> DR
>
> On 2017-10-27 11:41 am, David Rosenstrauch wrote:
>
>> I have a pod which runs a single container.  The pod is being run
>> under a ReplicaSet (which starts a new pod to replace a pod that's
>> terminated).
>>
>>
>> What I'm seeing is that when the container within that pod terminates,
>> instead of the pod terminating too, the pod stays alive, and just
>> restarts the container in it.  However I'm thinking that what would
>> make more sense would be for the entire pod to terminate in this
>> situation, and then another would automatically start to replace it.
>>
>> Does this seem sensible?  If so, how would one accomplish this with
>> k8s?  Changing the restart policy setting doesn't seem to be an
>> option.  The restart policy (e.g. Restart=Always) seems to apply only
>> to whether to restart a pod; the decision about whether to restart a
>> container in a pod doesn't seem to be configurable.  (At least not
>> that I could see.)
>>
>> Would appreciate any guidance anyone could offer here.
>>
>> Thanks,
>>
>> DR
>>
>
> --
> 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] minikube - Error from server (BadRequest): container "hello-minikube" in pod "hello-minikube-180744149-z87pb" is waiting to start: ContainerCreating

[Rodrigo Campos]

Check the docs, but IIRC the kubectl run created a deployment or rc. That's
why, I guess

On Friday, October 20, 2017, DK  wrote:

> *Also there doesn't seem to be a way to delete the pod in this state*
>>
> kubectl delete pods *hello-minikube-180744149-z87pb*
> pod "*hello-minikube-180744149-z87pb*" deleted
>
> But it never gets removed
>
>
> --
> 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] Re: GKE Kubernetes control plane unable to talk to service

[Rodrigo Campos]

On Sun, Oct 15, 2017 at 12:45:38PM -0700, adi...@portworx.com wrote:
> Can someone help us here?
> Basically the Kubernetes controller manager on GKE is unable to reach the 
> Service. Is something different required in case of GKE in the service 
> description?

Is kube-proxy running on that node? I'd guess it is not, if that is the only
node not capable to access it.

-- 
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] Cluster DNS: bottleneck with ~1000 outbound connections per second

[Rodrigo Campos]

Ohh, sorry. My bad, just ignore my past email :-)

On Thursday, October 5, 2017, Evan Jones <evan.jo...@bluecore.com> wrote:

> My script *is* always looking up the same domain, and I believe it is
> cached by dnsmasq. I *think* the limit is the kernel NAT connection
> tracking, because each DNS query comes from a new ephemeral port, so it
> ends up using up all NAT mappings on the node running kube-dns. This is why
> dnsPolicy: Default fixes the problem: It uses the host's DNS configuration
> which avoids the NAT connection limits.
>
> Details including the Python code and configs to reproduce it on a brand
> new GKE cluster are at the bottom of https://github.com/kubernet
> es/kubernetes/issues/45976
>
> I did a separate test, using a Go DNS query generator, which was able to
> do 8 DNS queries per second, so dnsmasq does not appear to be the limit.
>
> Thanks!
>
> Evan
>
>
> On Thu, Oct 5, 2017 at 5:26 PM, Rodrigo Campos <rodr...@sdfg.com.ar
> <javascript:_e(%7B%7D,'cvml','rodr...@sdfg.com.ar');>> wrote:
>
>> On Thu, Oct 05, 2017 at 04:29:21PM -0400, Evan Jones wrote:
>> > The sustained 1000 qps comes from an application making that many
>> outbound
>> > connections. I agree that the application is very inefficient and
>> shouldn't
>> > be doing a DNS lookup for every request it sends, but it's a python
>> program
>> > that uses urllib2.urlopen so it creates a new connection each time. I
>> > suspect this isn't that unusual? This could be a server that hits an
>> > external service for every user request, for example. Given the
>> activity on
>> > the GitHub issues I linked, it appears I'm not the only person to have
>> run
>> > into this.
>>
>> But is always on different domains? If not, it can probably be cached (as
>> long
>> as the TTL allows) by the DNS server and, even if your app makes so many
>> requests, it should be answered quite fast.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Kubernetes user discussion and Q" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/kubernetes-users/7JBq6jhMZHc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> kubernetes-users+unsubscr...@googlegroups.com
>> <javascript:_e(%7B%7D,'cvml','kubernetes-users%2bunsubscr...@googlegroups.com');>
>> .
>> To post to this group, send email to kubernetes-users@googlegroups.com
>> <javascript:_e(%7B%7D,'cvml','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
> <javascript:_e(%7B%7D,'cvml','kubernetes-users%2bunsubscr...@googlegroups.com');>
> .
> To post to this group, send email to kubernetes-users@googlegroups.com
> <javascript:_e(%7B%7D,'cvml','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] Cluster DNS: bottleneck with ~1000 outbound connections per second

[Rodrigo Campos]

On Thu, Oct 05, 2017 at 04:29:21PM -0400, Evan Jones wrote:
> The sustained 1000 qps comes from an application making that many outbound
> connections. I agree that the application is very inefficient and shouldn't
> be doing a DNS lookup for every request it sends, but it's a python program
> that uses urllib2.urlopen so it creates a new connection each time. I
> suspect this isn't that unusual? This could be a server that hits an
> external service for every user request, for example. Given the activity on
> the GitHub issues I linked, it appears I'm not the only person to have run
> into this.

But is always on different domains? If not, it can probably be cached (as long
as the TTL allows) by the DNS server and, even if your app makes so many
requests, it should be answered quite fast.

-- 
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] Need to talk to Kubernetes technical team

[Rodrigo Campos]

What do you mean with kubernetes technical team?

If you have any security issue, please see: https://kubernetes.io/security/

I can't think of anything else, so can you please elaborate?

On Saturday, September 30, 2017,  wrote:

> Hey,
>
> Can Anyone from the Kubernetes technical team contact me.
>
>
> Please respond as soon as possible.
>
> --
> 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] Resolv.conf override for a pod

[Rodrigo Campos]

Not sure that will work, try step by step.

Start creating the file in some dir in /etc/ and then try to just have the
file in /etc/ (probably with subpath or something like that), and then ten
try to use it mount it as /etc/resolv.conf

Any example of mounting the configmap as a volume will do the first step.
I'd start like that.

Another hack you can 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 <
simone.dandr...@gmail.com> wrote:

> I can't try today unfortunately but that's definitely the issue, I will
> have to test it to an environment where I can reach the consul subnets.
> As per what I am trying to achieve (and that's perfectly fine if we cannot
> find a viable solution, it is a proof of concept after all) I need a way to
> have different nameservers per namespace or pod. It was suggested before
> that I could do it via volumeMounts, by creating a new resolv.conf and
> copying it over the resolv.conf of the pod. I tried but I couldn't get it
> working, but I believe I am doing something wrong when mounting.. do you
> have any example I can use and adapt to my needs?
> Thanks
> Simone
>
> Il giorno mercoledì 27 settembre 2017 15:14:59 UTC+2, Rodrigo Campos ha
> scritto:
>>
>> Can you ping the IP? There might not be any route to that subnet? Have
>> you tried/checked that?
>>
>> And as far as I know, there is no way. Im not 100% sure what problem you
>> are trying to solve, exactly, though. You can have a service type external,
>> configure kube dns stub domains, but having **the same stub domains**
>> resolve to different NS servers according to the kubernetes namespace the
>> query is executed 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>
>> wrote:
>>
>>> Ah yeah that's a typo.. it's setup as consul.service.domain.io but I
>>> don't know why I cannot ping it - are the service and the endpoint properly
>>> declared?
>>> As per the link you provided - I used the stubDomain and gave the
>>> domain.io name a list of Consul IPs - all good, but this will overwrite
>>> the kube-dns configmap in the kube-system namespace so the new dns
>>> resolution will be per node. I need that per namespace or pod.
>>> Is there anyway I can do that?
>>> Hope it's clear and thanks a lot for your help.
>>> Simone
>>>
>>> Il giorno martedì 26 settembre 2017 22:30:12 UTC+2, Rodrigo Campos ha
>>> scritto:
>>>>
>>>> What I tried to say is using this: http://blog.kubernetes.i
>>>> o/2017/04/configuring-private-dns-zones-upstream-nameservers
>>>> -kubernetes.html?m=1
>>>>
>>>> in kube-dns configuration. Not sure how your consul name is and, with
>>>> all you said in the previous mail, a service type 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 records such as myservice.service.domain.io, so your
>>>>> application must be able to contact a dns forwarder which has the zone for
>>>>> that domain.io.
>>>>> What I am using at the moment are stubdomains to include the domain.io
>>>>> but it's at cluster level. What I need to do is to solve different consul
>>>>> names per namespace or pod.
>>>>> I tried to use a service definition as follows:
>>>>>
>>>>> kind: Service
>>>>> apiVersion: v1
>>>>> metadata:
>>>>>   name: consul-resolution
>>>>>   namespace: default
>>>>> spec:
>>>>>   type: ExternalName
>>>>>   externalName: consul.service.domain.io
>>>>>
>>>>> And an endpoint:
>>>>> kind: Endpoints
>>>>> apiVersion: v1
>>>>> metadata:
>>>>>   name: consulresolution
>>>>> subsets:
>>>>>   - addresses:
>>>>>   - ip: 10.24.7.26
>>>>> ports

Re: [kubernetes-users] Resolv.conf override for a pod

[Rodrigo Campos]

Can you ping the IP? There might not be any route to that subnet? Have you
tried/checked that?

And as far as I know, there is no way. Im not 100% sure what problem you
are trying to solve, exactly, though. You can have a service type external,
configure kube dns stub domains, but having **the same stub domains**
resolve to different NS servers according to the kubernetes namespace the
query is executed 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.dandr...@gmail.com> wrote:

> Ah yeah that's a typo.. it's setup as consul.service.domain.io but I
> don't know why I cannot ping it - are the service and the endpoint properly
> declared?
> As per the link you provided - I used the stubDomain and gave the
> domain.io name a list of Consul IPs - all good, but this will overwrite
> the kube-dns configmap in the kube-system namespace so the new dns
> resolution will be per node. I need that per namespace or pod.
> Is there anyway I can do that?
> Hope it's clear and thanks a lot for your help.
> Simone
>
> Il giorno martedì 26 settembre 2017 22:30:12 UTC+2, Rodrigo Campos ha
> scritto:
>>
>> What I tried to say is using this: http://blog.kubernetes.i
>> o/2017/04/configuring-private-dns-zones-upstream-nameservers
>> -kubernetes.html?m=1
>>
>> in kube-dns configuration. Not sure how your consul name is and, with all
>> you said in the previous mail, a service type 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 records such as myservice.service.domain.io, so your
>>> application must be able to contact a dns forwarder which has the zone for
>>> that domain.io.
>>> What I am using at the moment are stubdomains to include the domain.io
>>> but it's at cluster level. What I need to do is to solve different consul
>>> names per namespace or pod.
>>> I tried to use a service definition as follows:
>>>
>>> kind: Service
>>> apiVersion: v1
>>> metadata:
>>>   name: consul-resolution
>>>   namespace: default
>>> spec:
>>>   type: ExternalName
>>>   externalName: consul.service.domain.io
>>>
>>> And an endpoint:
>>> kind: Endpoints
>>> apiVersion: v1
>>> metadata:
>>>   name: consulresolution
>>> subsets:
>>>   - addresses:
>>>   - ip: 10.24.7.26
>>> ports:
>>>   - port: 8300
>>>
>>> But I am not even able to ping consul.service.cnqr.io.. any idea?
>>> Thanks
>>>
>>> Il giorno martedì 26 settembre 2017 16:03:16 UTC+2, Rodrigo Campos ha
>>> scritto:
>>>>
>>>> Sorry, never used consul and I don't follow what you said.
>>>>
>>>> Does it create records like .k8s-service that won't work
>>>> with just a k8s external type service?
>>>>
>>>> Then it might be possible to say to kube dns to use some upstream to
>>>> some domains, probably? I've not played with it, as I don't need it. But
>>>> I'd 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 to solve
>>>>> consul.service.domain but I won't be able to solve external services
>>>>> registered within consul, such as mydatabase.service.domain because I need
>>>>> a NS record.. unless I can use that CNAME as a NS record, but I don't 
>>>>> think
>>>>> it's the right approach..
>>>>>
>>>>>
>>>>> 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
>>>>>>
>>>>>> Il giorno lunedì 25 settembre 2017 18:34:07 UTC+2, R

Re: [kubernetes-users] Resolv.conf override for a pod

[Rodrigo Campos]

What I tried to say is using this:
http://blog.kubernetes.io/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes.html?m=1

in kube-dns configuration. Not sure how your consul name is and, with all
you said in the previous mail, a service type 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.dandr...@gmail.com>
wrote:

> It creates records such as myservice.service.domain.io, so your
> application must be able to contact a dns forwarder which has the zone for
> that domain.io.
> What I am using at the moment are stubdomains to include the domain.io
> but it's at cluster level. What I need to do is to solve different consul
> names per namespace or pod.
> I tried to use a service definition as follows:
>
> kind: Service
> apiVersion: v1
> metadata:
>   name: consul-resolution
>   namespace: default
> spec:
>   type: ExternalName
>   externalName: consul.service.domain.io
>
> And an endpoint:
> kind: Endpoints
> apiVersion: v1
> metadata:
>   name: consulresolution
> subsets:
>   - addresses:
>   - ip: 10.24.7.26
> ports:
>   - port: 8300
>
> But I am not even able to ping consul.service.cnqr.io.. any idea?
> Thanks
>
> Il giorno martedì 26 settembre 2017 16:03:16 UTC+2, Rodrigo Campos ha
> scritto:
>>
>> Sorry, never used consul and I don't follow what you said.
>>
>> Does it create records like .k8s-service that won't work
>> with just a k8s external type service?
>>
>> Then it might be possible to say to kube dns to use some upstream to some
>> domains, probably? I've not played with it, as I don't need it. But I'd
>> 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 to solve consul.service.domain
>>> but I won't be able to solve external services registered within consul,
>>> such as mydatabase.service.domain because I need a NS record.. unless I can
>>> use that CNAME as a NS record, but I don't think it's the right approach..
>>>
>>>
>>> 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
>>>>
>>>> Il giorno lunedì 25 settembre 2017 18:34:07 UTC+2, Rodrigo Campos ha
>>>> scritto:
>>>>>
>>>>> Sorry, I must be missing something. But if you want to resolve to
>>>>> different consul clusters in different kubernetes namespaces, can't you
>>>>> just use a service type external on each?
>>>>>
>>>>> You create a service, named as you want them to contact, and is per ns
>>>>> and returns a CNAME.
>>>>>
>>>>> Wouldn't that do the trick?
>>>>>
>>>>> 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.
>>>>>> The scenario is: I have a  kubernetes cluster which is shared between
>>>>>> different teams, and each team has his own namespace to deploy pods. 
>>>>>> Anyway
>>>>>> these pods must be able to communicate with different consul clusters 
>>>>>> which
>>>>>> are in different environments. Since they are in different envs, we need 
>>>>>> to
>>>>>> point to different DNS. Since pods get dns resolutions from the nodes, 
>>>>>> but
>>>>>> the nodes are shared, we need a way to overwrite the dns settings per 
>>>>>> pods.
>>>>>> I know this is a bad practice - I get what Tim said above in this
>>>>>> thread - but this is just a proof of concept and we'd like to know 
>>>>>> whether
>>>>>> there is a way to do this (the cleaner the better :D)
>>>>>> 

Re: [kubernetes-users] Resolv.conf override for a pod

[Rodrigo Campos]

Sorry, never used consul and I don't follow what you said.

Does it create records like .k8s-service that won't work with
just a k8s external type service?

Then it might be possible to say to kube dns to use some upstream to some
domains, probably? I've not played with it, as I don't need it. But I'd
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.dandr...@gmail.com>
wrote:

> I am afraid it won't work. I will be able to solve consul.service.domain
> but I won't be able to solve external services registered within consul,
> such as mydatabase.service.domain because I need a NS record.. unless I can
> use that CNAME as a NS record, but I don't think it's the right approach..
>
>
> 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
>>
>> Il giorno lunedì 25 settembre 2017 18:34:07 UTC+2, Rodrigo Campos ha
>> scritto:
>>>
>>> Sorry, I must be missing something. But if you want to resolve to
>>> different consul clusters in different kubernetes namespaces, can't you
>>> just use a service type external on each?
>>>
>>> You create a service, named as you want them to contact, and is per ns
>>> and returns a CNAME.
>>>
>>> Wouldn't that do the trick?
>>>
>>> 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.
>>>> The scenario is: I have a  kubernetes cluster which is shared between
>>>> different teams, and each team has his own namespace to deploy pods. Anyway
>>>> these pods must be able to communicate with different consul clusters which
>>>> are in different environments. Since they are in different envs, we need to
>>>> point to different DNS. Since pods get dns resolutions from the nodes, but
>>>> the nodes are shared, we need a way to overwrite the dns settings per pods.
>>>> I know this is a bad practice - I get what Tim said above in this
>>>> thread - but this is just a proof of concept and we'd like to know whether
>>>> there is a way to do this (the cleaner the better :D)
>>>> Thanks
>>>> Simone
>>>>
>>>> Il giorno lunedì 25 settembre 2017 15:15:43 UTC+2, Rodrigo Campos ha
>>>> scritto:
>>>>>
>>>>> Can you explain what do you what to achieve?
>>>>>
>>>>> Maybe changing the configmap kube-dns uses it's enough (and is
>>>>> prepared to be changed easily, now).
>>>>>
>>>>> On Monday, September 25, 2017, Simone D'Andreta <simone@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Tim,
>>>>>> I know what you mean and that's definitely a big issue on our side.
>>>>>> This is for us more a proof of concept to understand if we can go this 
>>>>>> way.
>>>>>> Since I am not a big expert with Kubernetes, I wanted to know if there 
>>>>>> are
>>>>>> solutions I haven't considered that might solve my problem.
>>>>>> That said, I thank you a lot for your explanations here. I  found
>>>>>> something that can help me, though it sets dns names at node level - not
>>>>>> per pod:
>>>>>> https://kubernetes.io/docs/tasks/administer-cluster/dns-cust
>>>>>> om-nameservers/
>>>>>> If I include the different IPs in the stub domains I definitely
>>>>>> should get an answer for the service discovery part. Not ideal, but I 
>>>>>> think
>>>>>> better than mounting and overriding the resolv.conf.
>>>>>> Cheers
>>>>>> Simone
>>>>>>
>>>>>> Il giorno venerdì 22 settembre 2017 19:10:01 UTC+2, Tim Hockin ha
>>>>>> scritto:
>>>>>>>
>>>>>>> you're trying to mount a directory (emptyDir) onto a file
>>>>>>> (/etc/resolv.conf).  Without seeing the error that is a wild guess.
>>>>>

Re: [kubernetes-users] Resolv.conf override for a pod

[Rodrigo Campos]

Sorry, I must be missing something. But if you want to resolve to different
consul clusters in different kubernetes namespaces, can't you just use a
service type external on each?

You create a service, named as you want them to contact, and is per ns and
returns a CNAME.

Wouldn't that do the trick?

On Monday, September 25, 2017, Simone D'Andreta <simone.dandr...@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.
> The scenario is: I have a  kubernetes cluster which is shared between
> different teams, and each team has his own namespace to deploy pods. Anyway
> these pods must be able to communicate with different consul clusters which
> are in different environments. Since they are in different envs, we need to
> point to different DNS. Since pods get dns resolutions from the nodes, but
> the nodes are shared, we need a way to overwrite the dns settings per pods.
> I know this is a bad practice - I get what Tim said above in this thread -
> but this is just a proof of concept and we'd like to know whether there is
> a way to do this (the cleaner the better :D)
> Thanks
> Simone
>
> Il giorno lunedì 25 settembre 2017 15:15:43 UTC+2, Rodrigo Campos ha
> scritto:
>>
>> Can you explain what do you what to achieve?
>>
>> Maybe changing the configmap kube-dns uses it's enough (and is prepared
>> to be changed easily, now).
>>
>> On Monday, September 25, 2017, Simone D'Andreta <simone@gmail.com>
>> wrote:
>>
>>> Hi Tim,
>>> I know what you mean and that's definitely a big issue on our side. This
>>> is for us more a proof of concept to understand if we can go this way.
>>> Since I am not a big expert with Kubernetes, I wanted to know if there are
>>> solutions I haven't considered that might solve my problem.
>>> That said, I thank you a lot for your explanations here. I  found
>>> something that can help me, though it sets dns names at node level - not
>>> per pod:
>>> https://kubernetes.io/docs/tasks/administer-cluster/dns-cust
>>> om-nameservers/
>>> If I include the different IPs in the stub domains I definitely should
>>> get an answer for the service discovery part. Not ideal, but I think better
>>> than mounting and overriding the resolv.conf.
>>> Cheers
>>> Simone
>>>
>>> Il giorno venerdì 22 settembre 2017 19:10:01 UTC+2, Tim Hockin ha
>>> scritto:
>>>>
>>>> you're trying to mount a directory (emptyDir) onto a file
>>>> (/etc/resolv.conf).  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> wrote:
>>>> > I am trying to mount that volume but my container won't start. I
>>>> guess I am
>>>> > doing something wrong. This is the yaml
>>>> > apiVersion: extensions/v1beta1
>>>> > kind: Deployment
>>>> > metadata:
>>>> >   name: {{ template "fullname" . }}
>>>> >   namespace: code
>>>> >   labels:
>>>> > chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}"
>>>> >   annotations:
>>>> > commitSHA: {{ .Chart.AppVersion }}
>>>> > isNotifiable : "true"
>>>> > spec:
>>>> >   replicas: {{ .Values.replicaCount }}
>>>> >   template:
>>>> > metadata:
>>>> >   labels:
>>>> > app: {{ template "fullname" . }}
>>>> >
>>>> > spec:
>>>> >
>>>> >   containers:
>>>> >   - name: {{ .Chart.Name }}
>>>> > image: "{{ .Values.image.repository }}:{{ .Values.image.tag
>>>> }}"
>>>> > imagePullPolicy: {{ .Values.image.pullPolicy }}
>>>> > volumeMounts:
>>>> > - name: new-resolv
>>>> >   mountPath: /etc/resolv.conf
>>>> > command: ["/bin/sh"]
>>>> > args: ["-c", "echo nameserver 10.24.26.102 >
>>>> /etc/resolv.conf"]
>>>> >
>>>> >
>>>> > ports:

Re: [kubernetes-users] Resolv.conf override for a pod

[Rodrigo Campos]

Can you explain what do you what to achieve?

Maybe changing the configmap kube-dns uses it's enough (and is prepared to
be changed easily, now).

On Monday, September 25, 2017, Simone D'Andreta 
wrote:

> Hi Tim,
> I know what you mean and that's definitely a big issue on our side. This
> is for us more a proof of concept to understand if we can go this way.
> Since I am not a big expert with Kubernetes, I wanted to know if there are
> solutions I haven't considered that might solve my problem.
> That said, I thank you a lot for your explanations here. I  found
> something that can help me, though it sets dns names at node level - not
> per pod:
> https://kubernetes.io/docs/tasks/administer-cluster/dns-
> custom-nameservers/
> If I include the different IPs in the stub domains I definitely should get
> an answer for the service discovery part. Not ideal, but I think better
> than mounting and overriding the resolv.conf.
> Cheers
> Simone
>
> Il giorno venerdì 22 settembre 2017 19:10:01 UTC+2, Tim Hockin ha scritto:
>>
>> you're trying to mount a directory (emptyDir) onto a file
>> (/etc/resolv.conf).  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
>>  wrote:
>> > I am trying to mount that volume but my container won't start. I guess
>> I am
>> > doing something wrong. This is the yaml
>> > apiVersion: extensions/v1beta1
>> > kind: Deployment
>> > metadata:
>> >   name: {{ template "fullname" . }}
>> >   namespace: code
>> >   labels:
>> > chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}"
>> >   annotations:
>> > commitSHA: {{ .Chart.AppVersion }}
>> > isNotifiable : "true"
>> > spec:
>> >   replicas: {{ .Values.replicaCount }}
>> >   template:
>> > metadata:
>> >   labels:
>> > app: {{ template "fullname" . }}
>> >
>> > spec:
>> >
>> >   containers:
>> >   - name: {{ .Chart.Name }}
>> > image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
>> > imagePullPolicy: {{ .Values.image.pullPolicy }}
>> > volumeMounts:
>> > - name: new-resolv
>> >   mountPath: /etc/resolv.conf
>> > command: ["/bin/sh"]
>> > args: ["-c", "echo nameserver 10.24.26.102 > /etc/resolv.conf"]
>> >
>> >
>> > ports:
>> >   - name: frontend
>> > containerPort: {{ .Values.port}}
>> > readinessProbe:
>> >   httpGet:
>> > path: {{ .Values.lifecheck }}
>> > port: {{ .Values.port}}
>> >
>> >   volumes:
>> >   - name: new-resolv
>> > emptyDir: {}
>> >
>> > I am using helm to deploy so the variables get expanded via Values.yaml
>> or
>> > other template files.
>> > I think I am just not able to mount that volume properly..
>> > Thanks
>> >
>> >
>> > Il giorno giovedì 21 settembre 2017 19:21:39 UTC+2, Tim Hockin ha
>> scritto:
>> >>
>> >> You'd have to craft a new file and mount it onto your resolv.conf,
>> >> which makes it harder to "just add another line" because you don't
>> >> have the base.
>> >>
>> >> But more than that, what you're asking for is really non-standard
>> >> behavior.  You can't safely add a nameserver record to resolv.conf
>> >> that produces different results.  The behavior of DNS resolvers varies
>> >> widely, and this will cause you pain eventually (kubernetes used to do
>> >> this, it was bad).
>> >>
>> >> Consider this - some resolvers ask all DNS 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
>> >>  wrote:
>> >> > 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,
>> >> >> thanks for your answer. I don't actually need to override all the
>> >> >> settings
>> >> >> in the resolv.conf, I just need to add another nameserver at the
>> top of
>> >> >> the
>> >> >> file. How about if I run a command in the pod such as:
>> >> >>
>> >> >> command: ['/bin/sh', '-c', 'echo 'nameserver x.y.z.w' | cat -
>> >> >> /etc/resolv.conf > temp && mv temp /etc/resolv.conf']
>> >> >> would it work?
>> >> >> Thanks
>> >> >>
>> >> >> Il giorno mercoledì 20 settembre 2017 17:29:16 UTC+2, Tim Hockin ha
>> >> >> scritto:
>> >> >>>
>> >> >>> There's no supported way to do that, in part because it would give
>> up
>> 

Re: [kubernetes-users] steps to migrate Docker image to use kubernetes

[Rodrigo Campos]

value: /agentsvolume
>> >>> >> volumeMounts:
>> >>> >> - name: config
>> >>> >>   mountPath: /c/Users/abc/config
>> >>> >>   volumes:
>> >>> >>- name: config
>> >>> >>  hostPath:
>> >>> >>  path: agentsvolume
>> >>> >>
>> >>> >> On Wed, Sep 20, 2017 at 2:24 PM, Shashank Dutt Jha
>> >>> >> <shashank...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','shashank...@gmail.com');>>
>> >>> >> wrote:
>> >>> >>>
>> >>> >>> Now I get following error: following your suggestion
>> >>> >>>
>> >>> >>> $ kubectl apply -f kuber-agent.yml
>> >>> >>> error: error validating "kuber-agent.yml": error validating data:
>> >>> >>> found
>> >>> >>> invalid field volumes for v1beta1.DeploymentSpec; if you choose to
>> >>> >>> ignore
>> >>> >>> these errors, turn validation off with --validate=false
>> >>> >>>
>> >>> >>>
>> >>> >>> kuber-agent.yml
>> >>> >>>
>> >>> >>> apiVersion: apps/v1beta1
>> >>> >>> kind: Deployment
>> >>> >>> metadata:
>> >>> >>>   name: agent-kuber
>> >>> >>> spec:
>> >>> >>>   replicas: 1
>> >>> >>>   template:
>> >>> >>> metadata:
>> >>> >>>   labels:
>> >>> >>> run: agentc
>> >>> >>> spec:
>> >>> >>>   containers:
>> >>> >>>   - name: agentk
>> >>> >>> image: library/app-agentk:v1
>> >>> >>> env:
>> >>> >>> - name: VOLUMEDIR
>> >>> >>>   value: agentsvolume
>> >>> >>> volumeMounts:
>> >>> >>> - name: config
>> >>> >>>   mountPath: /agentsvolume
>> >>> >>>   volumes:
>> >>> >>>   - name: config
>> >>> >>> hostPath:
>> >>> >>>  path:/c/Users/abc/config
>> >>> >>>
>> >>> >>>
>> >>> >>> On Tue, Sep 19, 2017 at 9:54 PM, 'Tim Hockin' via Kubernetes user
>> >>> >>> discussion and Q <kubernetes-users@googlegroups.com
>> <javascript:_e(%7B%7D,'cvml','kubernetes-users@googlegroups.com');>>
>> wrote:
>> >>> >>>>
>> >>> >>>> Your volume config is not valid.  What you need depends on
>> whether
>> >>> >>>> you
>> >>> >>>> want your volume to literally map `/c/Users/abcd/config` (which
>> you
>> >>> >>>> manage out of band, kubernetes won't touch) into your container
>> or
>> >>> >>>> whether you want just "an empty directory".
>> >>> >>>>
>> >>> >>>> The literal equivalent would be more like:
>> >>> >>>>
>> >>> >>>> ```
>> >>> >>>> apiVersion: apps/v1beta1
>> >>> >>>> kind: Deployment
>> >>> >>>> metadata:
>> >>> >>>>   name: agent-kuber
>> >>> >>>> spec:
>> >>> >>>>   replicas: 1 # optional, defaults to 1
>> >>> >>>>   template:
>> >>> >>>> metadata:
>> >>> >>>>   labels:
>> >>> >>>> run: agentc
>> >>> >>>> spec:
>> >>> >>>>   containers:
>> >>> >>>>   - name: app-agent
>> >>> >>>> image: app-agent
>> >>> >>>> env:
>> >>> >>>> - name: VOLUMEDIR
>> >>> >>>>   value: agentsvolume
>> >>> >>>> volumeMounts:
>> >>> >>>> - name: config
>> >>> >>>>  

Re: [kubernetes-users] Is a pod equivalent to a set of containers with shared IPC, net, PID namespaces and volumes?

[Rodrigo Campos]

At least ir has changed, you won't see pids from other containers in the
pod (although I think is the idea in some future, when containers runtimes
allow it)

On Friday, September 22, 2017,  wrote:

> 在 2016年10月5日星期三 UTC+8上午10:41:17，Anthony Alba写道：
> > Aside from the orchestration, is a pod equivalent to a set of containers
> with shared IPC, net, PID, and volumes?
> >
> >
> > I.e when Kubernetes creates a pod is it doing, behind the scenes, the
> equivalent of
> >
> >
> > docker run --name first app1
> >
> > docker run --net container:first --ipc container:first --pid
> container:first --volumes-from first app2
> >
> > docker run --net container:first --ipc container:first --pid
> container:first --volumes-from first app3
> >
> >
> > where  is obtained from first, or is there more to pods
> than this?
> >
> >
> > Thanks.
>
> I want to share PID among container  in one pod ,how to do ?
>
> --
> 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] Kubernetes Job Opportunity- Michigan

[Rodrigo Campos]

Sorry, but please don't use the Kubernetes users mailing list to recruit
people. The topic of this is to share and ask about Kubernetes specific
problems.

It's not about jobs nor about other technical tools. Please help us to keep
it this way.

On Thursday, September 21, 2017,  wrote:

> I have an opening in the Infrastructure Architecture space. This person
> will be architecting Infrastructure for Applications. On a day to day basis
> this will be responsible for reviews, bringing in new technologies, working
> with POC’s for vendors. There will be a lot of interaction between this
> team and other groups (engineering, operations, vendors) so it is
> imperative that this individual  has good communication written and oral. A
> majority of the focus that this individual will be responsible for will be
> for NGDC specifically around new technologies. Ideally we would like this
> person to come from a midsized to enterprise organization (1,000 servers +)
>
> This individual will need strong experience with Kubernetes which is an
> open source system for automating deployment and management of
> containerized applications. They should be able to engineer and have
> implementation knowledge.) This person should also have strong experience
> with Docker. Docker helps to run and manage applications in isolated
> containers. (Containers:  Containers do not bundle a full operating system,
> only libraries and settings required to make software work are needed. This
> helps to make efficient, lightweight, self-contained system and guarantees
> that the software will always run the same, regardless of where it’s
> deployed.) This individual will be responsible for planning, developing and
> the implementation, and the maintenance of Containers. This will allow Ford
> to extract through the Operating System without interrupting. This is
> cutting edge technology in the industry.
>
>
> Top 3:
> - 1-3+ years of experience with Kubernetes and/or Docker
> Being able to engineer and have implementation knowledge, being able to
> develop Docker images.
> - 3+ years of experience with Cloud technologies
> Currently they are using Azure but open to AWS, PCF
> General understanding of the concepts, usage and strategies.
> - 3-5+ years of experience of engineering VMware
> They are currently on 6.5
>
> Having experience with Vro, Vra
> General understanding of the products and the capabilities
>
> Nice to have: Linux (Suse or Ubuntu) automation, vRealize
>
> If you or anyone you may know is interested in this position please email
> jf...@teksystems.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.
>

-- 
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] steps to migrate Docker image to use kubernetes

[Rodrigo Campos]

t;>> >   claimName: logs-nfs
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, Sep 20, 2017 at 3:03 PM, Shashank Dutt Jha <
>>> shashank...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','shashank...@gmail.com');>>
>>> > wrote:
>>> >>
>>> >> I get this error now:
>>> >>
>>> >> $ kubectl apply -f kuber-agent.yml
>>> >> error: error validating "kuber-agent.yml": error validating data:
>>> found
>>> >> invalid field path for v1.Volume; if you choose to ignore these
>>> errors, turn
>>> >> validation off with --validate=false
>>> >>
>>> >> apiVersion: apps/v1beta1
>>> >> kind: Deployment
>>> >> metadata:
>>> >>   name: agent-kuber
>>> >> spec:
>>> >>   replicas: 1
>>> >>   template:
>>> >> metadata:
>>> >>   labels:
>>> >> run: agentc
>>> >> spec:
>>> >>   containers:
>>> >>   - name: agentk
>>> >> image: library/app-agentk:v1
>>> >> env:
>>> >> - name: VOLUMEDIR
>>> >>   value: /agentsvolume
>>> >> volumeMounts:
>>> >> - name: config
>>> >>   mountPath: /c/Users/abc/config
>>> >>   volumes:
>>> >>- name: config
>>> >>  hostPath:
>>> >>  path: agentsvolume
>>> >>
>>> >> On Wed, Sep 20, 2017 at 2:24 PM, Shashank Dutt Jha <
>>> shashank...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','shashank...@gmail.com');>>
>>> >> wrote:
>>> >>>
>>> >>> Now I get following error: following your suggestion
>>> >>>
>>> >>> $ kubectl apply -f kuber-agent.yml
>>> >>> error: error validating "kuber-agent.yml": error validating data:
>>> found
>>> >>> invalid field volumes for v1beta1.DeploymentSpec; if you choose to
>>> ignore
>>> >>> these errors, turn validation off with --validate=false
>>> >>>
>>> >>>
>>> >>> kuber-agent.yml
>>> >>>
>>> >>> apiVersion: apps/v1beta1
>>> >>> kind: Deployment
>>> >>> metadata:
>>> >>>   name: agent-kuber
>>> >>> spec:
>>> >>>   replicas: 1
>>> >>>   template:
>>> >>> metadata:
>>> >>>   labels:
>>> >>> run: agentc
>>> >>> spec:
>>> >>>   containers:
>>> >>>   - name: agentk
>>> >>> image: library/app-agentk:v1
>>> >>> env:
>>> >>> - name: VOLUMEDIR
>>> >>>   value: agentsvolume
>>> >>> volumeMounts:
>>> >>> - name: config
>>> >>>   mountPath: /agentsvolume
>>> >>>   volumes:
>>> >>>   - name: config
>>> >>> hostPath:
>>> >>>  path:/c/Users/abc/config
>>> >>>
>>> >>>
>>> >>> On Tue, Sep 19, 2017 at 9:54 PM, 'Tim Hockin' via Kubernetes user
>>> >>> discussion and Q <kubernetes-users@googlegroups.com
>>> <javascript:_e(%7B%7D,'cvml','kubernetes-users@googlegroups.com');>>
>>> wrote:
>>> >>>>
>>> >>>> Your volume config is not valid.  What you need depends on whether
>>> you
>>> >>>> want your volume to literally map `/c/Users/abcd/config` (which you
>>> >>>> manage out of band, kubernetes won't touch) into your container or
>>> >>>> whether you want just "an empty directory".
>>> >>>>
>>> >>>> The literal equivalent would be more like:
>>> >>>>
>>> >>>> ```
>>> >>>> apiVersion: apps/v1beta1
>>> >>>> kind: Deployment
>>> >>>> metadata:
>>> >>>>   name: agent-kuber
>>> >>>> spec:
>>> >>>>   replicas: 1 # optional, defaults to 1
>>> >>>>   t

Re: [kubernetes-users] is anybody running the tip of the master branch as a cluster?

[Rodrigo Campos]

On Tue, Sep 19, 2017 at 09:08:22PM +0300, Lubomir I. Ivanov wrote:
> On 19 September 2017 at 17:54, Rodrigo Campos <rodrig...@gmail.com> wrote:
> >
> >
> > On Tuesday, September 19, 2017, Lubomir I. Ivanov <neolit...@gmail.com>
> > wrote:
> >>
> >
> > To make sure your setup is okay, checkout an stable branch or tag, and try
> > to make that work first.
> 
> it was ok with 1.7.5 and the cni worked fine, but i guess i need to
> try a more recent stable build.
> my suspicion is that this issue lies deep and i won't be able to solve
> it easily.
> 
> i really need to be able to run the upstream cluster, though.
> so that my patches are not irrelevant compared to the latest master.

Sure, but to rule out options, can help. That is what I was trying to say (and
the more we can rule out easily is the best, as email for this is not the best
tool :))

> > And just in case, have you checked the guide and links on the readme?
> > https://github.com/kubernetes/kubernetes/blob/master/README.md#to-start-developing-kubernetes
> >
> 
> things like the dev. guide is a lot of information to process.
> https://github.com/kubernetes/community/blob/master/contributors/devel/development.md
> i need to take a careful read at that.

It seems longer than it is if you read it and follow the steps :)

> > I used the guides linked there when writing patches. That goes in more
> > detail, but basically compile and some scripts in "hack/" will help you do
> > the trick, probably (local cluster up, for example).
> >
> 
> thanks, will have a look.
> 
> > Don't hesitate to contact again! :-)
> >
> 
> out of interest what contributions have you made?

My github handle is @rata. I've contributed some proposals, simple patches to
kubernetes and the documentation

> any tips and suggestions for starters?

My first PR was a documentation fix. If you want to code, there are lot of
projects outside of core kubernetes (like kops, autoscaler, etc.) and of course,
kubernetes.

For core kubernetes, I'd look at issues with the for-new-contributors label. For
example: https://github.com/kubernetes/kubernetes/labels/for-new-contributors


> also, what (preferably simpler) areas of kubernetes need work, in your 
> opinion?

I don't really know. Probably all =)

Feel free to join slack and start participating in some SIG or something too! :)

-- 
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] steps to migrate Docker image to use kubernetes

[Rodrigo Campos]

On Tue, Sep 19, 2017 at 07:57:55AM -0700, paperless wrote:
> 
> 
> I have developed a simple Docker image. This can be run using command
> 
> docker run -e VOLUMEDIR=agentsvolume -v /c/Users/abcd/config:/agentsvolume 
> app-agent
> 
> Same thing if I want to run using kubernetes, can someone guide me what are 
> the steps to do it? Do I must create Pods/ Controller or service.. am not 
> able to get clear steps to run using Kubernetes?

Have you take a look to deployments? Just use that with the docker image from a
docker registry.

Not sure what your volume is. Is this how you want this to run on production?

> 
> 
> If I run anything using kuberctl i get following error:
> 
> 
> $ kubectl get pods
> 
> error: group map[extensions:0xc0823b44d0 policy:0xc0823b4540 
> federation:0xc08230f9d0 :0xc08230fea0 apps:0xc08230ff10 batch:0xc0823b4310 
> certificates.k8s.io:0xc0823b4380 componentconfig:0xc0823b43f0 
> authentication.k8s.io:0xc08230ff80 authorization.k8s.io:0xc0823b40e0 
> autoscaling:0xc0823b4150 rbac.authorization.k8s.io:0xc0823b45b0 
> storage.k8s.io:0xc0823b4620] is already registered

I've seen this some time. IIRC you are using quite different kubectl and
kubernetes server versions, or something like that

-- 
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] is anybody running the tip of the master branch as a cluster?

[Rodrigo Campos]

On Tuesday, September 19, 2017, Lubomir I. Ivanov 
wrote:

> hello,
>
> i've tried setuping a local cluster and after a lot of trial and error
> that worked well for 1.7.5.
> but my current employer is interested into kubernetes contributions, so
> i've tried building and running the most recent github maste,r so that i
> can try to understand the project upstream.
>


To make sure your setup is okay, checkout an stable branch or tag, and try
to make that work first.

And just in case, have you checked the guide and links on the readme?
https://github.com/kubernetes/kubernetes/blob/master/README.md#to-start-developing-kubernetes

I used the guides linked there when writing patches. That goes in more
detail, but basically compile and some scripts in "hack/" will help you do
the trick, probably (local cluster up, for example).

Don't hesitate to contact again! :-)

-- 
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] Autoscale pods based on the queue size threshold

[Rodrigo Campos]

I think this can probably be done using custom metrics:
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-custom-metrics

I have not used custom metrics, so it's not something I really know about
:-)

On Tuesday, September 19, 2017, Parth Gandhi  wrote:

> Hi,
> we have an console application running in the pods in kubernetes cluster.
> We have a DB table that keeps the count of incoming queue messages. We need
> to autoscale the pods when the table reaches certain threshold values. can
> this be achieved using k8s HPA? or do we need to write a different logic
> for this?
>
> Thanks.
>
> --
> 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] StatefulSet pod index as label?

[Rodrigo Campos]

On Wed, Sep 13, 2017 at 04:45:51PM -0700, 'Ahmet Alp Balkan' via Kubernetes 
user discussion and Q wrote:
> I'm curious if having ordinal index
> 
> for
> StatefulSet pods would be useful, if Kubernetes exported this information
> as a label on the pod.
> 
> This way a user could create a Service easily selecting a pod in the
> StatefulSet through its index label, and they would not worry about
> maintaining a manual Endpoints list (+an headless Service) to achieve this.
> 
> I don't use StatefulSets nor I have an use case for this, but I'm curious
> if this is something users would need at all.

After thinking a while, I don't see a use case, honestly. I can't think what can
be easier if a service can match ordinarls in stateful sets.

Did you have some rough idea or intuition? (I read you said you didn't have a
use case, but maybe some "gut feeling" or something?)



Thanks a lot,
Rodrigo

-- 
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 test your code with Kubernetes

[Rodrigo Campos]

Although Kubernetes can be involved, I think testing should also work as if
you are not using Kubernetes. How did you test these before Kubernetes?

But one trick you can try in Kubernetes is minikube for the app you are
running and a service type external pointing to the URL the other apps are
running in some cluster.

But again, this, for example, shouldn't be different than doing normal
deployment and just point to some other place to consume other applications
(if your pod is really simple).

On Saturday, September 9, 2017, Rami Shalom  wrote:

> Hi all, I am looking for ways to test my code before going through the
> cycles of integration tests in CI.
>
> The code i'm working on is part of a bigger project, 40-50 containers,
> some are Java based (memory consumption can be high);
>
>
> I can unit-test my code but it's out of the application context so it gets
> me so far.
>
> Run time of the entire application may be too long and require a lot of
> resources for me (others) to run quick code change cycles and test every
> change.
>
>
> I tried to "minimize" the app and used Minikube but it does not scale high
> enough for the tests i need to run.
>
>
> What other alternatives are available if the test requires more than one
> kubernetes node, or the load is greater than what a laptop can hold in a
> single node (which is what Minikube lets you run)?
>
>
> Thanks.
>
> --
> 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] Unable to send emails from kuberenetes pod

[Rodrigo Campos]

No. Have you tried a telnet from the pod? What did you find while
debugging? What do you see in a traceroute, etc.?

On Thursday, September 7, 2017,  wrote:

> Hi All,
>
> I am getting connection refused error while sending email and receving
> emails from pod.
>
> Do i need to configure anything explictly to connect to ports.
>
> Kindly assist
>
> --
> 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.