Open GenPage opened 1 year ago
here is the solution that might help those who don't want to downgrade the Operator.
Spinnaker Service version: 1.29.5
Spinnaker Operator version: 1.3.1
Kubernetes version: 1.27.4-eks-2d98532
The solution was suggested by @jasonmcintosh so I give credits to him for it. Tested and works just fine with Canary config. I had an issue with the AWS part of it, but it could be translated to anything that contains an encrypted secret string.
canary-config.yml
Patch. The key point here is to have only canary enabled flag.
apiVersion: spinnaker.io/v1alpha2
kind: SpinnakerService
metadata:
name: spinnaker
spec:
spinnakerConfig:
config:
canary:
enabled: true
reduxLoggerEnabled: true
stagesEnabled: true
templatesEnabled: true
showAllConfigsEnabled: true
profiles-kayenta.yml
Patch. This is where the actual AWS (and other) config is stored. kayenta.kayenta
is not a typo, that's the proper Kayenta profile > kayenta-local config format used in the Halyard version of it.
apiVersion: spinnaker.io/v1alpha2
kind: SpinnakerService
metadata:
name: spinnaker
spec:
spinnakerConfig:
profiles:
kayenta:
kayenta:
aws:
enabled: true
accounts:
- name: <redacted>
bucket: <redacted>
region: <redacted>
rootFolder: kayenta
explicitCredentials:
accessKey: encrypted:k8s!n:config-canary-aws!k:accessKeyId
secretKey: encrypted:k8s!n:config-canary-aws!k:secretAccessKey
supportedTypes:
- CONFIGURATION_STORE
- OBJECT_STORE
s3:
enabled: true
prometheus:
enabled: true
accounts:
- name: <redacted>
endpoint:
baseUrl: <redacted>
supportedTypes:
- METRICS_STORE
Moving all the configs to profiles allows you to use encrypted functionality. The AWS credentials need to be injected in a slightly different way from the original Halyard config, ee above example.
Spinnaker Service version:
1.29.2
Spinnaker Operator version:1.3.0
Kubernetes version:1.22
I was unable to upgrade our existing instance to 1.29.2 on the new 1.3.0 operator. I ended up having to nuke our dev instance and re-apply SpinService
1.28.1
with the operator1.2.5
to complete the upgrade to1.29.2
. It seems the operator1.3.0
doesn't allow to apply our configurationSpinService yaml: