-
Notifications
You must be signed in to change notification settings - Fork 592
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
rpk: migrate namespace to resource group #18149
Conversation
This also involves upgrading the control plane API beta v1 to v2 and dealing with the breaking changes
3c83248
to
f387042
Compare
f387042
to
3b2ba6a
Compare
new failures in https://buildkite.com/redpanda/redpanda/builds/48580#018f365b-36cd-46b3-8fe3-cda17f2faf36:
new failures in https://buildkite.com/redpanda/redpanda/builds/48580#018f365b-36d0-45dd-bf36-a4d1a4178b46:
new failures in https://buildkite.com/redpanda/redpanda/builds/48580#018f3662-1b23-4685-8250-4c4503ec8844:
new failures in https://buildkite.com/redpanda/redpanda/builds/48580#018f3662-1b2a-407e-9dcc-84fdb9df871d:
|
3b2ba6a
to
7258520
Compare
Adds back the namespace field and adds a migration mechanism for profiles that have the "namespace" value. |
7258520
to
15fd472
Compare
And bump version accordingly
15fd472
to
c36daed
Compare
This PR updates the Cloud's Namespace field to use Resource Group in the rpk codebase where we use the Public API.
This includes bumping the Cloud's Public API from v1Beta1 to v1Beta2, and bumping the
rpk.yaml
's version.The PR also renames
rpk cloud namespace
torpk cloud resource-group
, but remember that this was a hidden and undocumented command.Namespace
still works as an alias.Backports Required
Release Notes