Fix status sub-resource not found error on updating status

[vizv]

Description of the change

Add missing sub-resource for status, which causes error on updating status.

Benefits

SealedSecret resources in my Argo CD no longer stuck after this patchset.

Possible drawbacks

Nothing.

Applicable issues

• fixes After update to Helm release 2.6.4 Error updating SealedSecret "secret" not found message in log #961

Additional information

See #961 for details, the issue was introduced in #941 when generating CRD with controller-gen, and subresources was missed from generation, however status sub-resource is used in

sealed-secrets/pkg/client/clientset/versioned/typed/sealedsecrets/v1alpha1/sealedsecret.go

Line 131 in 0e3ca3f

SubResource("status").

which causes the error

[vizv]

@josvazg to reproduce this issue for #961 (comment):

• create a kind cluster with kind create cluster
• install the latest SealedSecret helm chart (v2.6.4) with helm upgrade --install sealed-secrets sealed-secrets --repo https://bitnami-labs.github.io/sealed-secrets --namespace kube-system --create-namespace
• create a SS resource with kubectl create secret generic test --dry-run=client --from-literal foo=bar -o yaml | kubeseal --controller-name sealed-secrets -o yaml | kubectl apply -f -
• check the log with kubectl -n kube-system logs -f deployments/sealed-secrets

You'll see the error Error updating SealedSecret default/test status: sealedsecrets.bitnami.com "test" not found, and SS resource doesn't contain a status field

[vizv]

btw the fix was tested with regenerate the CRD with make manifests using controller-gen v0.9.2, and then apply the modified CRD. The SS status gets updated, the error is gone from SS controller, and Argo CD SS resource no longer stuck in processing state.

[alemorcuq]

Great, thank you!