-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add omitempty for SchedulerName, ImagePullSecrets, HostNetwork #3032
Add omitempty for SchedulerName, ImagePullSecrets, HostNetwork #3032
Conversation
/kind bug |
/lgtm This doesn't qualify as a breaking change because users shouldn't have been depending on specifics like |
Thanks for the clarification. I guess my concern is more about the request for developers working around the API. Those fields are included even when not declared (e.g., when I tried to introduce pod template support in |
ee3d62e
to
ca8e352
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pritidesai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
This pull request adds
omitempty
for the following pod template fields:As documented in #17,
SchedulerName
andHostNetwork
are designated as optional fields and as such should be omitted if not declared. Why ImagePullSecrets is not considered optional seems interesting to me, and perhaps should be discussed a bit further before being introduced. But overall, it might have been overlooked when introducing #2547.Please let me know if there should be further discussions with regard to this being a breaking change.
Submitter Checklist
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes