Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.2.4, 2.3.0, 2.3.1, 2.3.2, 2.4.0
-
9 - Krakend, 10 - Krackeverlasting, 1 - Levianthanning, 2 - LeVIAthan or LeviaTHAN
-
0
Description
Currently the persistence secrets have exact same name as the cluster. This can cause problems if a cluster is quickly recreated as persistence secret from the previous instance could be reused resulting in unexpected behavior.
Since we never want to delete/overwrite the persistence secret we will need to wait to see if it's being deleted, then recreate (with retry) until we are able to create a new one within cluster.newCluster (cluster.go).
Attachments
Issue Links
- blocks
-
K8S-3052 2.4.1 Release Notes
- Resolved