OCPCLOUD-2011: Update implementation history of External platform type EP

[adriengentil]

This PR updates the implementation history of the External platform with
the upcoming change in openshift/api.

[openshift-ci-robot]

@adriengentil: This pull request references OCPCLOUD-2011 which is a valid jira issue.

Details

In response to this:

This PR updates the implementation history of the External platform with
the upcoming change in openshift/api.

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.

[adriengentil]

/hold

[bparees]

/approve

thanks for keeping the history updated

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees

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:

• OWNERS [bparees]

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

[elmiko]

/lgtm

[elmiko]

@JoelSpeed and i discussed this today and i think we've got more questions about the best place to put this field. essentially we have some thoughts about if this should be in the spec or status, and what the most appropriate usage is for users.

/lgtm cancel

[elmiko]

these updates look nice to me, i'm not sure we want to add any language about how the status will be reconciled. perhaps we should add those details as followup when we get closer to deciding how it will work.

[elmiko]

/lgtm

[adriengentil]

these updates look nice to me, i'm not sure we want to add any language about how the status will be reconciled. perhaps we should add those details as followup when we get closer to deciding how it will work.

yes, this is what I was thinking, to update this enhancement once we have a clearer picture on how the reconciliation will work.

[adriengentil]

As agreed with @elmiko and @JoelSpeed, I updated the document to control the Cloud Controller Manager state from the status as this setting will be set at installation time and we won't allow it to be changed afterwards.

[openshift-bot]

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle stale.
Stale proposals rot after an additional 7d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle stale

[adriengentil]

/remove-lifecycle stale

[JoelSpeed]

@adriengentil I think a few things changed in the final few days before we merged the API, is this still up to date?

[adriengentil]

In my last commit I updated a CEL and mentioned that this new API is behind TechPreviewNoUpgrade, so think we should be good.

[elmiko]

thanks for the updates @adriengentil

/lgtm

[adriengentil]

/unhold

[openshift-ci]

@adriengentil: all tests passed!

Full PR test history. Your PR dashboard.

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.