-
Notifications
You must be signed in to change notification settings - Fork 169
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
Use latest "in-progress" ARO API for local/E2E cluster creation #3622
Use latest "in-progress" ARO API for local/E2E cluster creation #3622
Conversation
fd8b39b
to
f4cce74
Compare
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run ci,e2e |
Please rebase pull request. |
f4cce74
to
abcb2eb
Compare
abcb2eb
to
c05f300
Compare
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
Please rebase pull request. |
c05f300
to
510b3ee
Compare
/azp run ci,e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
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.
2 questions but nothing blocking this
e153071
to
510b3ee
Compare
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.
Seems elegant enough, nice!
Which issue this PR addresses:
Fixes ARO-8003
What this PR does / why we need it:
This PR updates
pkg/util/cluster/cluster.go
to use the latest in-progress API (v20240812preview) when environment variableRP_MODE
is set todevelopment
, and the latest released API that's routable in ARM otherwise (v20231122).This allows local development cluster creation, as well as E2E runs against a locally running RP (e.g. the E2E PR pipeline) to test cluster creation/deletion against our in-progress API, while still ensuring that we utilize the latest ARM-routable API during production contexts (e.g. prod E2E).
The implementation here is generic, and could be expanded in the future to allow us to arbitrarily select which ARO API version we would like to use.
Test plan for issue:
Is there any documentation that needs to be updated for this PR?
How do you know this will function as expected in production?
This change is not utilized by any production services, and is only utilized in development and E2E flows.