Skip to content

known-issues.md

Latest commit

 

History

History
87 lines (56 loc) · 3.31 KB

known-issues.md

File metadata and controls

87 lines (56 loc) · 3.31 KB

Known Issues

This page outlines known issues with Managed OpenShift on Azure (OSA), including workarounds if known.

Providers and features must be registered manually

Currently, the Microsoft.ContainerService openshiftmanagedcluster feature, Microsoft.Solutions and Microsoft.Network providers must be registered to your subscription manually before deploying your first OSA cluster.

  • Run a Cloud Shell (Bash) session from the Azure portal.

  • If you have access to multiple subscriptions, specify the relevant subscription ID.

az account set --subscription <SUBSCRIPTION ID>
  • Register the Microsoft.ContainerService openshiftmanagedcluster feature.
az feature register --namespace Microsoft.ContainerService -n openshiftmanagedcluster
  • Register the Microsoft.Solutions provider.
az provider register -n Microsoft.Solutions --wait
  • Register the Microsoft.Network provider.
az provider register -n Microsoft.Network --wait
  • Refresh the registration of the Microsoft.ContainerService resource provider.
az provider register -n Microsoft.ContainerService --wait

May not be possible to retry creation of a failed cluster

Currently, in many circumstances, if creation of a cluster using the az CLI fails, retrying creation will always fail. In this case, use az openshift delete to delete the failed cluster and attempt to create an entirely new cluster.

OpenShift server certificate is untrusted

Note that currently the OpenShift console certificate is untrusted, therefore when navigating to the console, you will need to manually accept the untrusted certificate in your browser.

OpenShift Managed Cluster resource is hidden by default

Currently, the Microsoft.ContainerService/openShiftManagedClusters resource created by the az CLI is hidden in the Azure portal. In the relevant Resource group view, check Show hidden types to view the resource.

Hidden Type

Only available cluster update is scale up / scale down

Currently, no modifications are permitted to the Microsoft.ContainerService/openShiftManagedClusters resource after creation, except for scaling up or down the number of compute nodes. Currently the maximum number of compute nodes is limited to 20.

Limited VM sizes

Managed OpenShift on Azure only permits certain VM sizes to be used. You can find the permitted sizes here.

Azure Active Directory restriction

Using the CLI to create a new OpenShift cluster by not passing any AAD Client values will try to automatically create one for you. The creation might fail with the following message :

Directory permission is needed for the current user to register the application. For how to configure, please refer 'https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal'. Original error: Insufficient privileges to complete the operation.

You need to ask your administrator to create one AAD Client first using this documentation.

Create an OpenShift cluster using a custom AAD Client:

az openshift create -g MyResourceGroup -n MyOpenShiftCluster --fqdn ${FQDN} --aad-client-app-id ${APP_ID} --aad-client-app-secret ${APP_SECRET} --aad-tenant-id ${TENANT_ID}