Deleting k8s manifest does not properly reflect deletion

[charlessteindell]

Hello all!

Per the documentation, deleting a kubectl yaml file should cause for the namespaces to be cleared of reflected secrets. This was functioning in a previous version 7.1.288; however, in new version 9.0.322, this seems to be broken.

System:

• OS: SUSE SLES 15 SP4, and SUSE SLES 15 SP6
• K8S Engine: Rke2
• Resources for reflector: CPU=100m, Memory=256Mi

Steps to reproduce:

1. Create a namespace called mynamespace
2. apply the following secret via kubectl apply -f secret.yml:
   apiVersion: v1 kind: Secret metadata: name: turkey namespace: mynamespace annotations: reflector.v1.k8s.emberstack.com/reflection-allowed: "true" reflector.v1.k8s.emberstack.com/reflection-auto-enabled: "true" data: name: "test"
3. Note that the secret "turkey" is reflected across namespaces
4. Run kubectl delete -f secret.yml
5. Note that the secret "turkey" is deleted only in the namespace called mynamespace; however, the other namespaces all still show the secret as previously reflected, as if it was not deleted.

I am happy to share any info that you need to resolve this issue. Please let me know at your earliest convenience and I'd be happy to demonstrate.

Thank you,
Charlie

[winromulus]

Should be fixed in the latest release. Please update and if the issue persists, reopen please.