Question

我正在Sonarqube 6.7上以AWS EKS运行，部署时带有1个副本，该副本由RDS数据库和EFS支持以实现持久卷。
在我编辑部署文件以使副本数达到2时，新的pod进入CrashLoopBackOff。
让我知道您需要什么所有信息，我很乐意提供。

CrashLoopBackOff吊舱日志：

2019.01.21 06:20:15 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2019.01.21 06:20:15 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.01.21 06:20:15 INFO  app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch -Epath.conf=/opt/sonarqube/temp/conf/es
2019.01.21 06:20:15 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2019.01.21 06:20:17 INFO  app[][o.e.p.PluginsService] no modules loaded
2019.01.21 06:20:17 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.01.21 06:20:22 WARN  app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1
2019.01.21 06:20:22 INFO  app[][o.s.a.SchedulerImpl] Process [es] is stopped
2019.01.21 06:20:22 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Answer 1

我遇到了相同的错误，并通过在spec.template.spec的部署yaml中添加以下内容来解决

securityContext: fsGroup: 999

无法扩展Sonarqube的部署

1 个答案: