Ahmet Alp Balkan

Indeed, after creating the issue I've realized HTTP response code must be 200 regardless of the admission response (which contains the status code the apiserver would return in its response...

/remove-kind bug /kind feature

Sorry I forgot to reply. > A namespaced object (NodeFeature) cannot be "owned" (as by ownerReference) by a cluster-scoped object (Node). Are you sure? I think it's the other way...

It seems newer versions of NFD now parent NodeFeature resource to `DaemonSet`. I think this is still a bad idea. We might remove the DaemonSet accidentally, or another reason like...

Those were secondary issues I mentioned. The main issue is Kruise mutating its own CRD which still does not make sense. It sounds like a hacky solution to a problem...

I understand that the Kruise operator has a self-signed certificate configuration mode and where the controller updates the CRDs, because CRDs have a conversion webhook section that has a `clientConfig.caBundle`...

I'm afraid this is by design in kubectl and I agree with the design. Context name should not be the same across multiple files.

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- Thanks for submitting your kubectl plugin to Krew! One of the krew-index maintainers will review it soon....

/lgtm /approve Thanks! Also, please consider setting up [Krew release automation](https://krew.sigs.k8s.io/docs/developer-guide/release/automating-updates/) which helps you skip manually making updates to your Krew manifests on each new version and send a pull...

Krew only allows publishing the latest version.