-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Don't output empty sections in the manifests #8317
Merged
k8s-ci-robot
merged 2 commits into
kubernetes:master
from
justinsb:clean_up_empty_manifest_sections
Jan 12, 2020
Merged
Don't output empty sections in the manifests #8317
k8s-ci-robot
merged 2 commits into
kubernetes:master
from
justinsb:clean_up_empty_manifest_sections
Jan 12, 2020
Conversation
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb 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 |
In our kube-dns manifest for 1.6 we often had an empty section, normalization converted this to `{}` which causes `kubectl apply` to fail. We can simply skip empty objects when outputing.
(The tests are split out for easier cherry-picking, should we choose to)
97bf64b
to
cf5c53c
Compare
/lgtm |
This was referenced Jan 12, 2020
k8s-ci-robot
added a commit
that referenced
this pull request
Jan 12, 2020
…-origin-release-1.17 Automated cherry pick of #8317: Don't output empty sections in the manifests
k8s-ci-robot
added a commit
that referenced
this pull request
Jan 18, 2020
…-origin-release-1.16 Automated cherry pick of #8317: Don't output empty sections in the manifests
k8s-ci-robot
added a commit
that referenced
this pull request
Jan 22, 2020
…-origin-release-1.15 Automated cherry pick of #8317: Don't output empty sections in the manifests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our kube-dns manifest for 1.6 we often had an empty section,
normalization converted this to
{}
which causeskubectl apply
to fail.We can simply skip empty objects when outputing.
Tests are split into a separate commit for easier cherry-picking.