digitalocean / do-operator

The Kubernetes Operator for DigitalOcean
Apache License 2.0
77 stars 10 forks source link

Delete never succeeds if you delete an object that would never have formed a cluster #4

Closed jhgaylor closed 2 years ago

jhgaylor commented 4 years ago

This is the example from the readme. If you apply it, there are errors because num_nodes should be numNodes. If you then delete that object it never gets cleared out. If you manually delete the finalizers from the object using kubectl edit database example then the object clears out immediately.

I think the operator can reject the illegal object before it ever gets into the cluster so maybe this needn't be fixed directly.

apiVersion: doop.do.co/v1alpha1
kind: Database
metadata:
  name: example
spec:
  name: example
  engine: redis
  version: "5"
  size: db-s-2vcpu-4gb
  region: sfo2
  num_nodes: 2
  tags:
  - test
  - doop
adamwg commented 2 years ago

I believe this is not relevant to the new version of the operator. Closing this out.