You are viewing version 2.25 of the documentation, which is no longer maintained. For up-to-date documentation, see the latest version.

Errors and Troubleshooting

This guide shows which errors are OK to ignore, how to troubleshoot Operator installation and manifest deployment, and where to ask for help.

Reconciler error

You may see this error even though Operator successfully applies your manifest. This error may be normal depending on the frequency of the error. Controllers work with a local cache that can be out of sync. The issue should resolve itself via repeated synchronization. One error may be fine since it’s in the design of the reconciler. Too many means something is wrong.

  "level": "error",
  "ts": 1592879777.6785922,
  "logger": "controller-runtime.controller",
  "msg": "Reconciler error",
  "controller": "spinnakerservice-controller",
  "request": "spinnaker-migration/spinnaker",
  "error": "Operation cannot be fulfilled on
   \"spinnaker\": the object has been modified; please apply your changes to the latest version and try again",
  "stacktrace": "*zapLogger).Error

Kustomize panic error

If you installed Kustomize standalone, Kustomize v4.0+ kustomize build throws a panic error when it tries to parse and build using the patch files in the spinnaker-kustomize-patches repo. For example:

panic: runtime error: index out of range [145] with length 145 [recovered]
 panic: runtime error: index out of range [145] with length 145

Starting with kubectl v1.21 , the bundled Kustomize version is v4.0.5, so if you execute kubectl kustomize ., you also see this error.


  • Downgrade standalone Kustomize to v3.8.10.
  • Downgrade to kubectl v1.19.

Help resources

Last modified April 19, 2021: (c9f463b)