David Eads
David Eads
I think we should refactor the API to reflect the lessons learned from our first discovery document. Details like separation of GVR from GVK and the handling of subresources should...
> I talked with the team, the intent here was actually not to change the API at all, This came up in the KEP review here: https://github.com/kubernetes/enhancements/pull/3364#discussion_r897282810 with a specific...
> Once a new API is released, it will be pinned. Creating a new API with the known flaws of the previous API is a mistake. The consuming code has...
> This was discussed a couple of weeks ago on the sig-cli call. I have some investigative work to do and some questions to answer for the group before I...
I'm still not clear on why it's a good thing that our documentation, existing blogs, and existing scripts will not be portable to heterogeneous clusters. Can we update the description...
do you have PR open demonstrating how this will be used? I think that will help reviewers understand the purpose better and how the failures will be manifested to developers...
Can you open a k/k PR with the change you plan to merge to use this env var?
/milestone v1.27 /label lead-opted-in /stage stable
is this still a WIP?
This file is generated by https://github.com/openshift/cluster-debug-tools Glad to see details coming here.