Complete Phase 8 of Kubernentes-based infrastructure

[No767]

Summary

This is the one that actually makes the whole cluster usable. Effectively, this adds in our routing rules, so if traffic goes to /auth, they are directed accordingly. There are actually quite a lot of changes within this PR that had to happen that aren't directly related with the plan. Namely:

• k3d now uses Cilium for both the CNI and enforcement of network policies. This replaces Flannel for CNI, and kube-router for the netpol controller for network policy.

  • This now aligns our stack to what Scaleway uses in production. Should help with some networking issues locally
  • Had to be done because kube-router kept on racing with our SQL migration jobs, and would literally block all ingress connections to Postgres for some reason
    • Cilium doesn't have this same behavior, so we had to use that to fix it

• Management of charts are now relegated to helmfile

  • This means no version pinning or defaulting in our scripts (yay!)
  • Separates the concern of values that would have been stored in values.yaml into the helmfile.yaml file
    • Instead of specifying flags that set the configuration options, they are declaratively stored in a file that contains the source of truth; that being hemlfile.yaml

Note that technically the /auth route doesn't work as of now as within kratos.prod.yml, the base URLs are hardcoded to be either https://ucmacm.dev or https://api.ucmacm.dev. The plan is to introduce the layered config overriding system we have for our main kratos.yml config into here. Completed and should now work

Types of changes

What types of changes does your code introduce to Kanae?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• All workflows pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud