Can think of potential scenarios where we might want to deny creation of new SharedSecret/SharedConfigMap:
- A Custom Resource is created where the source entity is the target in an existing Custom Resource & vice-versa, basically creating dependency loops.
- Other Scenarios?
Can think of potential scenarios where we might want to deny creation of new SharedSecret/SharedConfigMap: