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

[FEATURE_REQUEST] Need check for priorityClassName value #794

Open
marcmognol opened this issue Jun 10, 2024 · 0 comments
Open

[FEATURE_REQUEST] Need check for priorityClassName value #794

marcmognol opened this issue Jun 10, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers new-check

Comments

@marcmognol
Copy link

Description of the problem/feature request
I would like to ensure that my Deployment and Daemonset has priorityClassName value defined.

Description of the existing behavior vs. expected behavior
Current behavior: no error when a Deployment or Daemonset has no priorityClassName value.
Expected behavior: kube-linter should throw an error when priorityClassName is not defined.

Additional context
If this check is not requested enough by the community, is it possible to have a template which let me create a customCheck by myself.

The template could be take two parameters:

  • propertyName : string (ex priorityClassName)
  • possibleValues: array of string (possible values for priorityClassName )

Thanks
Marc

@janisz janisz added enhancement New feature or request good first issue Good for newcomers new-check labels Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers new-check
Projects
None yet
Development

No branches or pull requests

2 participants