-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
asset/manifests: update status of Infrastructure #1155
asset/manifests: update status of Infrastructure #1155
Conversation
/lgtm |
But the telemetry folks just fixed a config issue, so... /retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
both with panics :p. Just in case they're also flakes... /retest |
The |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
Needs a rebase. |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
e86ff6c
to
a341c2a
Compare
rebase around #1132 |
ping @wking |
This updates the `Infrastructure.config.openshift.io` object to catch up with [1]. Machine Config Operator uses the `APIServerURL` to point the kubelet on machines to apiserver, and `EtcdDiscoveryDomain` to setup the etcd members to bootstrap the etcd cluster using dns discovery [2]. This is required as Machine Config Operator currently uses the `cluster-config-v1` to creates these values and as `cluster-config-v1` is getting deprecated [3], Machine Config Operator will move to using the status of `Infrastructure.config.openshift.io` for sourcing that information. [1]: openshift/api#189 [2]: https://github.com/etcd-io/etcd/blob/583763261f1c843e07c1bf7fea5fb4cfb684fe87/Documentation/op-guide/clustering.md#dns-discovery [3]: openshift#680
a341c2a
to
49719a1
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, wking 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
Since [1], the `Infrastructure.config.openshift.io` global config object contains the kube apiserver's url and the domain that needs to be used by etcd to do bootstrapping using dns discovery. The installer creates and sets the appropiate value since [2]. Therefore there is no longer a requirement for cluster_name and base_domain to create these values in template controller. [1]: openshift/api#189 [2]: openshift/installer#1155
This updates the
Infrastructure.config.openshift.io
object to catch up with 1.Machine Config Operator uses the
APIServerURL
to point the kubelet on machines to apiserver, andEtcdDiscoveryDomain
to setup the etcdmembers to bootstrap the etcd cluster using dns discovery 2.
This is required as Machine Config Operator currently uses the
cluster-config-v1
to creates these values and ascluster-config-v1
is getting deprecated 3, Machine Config Operator will move tousing the status of
Infrastructure.config.openshift.io
for sourcing that information.