You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of building a simple pipeline using Jenkins X.
However, I have encountered a minor problem. When adding the helmfile via the jx CLI using jx-gitops helmfile add --chart stable/sonarqube the Helm Chart in the cluster was added, however I get the following issue.
~ kubectl get pods --namespace jx
NAME READY STATUS RESTARTS AGE
...
sonarqube-postgresql-0 0/1 CreateContainerConfigError 0 2d4h
sonarqube-sonarqube-679d67f8dc-kzmlr 0/1 CreateContainerConfigError 0 2d4h
As you can clearly see, the pods are in an error state. If you look at the events of the pods, you can see that the source of the error is the missing postgres secret.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulled 9m23s (x1256 over 2d3h) kubelet Container image "sonarqube:7.9.2-community" already present on machine
Warning Failed 4m30s (x1280 over 2d3h) kubelet Error: secret "sonarqube-postgresql" not found
The strange thing is, when I install SonarQube through the Helm CLI helm install stable/sonarqube, it works without errors (postgres secret was present).
Now I wonder, is the problem with Jenkins X or have I forgotten something? I know the problem could be fixed by installing the Helm Chart manually. But shouldn't Jenkins X already do everything correctly?
When looking at the yaml configurations in config-root/namespaces/jx/sonarqube the secret is also defined correctly, but maybe jenkins X forgot to create the resource?
Below are my installed versions.
~ kubectl version --short
Client Version: v1.19.4
Server Version: v1.20.0
~ minikube version
minikube version: v1.16.0
~ jx version
version: 3.1.88
The text was updated successfully, but these errors were encountered:
Hello all,
I am in the process of building a simple pipeline using Jenkins X.
However, I have encountered a minor problem. When adding the helmfile via the jx CLI using
jx-gitops helmfile add --chart stable/sonarqube
the Helm Chart in the cluster was added, however I get the following issue.~ kubectl get pods --namespace jx NAME READY STATUS RESTARTS AGE ... sonarqube-postgresql-0 0/1 CreateContainerConfigError 0 2d4h sonarqube-sonarqube-679d67f8dc-kzmlr 0/1 CreateContainerConfigError 0 2d4h
As you can clearly see, the pods are in an error state. If you look at the events of the pods, you can see that the source of the error is the missing postgres secret.
The strange thing is, when I install SonarQube through the Helm CLI
helm install stable/sonarqube
, it works without errors (postgres secret was present).Now I wonder, is the problem with Jenkins X or have I forgotten something? I know the problem could be fixed by installing the Helm Chart manually. But shouldn't Jenkins X already do everything correctly?
When looking at the yaml configurations in
config-root/namespaces/jx/sonarqube
the secret is also defined correctly, but maybe jenkins X forgot to create the resource?Below are my installed versions.
~ kubectl version --short Client Version: v1.19.4 Server Version: v1.20.0
~ minikube version minikube version: v1.16.0
~ jx version version: 3.1.88
The text was updated successfully, but these errors were encountered: