search

k8ssandra / k8ssandra-operator

The Kubernetes operator for K8ssandra
https://k8ssandra.io/
Apache License 2.0
173 stars 79 forks source link

K8SSAND-1869 ⁃ Medusa ConfigMaps should be deleted when K8ssandraCluster is deleted #751

Open adutra opened 2 years ago

adutra commented 2 years ago

The K8ssandra controller creates ConfigMaps for Medusa in all data planes, local and remote, but it does not remove such objects when the K8ssandraCluster object is deleted. This is what we do for Stargate, Reaper, and all other objects that are created by the K8ssandra controller.

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: K8OP-268

dnugmanov commented 1 year ago

@adutra hi,

This is what we do for Stargate, Reaper, and all other objects that are created by the K8ssandra controller.

Is it already implemented or work is ongoing? Because now after deleting k8ssandracluster following secrets are still remaining

        fmt.Sprintf("%s-ca-keystore", dcName),
        fmt.Sprintf("%s-keystore", dcName),
        fmt.Sprintf("%s-superuser", k8ssandraName),
        fmt.Sprintf("%s-medusa", k8ssandraName),
        fmt.Sprintf("%s-reaper", k8ssandraName),
        fmt.Sprintf("%s-reaper-jmx", k8ssandraName),
        fmt.Sprintf("%s-reaper-ui", k8ssandraName),

Or issue considered about work not only CM deleting and also secrets?