remove status field from generated yaml #1746
Conversation
Signed-off-by: shubhindia <shubhindia123@gmail.com>
Signed-off-by: shubhindia <shubhindia123@gmail.com>
|
@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 <shubhindia123@gmail.com>
ffe7691 to
204dff4
Compare
Signed-off-by: shubhindia <shubhindia123@gmail.com>
|
/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 DetailsNeeds 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 DetailsNeeds 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