Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

How far do we go with the templating of the resources from the CRO definition #8

Open
Lawouach opened this issue Mar 19, 2020 · 0 comments
Open

How far do we go with the templating of the resources from the CRO definition #8

Lawouach opened this issue Mar 19, 2020 · 0 comments
Labels
question Further information is requested

Comments

@Lawouach
Copy link
Contributor

The usual goal of a CRO definition is to remain simple and hide all the complexity in the CRD. But we have so many combinations (due to passing all the Kubernetes information) that we end up with an equally complex definition for the user.

Should we instead keep the basic options lean and simple and promote overriding the all pod otherwise?

Just thinking out loud :)

cc @dmartin35
@Lawouach Lawouach added the question Further information is requested label Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lawouach