My spinnaker kayenta pod can't start when I use minio


#1

I ues minio when I chhoose a storage service. Everything is going well.
version:1.8.3
I can’t use aws or gcs.
Now, I want use canary. I saw this post
url: Canary and “foolproof” install

I use the same way,but my spinnaker kayenta-pod can’t start.
Pod log:
2018-08-10 03:31:10.690 INFO 1 --- [ scheduler-5] c.n.k.o.controllers.PipelineController : Health indicators are still reporting DOWN; not starting orca queue processing yet: DOWN {redisHealth=UP {}, canaryConfigIndexingAgent=DOWN {existingByApplicationIndexCount=0, expectedByApplicationIndexCount=1, cyclesInitiated=73, cyclesCompleted=73}, diskSpace=UP {total=105553780736, free=81575895040, threshold=10485760}}

canary:
enabled: true
serviceIntegrations:
- name: google
enabled: false
accounts: []
gcsEnabled: false
stackdriverEnabled: false
- name: prometheus
enabled: true
accounts:
- name: prometheus
endpoint:
baseUrl: http://10.88.10.48:30009
supportedTypes:
- METRICS_STORE
- name: datadog
enabled: false
accounts: []
- name: aws
enabled: true
accounts:
- name: test001
bucket: spin-29b8cfa0-409d-410a-8c6e-4622ef2ea0ff
rootFolder: kayenta
endpoint: http://minio-service.spinnaker:9000
secretAccessKey: testtest
supportedTypes:
- CONFIGURATION_STORE
- OBJECT_STORE
s3Enabled: true
reduxLoggerEnabled: true
defaultMetricsAccount: prometheus
defaultStorageAccount: test001
defaultJudge: NetflixACAJudge-v1.0
defaultMetricsStore: prometheus
stagesEnabled: true
templatesEnabled: true
showAllConfigsEnabled: true

#2

:joy:
It’s my fault,sorry. I forgot to write the accseeID