Tristan Keen

Thanks for the quick reply @cppforlife, yes I was meaning an Application CR & your explanations make sense. Will proceed as is for now, but look forward to any further...

Having read through the code a bit more, is it actually intended behaviour to do nothing until the "NotBefore" time? Our SOP is to drain such nodes at earliest convenience...

Thanks, I've updated the title to better match the actual issue, as I certainly would like an option (if not the default/only functionality) to begin draining and termination as soon...

@jdomag I haven't tried it yet (I use helmfile not ArgoCD for deploying this project, nor have tried the 2.3 chart myself yet) but there supposedly is an ArgoCD workaround....

According to AWS support the listener/listener-rule resources themselves are deleted when the loadbalancer is, but the `resourcegrouptaggingapi` records get left behind. They don't ever seem to get cleared up -...

@benjdlambert if talking about "Relations not being deleted properly" please see my new issue https://github.com/backstage/backstage/issues/13774 for similar about `hasMember` between Group & User. Where would the "discussion" take place?

@dmitryp-orca see https://grafana.com/blog/2022/08/30/security-release-new-versions-of-grafana-and-grafana-image-renderer-with-a-high-severity-security-fix-for-cve-2022-31176/ - in the 8.5 series would need at least 8.5.11

Can I challenge you a bit on this @MOZGIII - I don't see the very useful k8s events you get from `kubectl get events` in the audit data, event when...

Looks like it was made to be a Set due to an issue with changing host order in API when the cert goes from Pending to Active: https://github.com/cloudflare/terraform-provider-cloudflare/issues/799

Having each account/role start with a different initial colour (based on a hash of the account ID/role name for cheap repeatability between users) would be a nice start