Is there an existing issue already for this bug?
I have read the troubleshooting guide
I am running a supported version of CloudNativePG
Contact Details
No response
Version
1.29 (latest patch)
What version of Kubernetes are you using?
1.34
What is your Kubernetes environment?
Self-managed: k3s
How did you install the operator?
Helm
What happened?
I ran kubectl cnpg destroy -n cnpg-system central-cluster central-postgres-1, noticing a typo yet the command succeeded.
central-cluster does not exist, the cluster is called central-postgres
The command however, deleted instance central-postgres-1 as requested and returned with:
Instance central-postgres-1 of cluster central-cluster is destroyed
Seems that some sort of validation did not happen? I'd expect it to fail as the cluster name specified does not exist.
Cluster resource
Relevant log output
Code of Conduct
Is there an existing issue already for this bug?
I have read the troubleshooting guide
I am running a supported version of CloudNativePG
Contact Details
No response
Version
1.29 (latest patch)
What version of Kubernetes are you using?
1.34
What is your Kubernetes environment?
Self-managed: k3s
How did you install the operator?
Helm
What happened?
I ran
kubectl cnpg destroy -n cnpg-system central-cluster central-postgres-1, noticing a typo yet the command succeeded.central-clusterdoes not exist, the cluster is calledcentral-postgresThe command however, deleted instance
central-postgres-1as requested and returned with:Instance central-postgres-1 of cluster central-cluster is destroyedSeems that some sort of validation did not happen? I'd expect it to fail as the cluster name specified does not exist.
Cluster resource
Relevant log output
Code of Conduct