Geoff Webster

Is there really still no way to update this secretKey? What is it used for internally to harbor? We ran into an outage because we attempted to change this value...

Could this get rebased? We've also got similar requirements for labeling pods to track cost information.

Note this might be missing this bit of configuration: https://github.com/goharbor/harbor-helm/issues/474 I only noticed it when I tried to enable podReadinessGate and then rollouts failed because the core service health checks...

This is also required to set per path healthchecking with the AWS LB Controller, mainly for the core service: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/93#issuecomment-473679642

@swetashre You could try using the regional STS endpoint.

@dtnyn Have you given the new IP prefix's a try/do they have similar delay? I expect I might be experiencing similar delays as we have the same type of config...

Any updates on PR Progress?

This is still a requirement.

/remove-lifecycle stale

Currently users have to contact AWS Support to get these enabled on the AWS side rather than directly from the CNI: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/monitor.html