Only try create secret if not present

[0sewa0]

Users can limit how many secrets can be created in their namespaces.

However, if that limit is reached and our namespace secret is already in the namespace, our update mechanism fails.
Because we try to create a new secret and would expect a Already Exists error, but in such case, we get an alreadyLimit reached error back, which crashes our logic.

How can this be tested?

Example resource quota:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: secret-quota
  namespace: test
spec:
  hard:
    count/secrets: "2"

Use a dyankube that would inject into the namespace that has the quota. Wait for an update. Should not fail. (the secret number may change depending what you deploy 😬 )

Checklist

• [ ] Unit tests have been updated/added
• PR is labeled accordingly
• I have read and understood the contribution guidelines