You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
Thanks
Marc
The text was updated successfully, but these errors were encountered: