wangyang0918 commented on pull request #17819:
URL: https://github.com/apache/flink/pull/17819#issuecomment-1011771453


   @alpreu  Currently, the 45 characters pre-check could only work for native 
K8s HA/non-HA mode. But for standalone cluster with K8s HA enabled, we do not 
have the pre-check and will cause the exception in 
[FLINK-15816](https://issues.apache.org/jira/browse/FLINK-15816?focusedCommentId=17417129&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17417129)
 if the cluster-id is longer than 63 characters.
   
   I have verified that cluster id with 45 characters works well.
   ```
   wangyang-pc:scripts danrtsey.wy$ kubectl get pods
   NAME                                                             READY   
STATUS    RESTARTS   AGE
   xxxxx1234567890123456789012345678901234567890-77895db8dd-mrcnm   1/1     
Running   0          22m
   xxxxx1234567890123456789012345678901234567890-taskmanager-1-1    1/1     
Running   0          21m
   wangyang-pc:scripts danrtsey.wy$ kubectl get cm
   NAME                                                                         
                      DATA   AGE
   flink-config-xxxxx1234567890123456789012345678901234567890                   
                      3      22m
   kube-root-ca.crt                                                             
                      1      22d
   
xxxxx1234567890123456789012345678901234567890-00000000000000000000000000000000-jobmanager-leader
   4      21m
   xxxxx1234567890123456789012345678901234567890-dispatcher-leader              
                      4      21m
   xxxxx1234567890123456789012345678901234567890-resourcemanager-leader         
                      2      21m
   xxxxx1234567890123456789012345678901234567890-restserver-leader              
                      2      21m
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to