Bump Kommander chart

[gracedo]

https://jira.d2iq.com/browse/D2IQ-64099
Bumps the kommander chart to pull in the latest changes which added the secret reloader annotations for karma and thanos proxies.

The following needs to be done (with #438 merge):

1. Bump the version of mtls-proxy used in kommander-thanos and kommander-karma and add the secret.reloader.stakater.com/reload annotations ✅ DONE IN [kommander-karma] [kommander-thanos] Add secret reloader annotations charts#443
2. Bump the deps of kommander-thanos and kommander-karma in kommander chart to pull in the latest changes from the above ✅ DONE IN kommander: Bump kommander-karma and kommander-thanos deps charts#446
3. Bump kommander version in kubeaddons-kommander ✅ DONE IN THIS PR

Testing

I tested this manually by hosting mtls-proxy, kommander-thanos, kommander-karma, and kommander charts on my personal GH. I konvoy up on addons version master, then upgraded the kommander chart by deploying addons with my kubeaddons-kommander branch gracedo/bug_certs_D2IQ-64099 (this branch has obviously now been updated to mesosphere's hosted kommander chart).

  - configRepository: https://github.com/mesosphere/kubeaddons-kommander
    #configVersion: master
    configVersion: gracedo/bug_certs_D2IQ-64099
    addonsList:
    - name: kommander
      enabled: true

Upon upgrading, I verified that updated secrets were federated out to the managed clusters (as they were before) then checked that the proxies now had the reloader annotation:

I checked Thanos and Karma UIs in the kommander cluster and saw that they were still able to connect to the proxies even after upgrading

[gracedo]

@juliangieseke @hectorj2f Can we make sure to use this updated kommander chart version for tomorrow's MWT?

[samvantran]

this should point to -11?

[samvantran]

kommander-thanos doesn't need the same annotation?

[shaneutt]

You should check out #12 as there are some more recent updates there that this conflicts with and make adjustments here accordingly

[gracedo]

@shaneutt Looks like that PR bumped to 0.4.12 which covers the 0.4.11 bump here :) closing this out!