fix: orphan SA mongodb-enterprise-database-pods and mongodb-enterprise-ops-manager #294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have noticed instances of orphan resources in your Kubernetes configuration files. Deploying Kubernetes resources that are not being actively used or referenced by any other resources in the cluster can lead to orphan resources. These orphan resources consume unnecessary resources and can potentially cause confusion or clutter within the cluster. Additionally, we provide anecdotal evidence from topolvm-topolvm#484 regarding the orphan resource defect.
SA mongodb-enterprise-database-pods and mongodb-enterprise-ops-manager do not bind to any role or cluster role, and they can be considered orphan resources.
delete mongodb-enterprise-database-pods and mongodb-enterprise-ops-manager or bind them to a role or cluster role.
All Submissions:
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).