Skip to content

Conversation

@abhinavdahiya
Copy link
Contributor

@abhinavdahiya abhinavdahiya commented Jul 2, 2019

the API were added in openshift/api#300 and openshift/api#359

Platform specific status fields allow installer a way to provide details about the platform to the operators.

/cc @jhixson74 @patrickdillon
^^-- for the changes
/cc@coreydaley @ironcladlou
^^-- for openshift-ingress and openshift-image-registry operator API for GCP.

Closes #1725

abhinavdahiya and others added 3 commits July 1, 2019 16:50
Based on openshift/api#359 that adds the platform specific status for Azure and GCP. This sets the
* resource group name for the Azure platform
  operators that need the location, should use the location of the resource group.
* add the project ID and region for the GCP platform
  this allows operators to create resources for the cluster correctly.
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 2, 2019
@openshift-ci-robot
Copy link
Contributor

@abhinavdahiya: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 66ce047 link /test e2e-aws-scaleup-rhel7

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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.

@ironcladlou
Copy link
Contributor

Awesome, thanks!

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, ironcladlou

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit c6efecd into openshift:master Jul 2, 2019
@ironcladlou
Copy link
Contributor

@abhinavdahiya Well, I didn't realize I was an approver here when I tagged this and now it merged without wide review — sorry.

@dmage
Copy link

dmage commented Jul 2, 2019

/cc @coreydaley
(in the description there is no space before "@", so I guess GitHub didn't send a notification)

default:
config.Status.PlatformStatus.Type = configv1.NonePlatformType
}
config.Status.Platform = config.Status.PlatformStatus.Type
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems pointless to have this assignment and the same assignment in the case statements. The assignment in the case statements will be undone by this. Which one we keep depends on whether they are always equal or if there can be skew depending on the platform.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, agree.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

opened #1934 to fix it.

abhinavdahiya added a commit to abhinavdahiya/installer that referenced this pull request Jul 2, 2019
…ormType

.status.platformType was being set twice by changes in openshift#1930

This move the assignment to single location after the switch.
APIServerURL: getAPIServerURL(installConfig.Config),
APIServerInternalURL: getInternalAPIServerURL(installConfig.Config),
EtcdDiscoveryDomain: getEtcdDiscoveryDomain(installConfig.Config),
PlatformStatus: &configv1.PlatformStatus{},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The MCO was reading Platform- is it just enough to switch to PlatformStatus? cc @sgreene570

Copy link
Contributor Author

@abhinavdahiya abhinavdahiya Jul 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sgreene570 @runcom
This is only set in new 4.2 clusters.
4.1 clusters do not have .status.platformStatus set.

A migration will be required to provide this field to all 4.1 clusters.. or operators can use fields if set and fall back to old field....
Still seeing if a migration will be required as only 4.2 platforms require .status.platformStatus to be set.

Copy link
Member

@runcom runcom Jul 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know, so it's ok to switch to the new platformStatus in 4.2 and live with that as you're doing in this PR?

Still seeing if a migration will be required as only 4.2 platforms require .status.platformStatus to be set.

👍 awesome, that's what I was looking for as well for MCO specifically, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants