Open Issues Need Help
View All on GitHub requiredfields/optionalfields: false positive on metav1.Time and corev1.LocalObjectReference with omitzero about 4 hours ago
help wanted
kind/bug help wanted good first issue
[bug] Minimum length linter should explain required fields are valid choices for structs 4 months ago
help wanted good first issue
Allow custom messages for PreferredMarkers linter 5 months ago
help wanted good first issue
help wanted
kind/bug help wanted
Update all analyzers to output `<struct name>.<field name>` for more precise error message output 8 months ago
help wanted good first issue
kind/feature help wanted lifecycle/frozen
KAL does not detect zero value invalid via string validation markers on underlying struct 8 months ago
kind/bug help wanted
help wanted good first issue
KAL incorrectly recommends making a *[]corev1.Taint field with MinItems=0 a non-pointer 8 months ago
kind/bug help wanted
New Linter: DefaultOrRequired 8 months ago
kind/feature help wanted good first issue
New Linter: references 8 months ago
kind/feature help wanted good first issue
New Linter: arrayofstruct 9 months ago
kind/feature help wanted good first issue lifecycle/frozen
kind/feature help wanted
optionalfields linter does not detect enum marker on type about 1 year ago
AI Summary: The `optionalfields` linter in the Kube API Linter (KAL) incorrectly flags optional fields with enum validation as having invalid zero values. The task is to modify the linter to recognize and correctly handle fields with both `+optional` and `+kubebuilder:validation:Enum` annotations, preventing false positives.
Complexity:
4/5
kind/bug help wanted