Why do I see kots.io/exclude: true on all my HelmChart Custom Resources?

I was looking at my deployed app recently and I noticed that all the HelmChart custom resource instances, when viewed in the View Files tab of the App Manager console, have

metatdata:
  annotations:
    kots.io/exclude: true

Why is this getting added? Should I be worried about this?

This is done to make maintaining backwards compatibility easier. When a new kots kind is added, older versions won’t know about it and may try to deploy it. The kots.io/exclude annotation works even with very old kots releases. Most kots kinds have been around for a long time, but the annotation was added to all of them for consistency.

1 Like