-
Notifications
You must be signed in to change notification settings - Fork 189
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
USHIFT-607: Introduce a new config format for microshift config #1030
Conversation
@benluddy @dgrisonnet @fzdarsky Please take a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've had a few conversations about these changes in different places, so it would be useful to capture the reasoning in an enhancement. We could continue to use this PR to hammer out the final structure, and then document it retroactively.
7209081
to
230d38b
Compare
230d38b
to
bb2b1da
Compare
1d6f641
to
090f2c2
Compare
090f2c2
to
73b8399
Compare
I addressed the outstanding comments, PTAL @fzdarsky @dhellmann. |
/retest |
/approve The new format seems reasonable. |
/unapprove |
I see some inconsistency with baseDomain/domain/clusterDomain I would suggest we change that parameter to clusterDomain, and we update the description. So this would fully align with the name used in the openshift DNS operator: https://github.com/openshift/cluster-dns-operator/blob/master/pkg/operator/controller/controller_dns_configmap.go#L80 |
For me it would work to merge and iterate. |
@mangelajo I renamed the option to |
The test/config.yaml needs an update, I guess it's simply not used yet. We can follow up on that as we explained /approve |
Separate component-specific config and microshift-specific config into 2 sections within top-level config. The components config is modelled after OpenShift config v1 API while microshift config contains fields that are specific to microshift usage. Signed-off-by: Vu Dinh <vudinh@outlook.com> Co-authored-by: Damien Grisonnet <dgrisonn@redhat.com>
I updated test/config.yaml. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu, mangelajo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
@dinhxuanvu: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/hold cancel |
Separate component-specific config and microshift-specific config into 2 sections within top-level config. The components config is modelled after OpenShift config v1 API while microshift config contains fields that are specific to microshift usage.
Signed-off-by: Vu Dinh vudinh@outlook.com
Which issue(s) this PR addresses:
Closes #