We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
+default
As per https://book.kubebuilder.io/reference/markers/crd-validation, kubebuilder respects its own +kubebuilder:default. It would be beneficial for end users to also respect +default.
+kubebuilder:default
Naive
Add support in controller-tools:
controller-tools
diff --git a/pkg/crd/markers/validation.go b/pkg/crd/markers/validation.go index 06d1cab6..aaae336c 100644 --- a/pkg/crd/markers/validation.go +++ b/pkg/crd/markers/validation.go @@ -91,6 +91,8 @@ var FieldOnlyMarkers = []*definitionWithHelp{ must(markers.MakeAnyTypeDefinition("kubebuilder:default", markers.DescribesField, Default{})). WithHelp(Default{}.Help()), + must(markers.MakeAnyTypeDefinition("default", markers.DescribesField, Default{})). + WithHelp(Default{}.Help()), must(markers.MakeAnyTypeDefinition("kubebuilder:example", markers.DescribesField, Example{})). WithHelp(Example{}.Help()),
The text was updated successfully, but these errors were encountered:
Add support for +default markers
73cdab1
https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1929-built-in-default#summary https://github.com/kubernetes-sigs/kubebuilder/issues/3896
Opened #938 to add this support
/transfer controller-tools
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Problem statement
As per https://book.kubebuilder.io/reference/markers/crd-validation, kubebuilder respects its own
+kubebuilder:default
. It would be beneficial for end users to also respect+default
.Related issues/PRs
Proposed solution
Naive
Add support in
controller-tools
:The text was updated successfully, but these errors were encountered: