-
Notifications
You must be signed in to change notification settings - Fork 689
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make all ContourConfiguration CRD fields optional (#4451)
Removes all kubebuilder defaults from ContourConfiguration fields and switches them to pointers with the `omitempty` JSON tag to make them all fully optional. Defaults are then applied internally by Contour. Signed-off-by: Steve Kriss <krisss@vmware.com>
- Loading branch information
Showing
25 changed files
with
1,940 additions
and
3,315 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
## All ContourConfiguration CRD fields are now optional | ||
|
||
To better manage configuration defaults, all `ContourConfiguration` CRD fields are now optional without defaults. | ||
Instead, Contour itself will apply defaults to any relevant fields that have not been specified by the user when it starts up, similarly to how processing of the Contour `ConfigMap` works today. | ||
The default values that Contour uses are documented in the `ContourConfiguration` CRD's API documentation. |
Oops, something went wrong.