wolfboys commented on issue #2404:
URL: 
https://github.com/apache/incubator-streampark/issues/2404#issuecomment-1563833945

   > This error can have many different reasons that I encountered and 
resolved. It's possible that your situation is different from mine, but I still 
hope to help you.
   > 
   > My Env: (streampark2.1.0 + flink1.14.5 + k8s Major:"1", Minor:"22+")
   > 
   > 1.Check the version of K8s to ensure it is 1.19 or above.
   > 
   > 2.Verify if .kube/config has the appropriate permissions (I encountered 
this issue due to insufficient permissions for the service account).
   > 
   > 3.Flink REST endpoint cannot be accessed or requested .I found that I 
could make a successful REST request using curl, but streampark couldn't 
retrieve the REST address. After investigation, I discovered an error in the 
method 
**org.apache.streampark.flink.kubernetes.ingress.IngressController#ingressUrlAddress**,
 where the parsing of the K8s version was incorrect. The code in 
org.apache.streampark.flink.kubernetes.ingress.IngressStrategy was modified as 
follows: `val version = 
s"${versionInfo.getMajor}.${versionInfo.getMinor}".toDouble` Changed to: `val 
version = s"${versionInfo.getMajor}.${versionInfo.getMinor}".replace("+", 
"").toDouble` This resolved the issue.
   > 
   > 4. When submitting the **Flink on K8s** job, it is important to ensure 
that the **streampark.workspace.remote** parameter is configured correctly. You 
can specify an HDFS (or file://) address, and the Flink parameter 
jobmanager.archive.fs.dir should also point to this address (streampark 
automatically appends this parameter). (In my case, I mounted a shared 
directory PVC that was accessible in both the Flink pod and streampark pod,then 
i solved the issue.)
   > 
   > 希望对你有帮助.
   
   Thanks for your feedback. There was indeed a bug in the version parse, We 
have already fixed it. please see 
[here](https://github.com/apache/incubator-streampark/pull/2741)
   


-- 
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