Matt Johnston


tracking https://github.com/canonical/k8s-snap/issues/262

Verified that this issue is not impacted by adding the roles to the service account from the guide

flagged as `research` because I don't yet know if this is actually a good idea

Update: The fact that the `helm_release.set` value changes is a fundamental constraint about the `bcrypt()` implementation in Terraform. This could maybe be fixed by using a `provisioner` to create the...

Investigate using a K8s secret for argo's password instead of helm values

[fission.io](https://fission.io)

is ExternalDNS the way?? edit: no

When using Terraform it is simple to consume the new CNAME/IP for creating DNS records. We can create a Route53 record resource using the CNAME/IP with a custom domain from...

If this solution involves setting a leader node using array index 0 in `infrastructure.cndi.nodes` for the initial deployment, and not setting a node as `role: leader` that is totally fine....