Basic Functional Test (REC-31)

[REC-33] pod health check Created: 26/Aug/19  Updated: 22/Oct/19

Status: In Progress
Project: Radio Edge Cloud
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Medium
Reporter: Deepak Kataria Assignee: Indumathi Buddi
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This test is to check the health of K8s PODs. Two types of health checks can be performed:

  1. Liveness Test
  2. Readiness Test

For (1), a liveness probe will check if the container which is configured in the POD is still running. If the liveness probe fails, the kubelet will kill the container and re-start the container

For (2), a readiness probe will determine if a container is ready to service requests. If the readiness probe fails, the endpoints controller will ensure that the container has its IP address removed from the endpoints of all services. A readiness probe can be used to signal to the endpoints controller that even though a container is running, it should not receive any traffic from a proxy.



 Comments   
Comment by Indumathi Buddi [ 22/Oct/19 ]

https://gerrit.akraino.org/r/#/c/ta/cloudtaf/+/1809/2/testcases/basic_func_tests/tc_002_pod_health_check.py

 

Comment by Deepak Kataria [ 21/Oct/19 ]

Indu committed code and it is under review.

Comment by Deepak Kataria [ 18/Oct/19 ]

Indu completed automation. She will commit code to-day (10/18/19).

Comment by Deepak Kataria [ 16/Oct/19 ]

This is work in progress. Indu will try to test this today (10/16/19).

Comment by Deepak Kataria [ 15/Oct/19 ]

Indu is working on automation, since aknode82 is back up now.

Comment by Deepak Kataria [ 14/Oct/19 ]

Manual testing is complete, and test automation is in progress.

Comment by Deepak Kataria [ 11/Oct/19 ]

This is still in progress.

Comment by Deepak Kataria [ 10/Oct/19 ]

This continues to be in progress.

Comment by Deepak Kataria [ 09/Oct/19 ]

Indu is working on automating this with ROBOT, in progress

Comment by Deepak Kataria [ 08/Oct/19 ]

Indu has completed manual testing and is automating with ROBOT.

Comment by Deepak Kataria [ 04/Oct/19 ]

Indu created POD with readiness test and is manually testing on OE2 cluster. She will automate tests as next step.

Comment by Deepak Kataria [ 03/Oct/19 ]

No update on this.

Comment by Deepak Kataria [ 02/Oct/19 ]

No update on this.

Comment by Deepak Kataria [ 01/Oct/19 ]

No update on this.

Comment by Deepak Kataria [ 26/Sep/19 ]

No update on this.

Comment by Deepak Kataria [ 25/Sep/19 ]

No update on this.

Comment by Deepak Kataria [ 19/Sep/19 ]

No update on this since OE1 cluster was not available. OE1 is back up today, Indu will look into this after addressing review comments on REC-11, REC-13, REC-34 and REC-35

Comment by Deepak Kataria [ 18/Sep/19 ]

Indu will move to OE1 to continue testing. She has access to service endpoints now.

Comment by Deepak Kataria [ 17/Sep/19 ]

No update on this. Will start working on this to-day (9/17).

Comment by Deepak Kataria [ 16/Sep/19 ]

No update on this

Comment by Deepak Kataria [ 13/Sep/19 ]

Indu did not have a chance to work on this. She will create a POD with Readiness Test.

Comment by Deepak Kataria [ 09/Sep/19 ]

No update on this.

Comment by Deepak Kataria [ 05/Sep/19 ]

Sonobuoy is already doing Liveness Test, Indu confirms. Indu is exploring Readiness Test, she should look at the Service Watcher in REC, to figure out the Readiness test case

Comment by Deepak Kataria [ 04/Sep/19 ]

Indu to check support for Liveness Test in Sonobuoy; Indu to do Readiness Test using DANM endpoint controller as suggested by Levente

Comment by Levente Kálé [ 04/Sep/19 ]

considering this is basic K8s functionality, isn't it covered by sounoboy or some existing conformance tests?

what is REC specific related functionality and could be tested is the second, related to readyness probes.

you remember DANM supports K8s Services for multiple interfaces. in this case it is DANM who is responsible to creating, and deleting the Endpoints of a Service.

" If the readiness probe fails, the endpoints controller will ensure that the container has its IP address removed from the endpoints of all services. A readiness probe can be used to signal to the endpoints controller that even though a container is running, it should not receive any traffic from a proxy." -> this functionality could be tested with multi-NIC Services, managed by DANM endpoint controller

Comment by Deepak Kataria [ 03/Sep/19 ]

Indu is working on 2 types of tests. She will test manually and then automate with ROBOT.

Generated at Sat Feb 10 06:04:33 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.