-
Notifications
You must be signed in to change notification settings - Fork 425
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
🐛 remove metadata.creationTimestamp when generating CRDs, RBAC, and webhooks #800
🐛 remove metadata.creationTimestamp when generating CRDs, RBAC, and webhooks #800
Conversation
…hooks Signed-off-by: Joe Lanford <[email protected]>
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86, joelanford 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 |
/cherry-pick release-0.11 |
@joelanford: #800 failed to apply on top of branch "release-0.11":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Closes #402
This issue has been open for awhile, but seemingly not that big of a deal until kustomize v5 was released with a bug that converts
null
to"null"
. And that causes manifests to fail to apply.kubernetes-sigs/kustomize#5031
We can stem the tide in controller-tools by removing
creationTimestamp: null
just before writing the generated manifests. This was always unsightly/superfluous anyways.