Dr. Stefan Schimanski
Dr. Stefan Schimanski
@deads2k is preparing a KEP for this effort.
While in general this looks good, the timing is questionable. Why don't we first get the API in place properly with the fields we want, and AFTER that do the...
`helm install` fails with that message.
yes, that sounds like the right direction, to wait for `Established`.
The best solution, other than complicated work-arounds is to fix the CRD schema in the provider. Something along these lines: ```yaml type: array x-kubernetes-list-type: map x-kubernetes-list-map-keys: ["id"] items: properties: id:...
My comments are addressed. So as far as I can judge, and under the lack of proper e2e tests, this sgtm. Let's hope there is no firework 💥🍾🤞
With https://github.com/kcp-dev/kcp/pull/3156 the problem here goes away as the external virtual workspace user is preserved.
/lgtm /approve /ok-to-test
This looks like an instance of the misunderstanding of Kube versions in the helm provider types, i.e. what I tweeted in https://twitter.com/the_sttts/status/1771257423614836820. In code, these `forProviders` fields diverged in v1alpha1...