Skip to content

Commit 714e526

Browse files
authored
this applies not only to long running but also to newly created clusters
“… Due to this limitation, if you are planning to use long running clusters (e.g. more than 60 days), we recommend to use the same managed identity for all of the above scenarios …” From our experience we have noticed in the presented scenarios that the issue occurs not only with long running cluster but also with newly created ones. Therefore, the wording is misleading. So, we propose to remove the highlighted bit. As we think that will bring more clarity to the documentation.
1 parent f22d045 commit 714e526

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/hdinsight/hdinsight-managed-identities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Managed identities are used in Azure HDInsight in multiple scenarios. See the re
4040
* [Enterprise Security Package](domain-joined/apache-domain-joined-configure-using-azure-adds.md#create-and-authorize-a-managed-identity)
4141
* [Customer-managed key disk encryption](disk-encryption.md)
4242

43-
HDInsight will automatically renew the certificates for the managed identities you use for these scenarios. However, there is a limitation when multiple different managed identities are used for long running clusters, the certificate renewal may not work as expected for all of the managed identities. Due to this limitation, if you are planning to use long running clusters (e.g. more than 60 days), we recommend to use the same managed identity for all of the above scenarios.
43+
HDInsight will automatically renew the certificates for the managed identities you use for these scenarios. However, there is a limitation when multiple different managed identities are used for long running clusters, the certificate renewal may not work as expected for all of the managed identities. Due to this limitation, we recommend to use the same managed identity for all of the above scenarios.
4444

4545
If you have already created a long running cluster with multiple different managed identities and are running into one of these issues:
4646
* In ESP clusters, cluster services starts failing or scale up and other operations start failing with authentications errors.

0 commit comments

Comments
 (0)