-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Bug 1706689: asset/manifests: internal api server URL for infrastructure #1718
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
Bug 1706689: asset/manifests: internal api server URL for infrastructure #1718
Conversation
Brins in changes from openshift/api#308 ```console $ dep version dep: version : v0.5.0 build date : 2018-07-26 git hash : 224a564 go version : go1.10.3 go compiler : gc platform : linux/amd64 features : ImportDuringSolve=false $ dep ensure -update github.com/openshift/api github.com/openshift/client-go ```
@@ -326,6 +326,7 @@ func waitForInitializedCluster(ctx context.Context, config *rest.Config) error { | |||
clusterVersionContext, cancel := context.WithTimeout(ctx, timeout) | |||
defer cancel() | |||
|
|||
failing := configv1.ClusterStatusConditionType("Failing") |
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.
Is this just until the CVO moves to Degraded?
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.
no plans for CVO to move to Degraded
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're just going to translate operator Degradeds into CVO Failings forever?
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.
no plans for CVO to move to
Degraded
We're just going to translate operator Degradeds into CVO Failings forever?
forever
i can't say ;)
for now yes
We're
the installer only cares about the fact that CVO reports failing, its only a consumer. the installer shouldn't care
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.
every team was told to move. why didn't the cvo move?
/lgtm @deads2k thinks this might cause issues with in-cluster cert minting/rotating. But if it gets through CI it's fine with me, we just need to check/fix rotation before cutting a release. |
Catch up to the api change introduced in openshift/api#308 The migration is required until installer correctly sets up the infrastructure object in openshift/installer#1718
6409aec
to
259cb71
Compare
Catch up to the api change introduced in [1] PR [1] introduces breaking change for `.status.apiServerURL` therefore, this only adds the new field `.status.apiServerInternalURL` so that consumers like KAS-O and MCO can move to this new field and then installer can move the `.status.apiServerURL` to public url for Kubernetes API. [1]: openshift/api#308
PR [1] dropped the Failing condition and CVO moved to still reports Failing by using a local definiton [2]. This defines a local definition for failing condition like in CVO. [1]: openshift/api@a9fb3b1 [2]: openshift/cluster-version-operator@0b47fc9
259cb71
to
7aa6482
Compare
/lgtm with the ratchet too ;) |
[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 |
failing console...
/retest |
/retest |
Looks like https://bugzilla.redhat.com/show_bug.cgi?id=1707510 |
/retest |
I've reaped a few leaked resources, so these should go through now. /retest |
/retest |
/hold We want this, but it's not a beta-blocker. Putting the brakes on to let #1720 pass us in the merge queue. |
/retest |
/hold cancel |
PR [1] kept the `apiServerURL` field unchanged ie set to internal url for Kubernetes API so that the consumers of the field can move away from it. With KAS-O [2] change merged, we can move forward [1]: openshift#1718 [2]: openshift/cluster-kube-apiserver-operator#465
/retest |
Catch up to the api change introduced in openshift/api#308