-
Notifications
You must be signed in to change notification settings - Fork 601
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.
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
Broker class based defaults #5992
Comments
/assign |
In this configuration, the <broker_class> is the unknown key in JSON, and in the original code it use parseEntry function to transfer YAML to JSON, if we want to unmarshal the known key in the whole YAML, we need to modify the NewDefaultsConfigFromMap, it will make our code became more complex, so I suggest we use the following Configuration:
@pierDipi what do you think? |
/assign |
https://docs.google.com/document/d/1RKij-DYPmcbCTHF26hkXdrtWHqrksA-Fo5qYLRP7xVA/edit |
Problem
Operators can set defaults for brokers at the cluster or namespace level in the
config-br-defaults
ConfigMap.When there are multiple classes in the same cluster, it's not possible to set
a default for
broker.spec
fields based on the configured broker class.A convenient configuration like the following would be perfect:
Persona:
Which persona is this feature for?
Operator
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
2
Additional context (optional)
Add any other context about the feature request here.
/area brokers
/priority important-longterm
/kind feature-request
The text was updated successfully, but these errors were encountered: