Tim Buckley

Thanks for the info, I've just updated index.yaml to fix the broken links and added a pull request (https://github.com/monasca/monasca-helm/pull/447) to fix the rest of the references to monasca.io in this...

It looks like RBAC isn't turned on, have you set `rbac.create` to `true` in your helm values (e.g. by adding `--set rbac.create=true` to the install/upgrade command)?

The cleanup job will have trouble as it's probably running with the old configuration that had no RBAC enabled - you can just delete the job (`kubectl delete job monasca-cleanup-job-...`)...

Hmm, I don't see any errors in those logs - are those the previous container logs (`kubectl logs -p ...`)? It looks like thresh is running alright in that 2nd...

That definitely should be enough memory, at least if you only have a few agents running. You might need more resources if you have more nodes (like 10+) but it's...

Yep, this should be enough to install on k8s 1.8: ``` helm install monasca/monasca \ --name monasca \ --namespace monitoring \ --set alarm_definition_controller.resource_enabled=false \ --set alarm_definition_controller.controller_enabled=false ``` We're hoping to...

`monasca-adc` should disappear, yes. The various `init-job` pods are supposed to run to completion and exit. By default `kubectl` hides completed pods, so you may need to use `kubectl get...

We should tweak this to make use of the `monasca_secret_env` template to keep secret handling standardized

Related: * `token` join method problems issue: https://github.com/gravitational/teleport/issues/26885 * `BotInstance` RFD: https://github.com/gravitational/teleport/pull/36510

> we should switch to UIDs rather than full users to work around `/etc/passwd` unavailability Since I think users are most likely to want to keep interacting with named users...