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

[Enhancement] Improve description of scale deployment to zero policy #949

Closed
2 tasks done
chipzoller opened this issue Mar 21, 2024 · 0 comments · Fixed by #955
Closed
2 tasks done

[Enhancement] Improve description of scale deployment to zero policy #949

chipzoller opened this issue Mar 21, 2024 · 0 comments · Fixed by #955
Labels
Contribfest Good first issues for KubeCon EU 2024 enhancement New feature or request good first issue Good for newcomers

Comments

@chipzoller
Copy link
Member

Kyverno Version

1.11

Kubernetes Version

1.27

Kubernetes Platform

K3d

Description

The Scale Deployment to Zero policy could use a sentence instructing/warning users they must modify Kyverno's ConfigMap to remove or change the line excludeGroups: system:nodes in order for the policy to work since 1.10.

Steps to reproduce

  1. Read description.

Expected behavior

Policy has an updated description.

Screenshots

No response

Kyverno logs

No response

Slack discussion

https://kubernetes.slack.com/archives/C032MM2CH7X/p1710953463123979

Troubleshooting

  • I have read and followed the documentation AND the troubleshooting guide.
  • I have searched other issues in this repository and mine is not recorded.
@chipzoller chipzoller added enhancement New feature or request good first issue Good for newcomers labels Mar 21, 2024
@realshuting realshuting added the Contribfest Good first issues for KubeCon EU 2024 label Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contribfest Good first issues for KubeCon EU 2024 enhancement New feature or request good first issue Good for newcomers
Projects
Development

Successfully merging a pull request may close this issue.

2 participants