Re: [kubernetes/features] kubectl get and describe should work well with extensions (#515)

[Ihor Dvoretskyi]

@smarterclayton @kubernetes/sig-cli-feature-requests @kubernetes/sig-api-machinery-feature-requests still on track for 1.10?

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Clayton Coleman]

We're trying to close the loop on the 1.10 plan

[Ihor Dvoretskyi]

@smarterclayton any progress?

[Clayton Coleman]

Yes, we are planning to bring this to beta in 1.10. Work is being tracked in kubernetes/kubernetes#58536

[Jennifer Rondeau]

@smarterclayton sorry, I thought I had pinged you about this earlier. If this feature needs docs, can you please get a PR in in the next day or so? We need to merge all docs PRs by this Friday (March 9). If not, can you please indicate on the feature tracking spreadsheet? Thanks!

[Clayton Coleman]

@juanvallejo can you add a doc?

[Juan Vallejo]

@smarterclayton sure, will add doc

[Stephen Augustus]

@smarterclayton
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[Clayton Coleman]

@juanvallejo can you add details about the 1.11 planned things? I think we should try to get custom CRD columns on the server side in 1.11 with a minimal alpha api. I can bump the stable target to 1.12

[Maciej Szulik]

The current tracking issue can be found in kubernetes/kubernetes#60712.
+1 for bumping this to stable in 1.12.

[Stephen Augustus]

Thanks for the update!

[Misty Stanley-Jones]

@justaugustus Does this need to be removed from the spreadsheet?

[Stephen Augustus]

@mistyhacks just fixed it!

[Stephen Augustus]

@soltysh @smarterclayton @juanvallejo @kubernetes/sig-api-machinery-feature-requests @kubernetes/sig-cli-feature-requests --

This feature was removed from the previous milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description

• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

/cc @justaugustus @kacole2 @robertsandoval @rajendar38

[Stephen Augustus]

@soltysh @smarterclayton @juanvallejo --
Feature Freeze is today. Are we planning on graduating this feature in Kubernetes 1.12?
If so, can you make sure everything is up-to-date, so I can include it on the 1.12 Feature tracking spreadsheet?

[Maciej Szulik]

@justaugustus I've updated the description, and moved the target stable from 1.12 to 1.13. We need to stabilize current API a bit more. And there are still some bits and nits that needs fixing. So that's what we'll focus on in 1.12.

[Stephen Augustus]

Sounds good. Thanks for the update, @soltysh!

[Stephen Augustus]

/remove-stage beta
/stage stable

[Kendrick Coleman]

Hi @soltysh @smarterclayton
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:
Docs (open placeholder PRs): 11/8
Code Slush: 11/9
Code Freeze Begins: 11/15
Docs Complete and Reviewed: 11/27

Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet

Thanks!

[Aish Sundar]

@soltysh what work if left in k/k for this feature to go to stable in 1.13? Is there a list of pending PRs (code, tests and docs) that we can track on our end? how confident are you in stabilizing the API in the short 1.13 timeframe ?

[Guinevere Saenger]

Hi @soltysh There has been no communication on the status of this enhancement and I could not find any linked pull requests. Are we confident this is going to make the v1.13 milestone? Enhancement freeze is tomorrow COB. If there is no communication or update on the PR, this is going to be pulled from the milestone as it doesn't fit with our "stability" theme. If there is no communication after COB tomorrow, an exception will be required to add it back to the milestone. Please let me or @kacole2 know where we stand. Thanks!

[Kendrick Coleman]

/milestone clear

[Aish Sundar]

@soltysh this enhancement has been moved out of 1.13 due to lack of clarity on whats pending for this to land . We are officially in Enhancement freeze now. Should you need this added back in it will require filing an exception.

[Maciej Szulik]

@AishSundar sorry for getting to it that late, I'm fine moving it further. We're still working on other related stuff, so this will not go into stable in 1.13. We need 100% confidence before we do so, that's why I removed any version from stable stage in the original description.

[Aish Sundar]

Ack that and thanks @soltysh

[Stephen Augustus]

(Some automation I'm testing accidentally sent out a comment, which I've deleted to not make things confusing. Sorry!)

[Claire Laurence]

@smarterclayton Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP

[Kendrick Coleman]

Hello @smarterclayton, I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. KEP needs to be merged before promotion as well.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[Clayton Coleman]

Yes, the API for this feature is targeted for stable API in 1.15.

KEP in implementable: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190322-server-side-get-to-ga.md

[Clayton Coleman]

/milestone 1.15

[Kubernetes Prow Robot]

@smarterclayton: You must be a member of the kubernetes/kubernetes-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone 1.15

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.

[Kendrick Coleman]

/milestone v1.15

[Barnabas Makonda]

Hey, @soltysh @smarterclayton @juanvallejo 👋 I'm the v1.15 docs Lead.
Does this enhancement require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions

[Clayton Coleman]

It does not outside of api documentation. We probably want to review the
topic though.

On May 10, 2019, at 2:59 AM, Barnabas Makonda <notifi...@github.com>
wrote:

Hey, @soltysh <https://github.com/soltysh> @smarterclayton
<https://github.com/smarterclayton> @juanvallejo
<https://github.com/juanvallejo> 👋 I'm the v1.15 docs Lead.

Does this enhancement require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch
dev-1.15) due by Thursday, May 30th. It would be great if it's the start of
the full documentation, but even a placeholder PR is acceptable. Let me
know if you have any questions

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub

<https://github.com/kubernetes/enhancements/issues/515#issuecomment-491179385>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAI37J3XVUT5E7QM2QH5QZDPUUMMPANCNFSM4EEZMI2Q>
.

[Barnabas Makonda]

@smarterclayton Noted. so this means it won't require any PR submitted to k/website

[Kendrick Coleman]

Hi @smarterclayton . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

The one I currently see in this issue is #76789. Let me know if there are missing ones.

If you know this will slip, please reply back and let us know. Thanks!

[Kendrick Coleman]

Hi @smarterclayton @soltysh , today is code freeze for the 1.15 release cycle. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[Clayton Coleman]

And was marked LGTM

On May 30, 2019, at 10:06 AM, Kendrick Coleman <notifi...@github.com>
wrote:

Hi @smarterclayton <https://github.com/smarterclayton> @soltysh
<https://github.com/soltysh> , today is code freeze for the 1.15 release

cycle. I do not see a reply for any k/k PRs to track for this merge. It's
now being marked as At Risk in the 1.15 Enhancement Tracking Sheet

<https://docs.google.com/spreadsheets/d/1Vc949C4iC2f8GTmjfJkX04VUNcbimhg8ujp1bUAjGK4/edit?ts=5cb282ad#gid=0>.

If there is no response, or you respond with PRs to track and they are not
merged by EOD PST, this will be dropped from the 1.15 Milestone. After this
point, only release-blocking issues and PRs will be allowed in the
milestone with an exception.

—

You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub

<https://github.com/kubernetes/enhancements/issues/515?email_source=notifications&email_token=AAI37JYG26Y34S323D6FKM3PX7NPVA5CNFSM4EEZMI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWSNLDQ#issuecomment-497341838>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAI37J7UEYJO2Q5IHPADS3DPX7NPVANCNFSM4EEZMI2Q>

[Clayton Coleman]

The only PR for 1.15 is

https://github.com/kubernetes/kubernetes/pull/77817#issuecomment-497352136

And is still on track to merge today.

[Kendrick Coleman]

This has graduated to stable and been implemented. Time to close

/milestone clear
/close

[Kubernetes Prow Robot]

Closed #515.

[Kubernetes Prow Robot]

@kacole2: Closing this issue.

In response to this:

This has graduated to stable and been implemented. Time to close

/milestone clear
/close

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.

—

[Maciej Szulik]

The describe part of this enhancement isn't implemented, yet.

/re-open

—
You are receiving this because you are on a team that was mentioned.

Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

[Paco Xu]

/reopen

[Kubernetes Prow Robot]

@pacoxu: Reopened this issue.

In response to this:

/reopen

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.

—

[Kubernetes Prow Robot]

Reopened #515.

[Kubernetes Triage Robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Kubernetes Triage Robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten

• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

—

Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

You are receiving this because you are on a team that was mentioned.Message ID: <kubernetes/enhancements/issues/515/996609321@github.com>

[Kubernetes Triage Robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen

• Mark this issue or PR as fresh with /remove-lifecycle rotten

• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

You are receiving this because you are on a team that was mentioned.Message ID: <kubernetes/enhancements/issues/515/1013850281@github.com>

[Kubernetes Prow Robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

—

Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

You are receiving this because you are on a team that was mentioned.Message ID: <kubernetes/enhancements/issues/515/1013850313@github.com>

[Kubernetes Prow Robot]

Closed #515.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

You are receiving this because you are on a team that was mentioned.Message ID: <kubernetes/enhancements/issue/515/issue_event/5900127939@github.com>