fix(calico): remove pinned version

[FredrikCarlssn]

What kind of PR is this?

• kind/bug

What does this PR do / why do we need this PR?

Bumps calico-accountant from 0.1.6-ck8s2 to 0.1.6-ck8s3.
This fixes an issue where, under Kubespray-based clusters, the
exporter could emit duplicate metric samples with identical label sets during
the same scrape interval.

This is linked to this PR on apps

Checklist

• Proper commit message prefix on all commits
• Change checks:
  • The change is transparent
  • The change is disruptive
  • The change requires no migration steps
  • The change requires migration steps
  • The change updates CRDs
  • The change updates the config and the schema
• Documentation checks:
  • The public documentation required no updates
• Metrics checks:
  • The metrics are still exposed and present in Grafana after the change
  • The metrics names didn't change
• Logs checks:
  • The logs do not show any errors after the change
• PodSecurityPolicy checks:
  • Any changed Pod is covered by Kubernetes Pod Security Standards
  • Any changed Pod is covered by Gatekeeper Pod Security Policies
  • The change does not cause any Pods to be blocked
• NetworkPolicy checks:
  • Any changed Pod is covered by Network Policies
  • The change does not cause any dropped packets
• Audit checks:
  • The change does not cause any unnecessary Kubernetes audit events
• Falco checks:
  • The change does not cause any alerts to be generated by Falco
• Bug checks:
  • The bug fix is covered by regression tests

[Xartos]

Since config isn't updated automatically, we'd need to add migration docs for this as well. This should also mention that the apps version needs to be a supported version

[FredrikCarlssn]

Since config isn't updated automatically, we'd need to add migration docs for this as well. This should also mention that the apps version needs to be a supported version

Absolutely, coming up. BTW do we actually know which version the [PR] will be in yet, or should we just have a placholder/note for the migration now?

[Xartos]

Since config isn't updated automatically, we'd need to add migration docs for this as well. This should also mention that the apps version needs to be a supported version

Absolutely, coming up. BTW do we actually know which version the [PR] will be in yet, or should we just have a placholder/note for the migration now?

Assume it will be in the next release 2.28, and if you don't manage to get it merged before the feature freeze of 2.28 you just change it to 2.29

[rarescosma]

lgtm

Vacation

[davidumea]

Great thank you!