Borja Clemente

Hi @timebertt, thanks for the quick response! Currently I am importing gardener `1.46.2` here: https://github.com/kyma-project/hydroform/tree/main/provision. This is causing issues when transitively importing things like helm 2.16, yaml.v2, a very outdated...

Hi @timebertt, @rfranzke, thanks for the response and looking into it again. I am very interested in learning more about the challenges this poses and why this sync-out is necessary....

Hi @timebertt, thanks for the feedback. If I understand correctly, the issue is the ambiguous import. I also faced this and the problem was not solvable for some time in...

I also encountered this issue in `v1.11.1`. But after investigating, I see that the issue was fixed [here](https://github.com/briandowns/spinner/commit/274d17742d9e79ebca441490246c31e47b64ba67) in July. But unfortunately this fix did not make it into `v1.11.1`....

Ideally we should do it if we want to support k3d on other machines. Otherwise we need to set the expectation clear that k3d only works locally.

Hi @Tomasz-Smelcerz-SAP, @jakobmoellersap, I clarified the AC and edited the title and description to reflect the dual validation needed to have safe module development.

Hi @Tomasz-Smelcerz-SAP, for the CRD itself we will have to define certain rules manually and check for them programatically. Best is to align with the module and lifecycle managers to...

Hi @Tomasz-Smelcerz-SAP, as you guessed, the CRD is on the operator and there should be only one which matches the operator name. Can you confirm the premise @jakobmoellersap?

Hi @tobiscr, that is a very good point. With the new deploy I do not think this is relevant anymore. Closing the issue.

Hi @tobiscr, we are not using CNUDIE but OCM (its successor). I updated the description to make it clear. The task is still relevant.