da0de8cff7
* Make sure the statefulset that is deleted manually gets re-created.
Per report and analysis by Manuel Gomez.
* Move the existence checks for other objects out of the Create functions.
create{Object} for services, endpoints and PDBs refused to continue if
there is a cached definition in the cluster, however, the only place
where it makes sense is when creating a new cluster. Note that contrary
to the statefulset this doesn't fix any issues, since those definitions
were nullified correspondingly when the sync code detected there is no
object present in the Kubernetes cluster.
|
||
|---|---|---|
| .. | ||
| cluster.go | ||
| cluster_test.go | ||
| exec.go | ||
| filesystems.go | ||
| k8sres.go | ||
| pg.go | ||
| pod.go | ||
| resources.go | ||
| sync.go | ||
| types.go | ||
| util.go | ||
| volumes.go | ||