commits.to

Following the model of mcserverhosting.net, have a look at https://www.packtpub.com/product/keycloak-identity-and-access-management-for-modern-applications/9781800562493

https://github.com/fluxcd/flux2/issues/1448

https://fluxcd.io/docs/faq/#what-is-the-behavior-of-kustomize-used-by-flux

There is a "Not yet" answer in here that we can upgrade to a more affirmative sounding response, https://fluxcd.io/docs/migration/helm-operator-migration/#are-automated-image-updates-supported – another here: https://fluxcd.io/docs/migration/helm-operator-migration/#how-do-i-automatically-apply-my-helmrelease-resources-to-the-cluster

https://cloud-native.slack.com/archives/CLAJ40HV3/p1626162104239000 A user of MS Teams + notification-controller alerts has reported an issue that sounds like a problem caused by rate limiting. The documentation about rate limiting in Notification Controller does not make it especially clear where rate limits can be applied, or whether the controller has been built to back off in the event that it has been rate limited by a provider. Things are complicated because MS docs indicate there are 4 status codes which you should retry, and not all are 50x codes. (To close this commit, we can make some progress understanding the issue and report back on this Slack thread.) The ideal resolution is a doc that shows screenshot of Grafana illustrating when we are being rate-limited and by what returned status code. Follow-up would be a PR publishing this doc, and/or an issue report that describes the bug which results in messages being dropped. NB: report still needs validation.

PRs and Issues together should total 90 or less