Exception Request: "kubectl commands in headers" for release 1.22

[Sean Sullivan]

• Enhancement name: kubectl commands in headers
• Enhancement status: beta
• SIG: CLI
• k/enhancements repo issue #: 859
• PR #’s: Update kubectl headers KEP to beta #2720 (merged)
• Additional time needed (in days): 1 day
• Reason this enhancement is critical for this milestone: kubectl headers are necessary for telemetry on kubectl usage. Delaying these headers delays the ability to gather kubectl usage information.
• Risks from adding code late: None
• Risks from cutting enhancement: kubectl usage telemetry delayed

Hello,

During development and review of the aforementioned KEP, I overlooked the "Graduation Criteria" section. I am requesting a one day exception to add this graduation criteria to the KEP. In all other respects the KEP is complete (for beta), and the KEP has been substantively reviewed by a PRR reviewer and a SIG TL.

Thank you ,

Sean Sullivan

SIG CLI co-chair

[Savitha Raghunathan]

Hi Sean,

Thanks for creating this exception request.

Since the risk is minimal to none and the KEP only needs a minor change, we are APPROVING this request. Please make sure to merge the updated KEP by May 18th. If you have any questions, please feel free to reach out to us in the #sig-release slack channel.

Have a great day!

Regards,

Savitha,

1.22 Release Team Lead

On Mon, May 17, 2021 at 11:47 AM Maciej Szulik <masz...@redhat.com> wrote:

+1

On Sat, May 15, 2021 at 12:04 AM Phillip Wittrock
<phil.w...@gmail.com> wrote:
>
>
> +1
>
> On Friday, May 14, 2021 at 1:12:34 PM UTC-7 eddi...@gmail.com wrote:
>>
>> +1
>>
>> Eddie Zaneski
>>
>> On Fri, May 14, 2021, 1:28 PM Jeremy Rickard <jeremy.r...@gmail.com> wrote:
>>>
>>> Also +1
>>>
>>> On Fri, May 14, 2021 at 1:12 PM 'John Belamaric' via kubernetes-sig-release <kubernetes-...@googlegroups.com> wrote:
>>>>
>>>> +1

>>>> --
>>>> You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/6e233e8c-ddb7-4e1c-9198-33273b40d28dn%40googlegroups.com.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
>>>
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAEHNk2xFtMJdabTNx7wK6PndGrYbVGwcWRhKBRLVyNse42t9Ug%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/5585c5ed-635f-4432-9d58-46a643f2550cn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CALFFA0NcpD68crxamk06o1VQ89WQmpnGgUwo%2BNhT%3DL8y8jpNFg%40mail.gmail.com.