-
Notifications
You must be signed in to change notification settings - Fork 768
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 status field from generated yaml #1746
remove status field from generated yaml #1746
Conversation
Signed-off-by: shubhindia <[email protected]>
Signed-off-by: shubhindia <[email protected]>
@shubhindia It seems that there are some status'es that are not deleted yet in the test files. |
@AhmedGrati pushed a commit to remove those. |
5ebc4b1
to
ffe7691
Compare
Signed-off-by: shubhindia <[email protected]>
ffe7691
to
204dff4
Compare
Signed-off-by: shubhindia <[email protected]>
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cdrage, shubhindia 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 |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cdrage, shubhindia 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 |
/lgtm |
/kind feature
What type of PR is this?
Whenever the k8s yamls are generated, since status field is part of APIs, it is being added in the generated yamls, which is fine but should not be there since the objects are not applied yet.
What this PR does / why we need it:
This just adds a simple hack to remove the status field from generated yamls
Which issue(s) this PR fixes:
Fixes #975