Completion of CRDs

[evolvedlight]

Hi,

I tried this out and it works nicely for the basics, however it's not very complete and so doesn't work, for example for adding new environment variables into a deployment config.

I guess these were handcoded for just your needs? Any idea if it'd be possible to generate full CRDs, or I should just try to extend by hand?

Thanks,
Steve

[BorntraegerMarc]

@evolvedlight you ever managed to use this?

[evolvedlight]

Hi @BorntraegerMarc ,
No, we're probably going to go in a different direction and not use this. We're not sure what to use instead yet though.

[Intey]

Hello, Thanks for this crds! With that, I found hope that it's really can be kustomizable withoud duplications, and with easy changes.

But we get same issues.

For example, we declare in kustomize base DeploymentConfig with predefined env vars: kafka broker secret, and so on.
in overlays, if it's all works correctly, i need to recrete secret and reuse env definitions from base layers.
So, it's like "API" of parent resource (like in OOP with objects and virtual methods or interfaces).

I try to use this with DeploymentConfig, and in overlay i add some new secrets (as mount volumes), change replicas count and in builded result get DeploymentConfig with volumes, changed replicas, but withoud predefined envs.

As workaround, we can use simple json-patches, or redeclare all needed stuff in overlay, but in last case we didn't use base.