[Starlingx-discuss] [Containers]How to put a node in FAIL

[Perez Carranza, Jose]

Thanks Bart, 

Sorry for the reference, here is [1], and thanks for your notes, they will helpe a lot !!

1. https://review.openstack.org/#/c/597123/

Regards,
José


> -----Original Message-----
> From: Wensley, Barton [mailto:Barton.Wensley at windriver.com]
> Sent: Monday, April 15, 2019 10:47 AM
> To: Perez Carranza, Jose <jose.perez.carranza at intel.com>; starlingx-
> discuss at lists.starlingx.io
> Subject: RE: [Containers]How to put a node in FAIL
> 
> José,
> 
> You forgot the reference. A couple notes for you:
> - Powering off the node would be a good way to test this.
> - Using "kubectl get nodes", you should see the status change to NotReady in
> roughly 20 seconds or so.
> - Kubernetes will not evict most of the kube-system and openstack pods, since
> these pods are either tied to a particular node (e.g. in a DaemonSet) or
> prevented from being co-located with anti-affinity policies.
> - You probably want to test this by launching your own pod and then verifying
> that it gets evicted when the node it is running on is powered down.
> 
> Bart
> 
> -----Original Message-----
> From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com]
> Sent: April 15, 2019 10:48 AM
> To: starlingx-discuss at lists.starlingx.io
> Subject: [Starlingx-discuss] [Containers]How to put a node in FAIL
> 
> Hi All
> 
> I'm validating this feature [1] and one of the points to validate is that pods get
> EVICTED on failed nodes in less than 50 seconds, Did anyone knows a way to
> put the node (controller or compute) on FAIL?
> 
>  I tried turning off the node but seems like this is not detected as failed node
> because pods are not evicted and actually the status of the node is show as
> OFFLINE.
> 
> Regards,
> José
> 
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss