Re: [kubernetes/kubernetes] Server-side printing continued (#60712)
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
@juanvallejo @soltysh @kubernetes/sig-cli-misc
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 7 days, the issue will be moved out of the v1.11 milestone.
sig/cli: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/feature: New functionality.
—
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.
Kubernetes Submit Queue
Kubernetes Submit Queue
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Attention
@juanvallejo @soltysh @kubernetes/sig-cli-misc
Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.
Note: If this issue is not resolved or labeled as priority/critical-urgent by Tuesday, June 5th it will be moved out of the v1.11 milestone.
Maciej Szulik
@juanvallejo we need to verify if the main bits here got in and move the remaining to 1.12
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Attention
@juanvallejo @soltysh @kubernetes/sig-cli-misc
Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.
Note: If this issue is not resolved or labeled as priority/critical-urgent by Tuesday, June 5th it will be moved out of the v1.11 milestone.
sig/cli: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/feature: New functionality.
—
Josh Berkus
So the only thing getting done on this for 1.11 is server-side-printing by default? Is that correct?
Juan Vallejo
So the only thing getting done on this for 1.11 is server-side-printing by default? Is that correct?
This as well as the second item from the list "Move the OpenAPI column rendering for CRD to the server in the CRD implementation" were completed for 1.11
Josh Berkus
OK, those are both merged, so should we change the milestone on this issue?
Juan Vallejo
@jberkus yes, I believe the remaining items can be bumped to the 1.12 milestone. Thanks
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Attention
@juanvallejo @soltysh @kubernetes/sig-cli-misc
Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.
Note: If this issue is not resolved or labeled as priority/critical-urgent by Tuesday, June 5th it will be moved out of the v1.11 milestone.
sig/cli: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/feature: New functionality.
—
Kubernetes Submit Queue
Kubernetes Submit Queue
Maciej Szulik
@jberkus updated milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process
sig/cli: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/feature: New functionality.
—
Davanum Srinivas
Looks like feature moved from 1.12 to 1.13 ( kubernetes/features#515 ) Moving this issue as well. please move it back if needed.
/milestone v1.13
Shubheksha
ping @juanvallejo, @soltysh - is this WIP for 1.13?
Juan Vallejo
@shubheksha I believe we're tracking any remaining client-side work for this feature in kubernetes/enhancements#515.
@smarterclayton Do we have any plans to work on any of the server-side items for 1.13?
Clayton Coleman
On Oct 24, 2018, at 6:07 PM, Juan Vallejo <notifi...@github.com> wrote:
@shubheksha <https://github.com/shubheksha> I believe we're tracking any
remaining client-side work for this feature in kubernetes/enhancements#515
@smarterclayton <https://github.com/smarterclayton> Do we have any plans to
work on any of the server-side items for 1.13?
—
Reply to this email directly, view it on GitHub
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p99GKLvupCKXTIW5nVwFf64RAXF1ks5uoOSPgaJpZM4SaGTn>
.
Shubheksha
Thank you for the clarification!
Can we remove the milestone from this issue?
Niko Pen
as this is an umbrella issue with various non-urgent fixes/improvements, this can be tagged for v1.14
/priority important-longterm
/milestone v1.14
Niko Pen
/remove-priority important-soon
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Niko Pen
/milestone clear
Kubernetes Prow Robot
Closed #60712.
Maciej Szulik
I'm closing this in favor of kubernetes/enhancements#515 and the work its tracking.
/close
Kubernetes Prow Robot
@soltysh: Closing this issue.
In response to this:
I'm closing this in favor of kubernetes/enhancements#515 and the work its tracking.
/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.