Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When enable the devops, The ks-apiserver pod will be Crashbackoff status after the installer complete install. #2276

Open
yasyx opened this issue Apr 30, 2024 · 1 comment

Comments

@yasyx
Copy link

yasyx commented Apr 30, 2024

Upon reviewing the logs, I discovered that the error was due to the Jenkins password and JWT secret being configured as empty. Consequently, I examined the ks-installer playbook and found that in the file roles/ks-core/config/tasks/main.yaml, the retrieval of the secret did not include the namespace, which was the cause of the error. Therefore, I would like to submit a pull request (PR) to fix this issue.

{{ bin_dir }}/kubectl get secret kubesphere-secret -o jsonpath='{.data.token}' | base64 -d

{{ bin_dir }}/kubectl get secret kubesphere-secret -o jsonpath='{.data.secret}' | base64 -d

@yasyx
Copy link
Author

yasyx commented Apr 30, 2024

This issue may only occur when running ks-installer locally; it might not exist when running ks-installer within a Kubernetes (k8s) environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant