Support for a k8s `ConfigMap` containing the stack configuration

[ringods]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The current Stack CRD only allows for a single level set of stack configuration items. If a user wants structured config, it is currently not possible for them to get this info injected.

Please allow for the stack config to be generated into a ConfigMap resource and attached to the Stack custom resource.

Affected area/feature

Stack Configuration.

[ljtfreitas]

Ideally the Stack object would be able to receive structured configs directly from the spec, not just by ConfigMaps. I mean, ConfigMaps are a good option and should be supported also, but it's harder to re-sync the Stack when the ConfigMap changes.

I've implemented this in the v1 version and sent a PR, it was rejected 🙄 , and the operator v2 has the same issue: #575

[EronWright]

@ljtfreitas all true and we're sorry that the PR was rejected. I believe the issue was about compatibility with Kubernetes CRD schema and the so-called "structural schema" requirements related to server-side apply.

The requirement is clear, and I would agree that it should be possible via the Stack object, since otherwise one must manually poke the stack to effect an update. Thanks for your patience!