Skip to content

Conversation

@nikhita
Copy link
Member

@nikhita nikhita commented Jan 12, 2023

One-line PR description:
We’ve received good feedback for this feature and would like to move it to beta in v1.27. Some examples of feedback:

Issue link: #2590

/assign @soltysh
cc @MadhavJivrajani

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 12, 2023
@k8s-ci-robot k8s-ci-robot requested a review from KnVerey January 12, 2023 12:45
@k8s-ci-robot k8s-ci-robot added the kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory label Jan 12, 2023
@k8s-ci-robot k8s-ci-robot requested a review from soltysh January 12, 2023 12:45
@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 12, 2023
@nikhita nikhita mentioned this pull request Jan 12, 2023
12 tasks
@nikhita nikhita force-pushed the subresource-kep-beta branch 2 times, most recently from 29703cf to 12ec0b6 Compare January 12, 2023 12:53
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 12, 2023
@nikhita nikhita force-pushed the subresource-kep-beta branch from 12ec0b6 to dba604b Compare January 12, 2023 12:57
@rikatz
Copy link
Member

rikatz commented Jan 12, 2023

User feedback here:

This feature is a must and has been a life saver for a while to me. Previously I've been using kubectl-edit_status plugin, and as soon as this feature was released on kubectl I've just migrated directly to it.

I have faced no problem so far, or inconsistency on the behavior. Just using kubectl --subresource=status has been enough for the majority of my daily tasks :)

Nice work folks!

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


#### Beta

- Add the `--subresource` flag to the apply command.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite convinced we want to support --subresource in apply command, given its general purpose of being a declarative command, which we covered in this presentation https://youtu.be/eOxy1PS5TyQ?t=780.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite convinced we want to support --subresource in apply command

It's also not straightforward to implement. Ref: #2600 (comment), #2600 (comment)

Is it ok to move this KEP to beta without adding --subresource support for apply?

Although, then I'm not sure what "beta" or "GA" for this feature would even mean 🤔

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite convinced we want to support --subresource in apply command

It's also not straightforward to implement. Ref: #2600 (comment), #2600 (comment)

Is it ok to move this KEP to beta without adding --subresource support for apply?

It's totally fine, just add a note, that due to additional complexity and the nature of kubectl apply command we've decided not to expand it with this flag.

Although, then I'm not sure what "beta" or "GA" for this feature would even mean thinking

You can promote to beta, w/o any test, which can be added during promotion, or after. For GA we need tests covering every are, ideally unit, integration (cmd) and e2e.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed feedback and updated to the new KEP template.

@nikhita nikhita force-pushed the subresource-kep-beta branch from dba604b to d0d40b5 Compare January 12, 2023 16:37
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one nit, but otherwise this lgtm


#### GA

- e2e tests are added.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests are required for GA, so you want them being added at beta stage, since that will be one of reqs for GA promotion.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

@nikhita nikhita force-pushed the subresource-kep-beta branch from d0d40b5 to a3b7f20 Compare January 12, 2023 17:28
@nikhita
Copy link
Member Author

nikhita commented Jan 12, 2023

/assign @johnbelamaric

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
from sig-cli pov

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 13, 2023
@BenTheElder
Copy link
Member

Hi @nikhita, Production Readiness Review Shadows are going to do first pass PRR reviews this cycle (recently announced here), I'll be shadowing this KEP and @johnbelamaric will be following later with a follow-up review and PRR approval.

#### Beta

- Gather feedback from users.
- e2e tests are added.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

#### Alpha

- [ ] Collect user feedback on adding support of `--subresource` for `apply`
- Add the `--subresource` flag to get, patch, edit and replace commands.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also unit tests?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added unit and integration tests.

@nikhita nikhita force-pushed the subresource-kep-beta branch from a3b7f20 to 505daaa Compare February 3, 2023 05:30
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 3, 2023
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 3, 2023
@johnbelamaric
Copy link
Member

In alpha, looks like we didn't make you set an env var in order to make the flag valid. Usually we do that now for kubectl. It is essentially a positive acknowledgement by the user that "I know I am using an alpha feature".

That's fine, no change needed now. But in the future that would be the right approach.

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johnbelamaric, nikhita, soltysh

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 7, 2023
@k8s-ci-robot k8s-ci-robot merged commit a86925e into kubernetes:master Feb 7, 2023
@k8s-ci-robot k8s-ci-robot added this to the v1.27 milestone Feb 7, 2023
@soltysh
Copy link
Contributor

soltysh commented Feb 8, 2023

In alpha, looks like we didn't make you set an env var in order to make the flag valid. Usually we do that now for kubectl. It is essentially a positive acknowledgement by the user that "I know I am using an alpha feature".

Yeah, that's my bad, I usually ensure that we have it behind an env var 😞 Sorry for that.

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. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/cli Categorizes an issue or PR as relevant to SIG CLI. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants