852ec5ed53
At startup, there might be pods that are left in unknown states. The k8s-pod-recovery service takes care of recovering these unknown pods in specific namespaces. To fix this for custom apps that are not part of starlingx, we modify the service to look into the /etc/k8s-post-recovery.d directory for conf files. Any app that needs to be recovered by this service will have to create a conf file e.g the app-1 will create /etc/k8s-post-recovery.d/APP_1.conf which will contain the following: namespace=app-1-namespace Closes-Bug: 1917781 Signed-off-by: Mihnea Saracin <Mihnea.Saracin@windriver.com> Change-Id: I8febdb685d506cff3c34946163612cafdab3e3a8 |
||
|---|---|---|
| .. | ||
| armada/centos | ||
| armada-helm-toolkit | ||
| chartmuseum/centos | ||
| cni/sriov-cni/centos | ||
| containerd/centos | ||
| docker-distribution/centos | ||
| etcd/centos | ||
| helm/centos | ||
| k8s-pod-recovery/centos | ||
| kubernetes/centos | ||
| n3000/centos | ||
| plugins | ||