-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[ACS] Remove private cluster and 2019-10-27-preview API #13618
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
Conversation
This reverts commit cd405fa.
…10-27-preview API version (Azure#12240)" This reverts commit 32e5102.
|
ACS |
|
Parameter name should not contain "id" |
| short-summary: The Object ID of an Azure Active Directory Group that memberships will get synced into the OpenShift group "osa-customer-admins". If not specified, no cluster admin access will be granted. | ||
| - name: --workspace-id | ||
| type: string | ||
| short-summary: The resource id of an existing Log Analytics Workspace to use for storing monitoring data. |
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.
Does it support name?
This question also applies to other parameters that only support id.
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.
Hi @qwordy this is a revert to the code that was there before. We had a numerous discussions about this name in the past. Also we are sunsetting the ARO v3 service and do not want to introduce any more changes.
arrownj
left a comment
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.
LGTM
Description
This PR reverts OSA support for
2019-10-17-previewAPI version and private clusters. The reason is that in order to use these features the customer's subscription either has to be whitelisted, or feature gate to be removed. Since we have GA'ed ARO v4, we are encouraging customers to use private clusters in v4 rather than v3, hence reverting this change which was broke the client for some customers.Azure/OpenShift#183
Testing Guide
create an OpenShift cluster
az openshift create -g <group_name> -n <resource_name> --location eastus2try show or list command:
az openshift listaz openshift show -g <group_name> -n <resource_name>They should execute without error and display the cluster info.
History Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.