ChenpiDog opened a new issue, #10400:
URL: https://github.com/apache/dolphinscheduler/issues/10400

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   In the official documents of 2.0.5 and 3.0.0-beta-1, there are problems in 
the deployment of kubernetes. The deployment cannot succeed according to the 
instructions in the documents.
   
   Encountered the following problems:
   
   1) Execute "helm dependency update." "Error: can't get a valid version for 
repositories PostgreSQL, zookeeper. try changing the version constraint in 
chart.yaml". Set chart In yaml, the PostgreSQL version is changed to 11.0.0, 
and the zookeeper version is changed to 9.0.0. This step can be successful.
   
   2) After "helm install dolphin scheduler. --set image.tag=2.0.5" is 
executed, the status of pod is createcontainerconfigerror, and the error 
message of pod is: "error: could't find key PostgreSQL password in secret 
default/dolphin scheduler PostgreSQL". Check the secret. There is PostgreSQL 
password in the secret.
   
   ### What you expected to happen
   
   I hope the application can be successfully deployed according to the 
official website documents, but there are many problems.
   
   ### How to reproduce
   
   Just follow the official website documents to reproduce the problem.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.0.0-beta-1
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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