Link to the correct issue:
https://github.com/kubernetes/kubernetes/issues/41283
On Friday, February 10, 2017 at 6:30:27 PM UTC-8, Saad Ali wrote:
>
> *tl;dr - 1.5.3 and 1.4.9 are being postponed to early next week.*
>
> The 1.5.3 and 1.4.9 releases were scheduled to go out today, February 10.
>
Hi, there
I'd like to deploy an app to monitor the pod creation/deletion events using
k8s watch api , and then persist the startTime and deleteTime of a pod.
With these persistent data, I am able to calculate the
resource usage(cpu/memory) of a pod. But what if the monitoring app crashed
and m
Ohh, now I see. I didn't get the original mail. Thanks!
On Sunday, February 12, 2017, 'David Oppenheimer' via Kubernetes user
discussion and Q&A wrote:
>
>
> On Sun, Feb 12, 2017 at 6:21 AM, Rodrigo Campos > wrote:
>
>> On Sunday, February 12, 2017, 'David Oppenheimer' via Kubernetes user
>> di
On Sun, Feb 12, 2017 at 6:21 AM, Rodrigo Campos wrote:
> On Sunday, February 12, 2017, 'David Oppenheimer' via Kubernetes user
> discussion and Q&A wrote:
>
>> [+kubernetes-users; kubernetes-dev to bcc]
>>
>
> Just curious, why kubernetes-dev?
>
The original message and some replies were sent t
No, this is not possible. You can either run multiple containers in a
single pod per node, or use multiple daemonsets.
/MR
On Sun, Feb 12, 2017, 09:45 'David Oppenheimer' via Kubernetes user
discussion and Q&A wrote:
> [+kubernetes-users; kubernetes-dev to bcc]
>
>
> On Sun, Feb 12, 2017 at 12:
On Sunday, February 12, 2017, 'David Oppenheimer' via Kubernetes user
discussion and Q&A wrote:
> [+kubernetes-users; kubernetes-dev to bcc]
>
Just curious, why kubernetes-dev?
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" gr
[moving kubernetes-dev back to bcc]
On Sun, Feb 12, 2017 at 1:11 AM, wrote:
> Hi David
> Thanks. You mean both nodeSelector and node affinity right. As per this
> doc https://kubernetes.io/docs/admin/daemons/#running-
> pods-on-only-some-nodes, both nodeSelector and node affinity work.
>
I bel
Hi David
Thanks. You mean both nodeSelector and node affinity right. As per this
doc https://kubernetes.io/docs/admin/daemons/#running-pods-on-only-some-nodes,
both nodeSelector and node affinity work.
But yeah my questions was about pod affinity/anti affinity which you are
saying doesnt work w
[+kubernetes-users; kubernetes-dev to bcc]
On Sun, Feb 12, 2017 at 12:41 AM, wrote:
> I want a single DaemonSet to run two pods(n pods) on each node(based on
> some label of the node), is that possible. From the documentation i dont
> see if thats possible, but i may be missing something
>
> -
[+kubernetes-users; kubernetes-dev to bcc]
No, and actually affinity doesn't work with DaemonSet right now either. The
problem is that DaemonSet does its own scheduling and doesn't yet share all
of the scheduler code.
The only affinity-related constraint that works with DaemonSet right now is
nod
10 matches
Mail list logo
