Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcard use in role and cluster role policy does not support list of exclude clusterrole. #1372

Open
sumanraja opened this issue Aug 23, 2024 · 0 comments

Comments

@sumanraja
Copy link

ISSUE TITLE: Kubernetes clusters should minimize wildcard use in role and cluster role policy does not support list of exclude clusterrole.


'PolicyName: Kubernetes clusters should minimize wildcard use in role and cluster role.

ISSUE DESCRIPTION (this template): Kubernetes clusters should minimize wildcard use in role and cluster role policy always show non compliance if you deploy cluster with calico plugin. Calico network plugin is aks managed add-on however tigera-operator cluster role does not under default exclusion list.

Details of the scenario you tried and the problem that is occurring

If you deploy AKS cluster with calico plugin, this wild card clusterrole policy alway show non-compliance state.

Verbose logs showing the problem

Suggested solution to the issue

Either policy need enhancement and support exclude clusterrole parameter, currently support only exclude namespace.
Otherwise include https://store.policy.core.windows.net/kubernetes/block-wildcard-roles/v1/template.yaml
With tigera-operator as AKS_MANAGED_CLUSTER_ROLE_NAMES.

If policy is Guest Configuration - details about target node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant