I set up a cloud cluster with two cascading edge clusters to verify.
1). When the mission matches and the content is to deploy a deployment and the status check command is empty:
The mission status shows the "Kubectl get [mission_content_resource]" of the cascading edge clusters as expected. And the status is update automatically.
2). When the mission does not match
3). when the customer specify its own status check command
Here I set the status check command as follows, to read the deployment status message:
This PR implements the idea about extending the mission CRD to include the section of status to show how mission content is running in the cascading edge clusters. The idea is explained in slides https://github.com/pdgetrf/ArktosEdge/blob/main/slides/extend_mission.pptx.
Verification:
I set up a cloud cluster with two cascading edge clusters to verify.
1). When the mission matches and the content is to deploy a deployment and the status check command is empty:
The mission status shows the "Kubectl get [mission_content_resource]" of the cascading edge clusters as expected. And the status is update automatically.
2). When the mission does not match
3). when the customer specify its own status check command
Here I set the status check command as follows, to read the deployment status message: