Mike Beaumont

Indeed, that works, thanks. It would be possible to use `aur sync` instead of the separate `fetch` + `build` steps which would simplify my `mkosi.build`. Now I'm running into `pacinstall`s...

* Service view - select services by type * Dropdown selector for service type * OR button per service type * Hostname generator view * We will already have this...

Let's close it for now and if we need this we'll create this again

Yep this is done

I think the "install with helm" section could be under "Deploy control plane"? Like users will always want `kumactl` but not necessarily for installing the CP, so anytime they're installing...

Another unfortunate side effect is that every tile at https://kuma.io/install/2.2.x/ redirects to the [install `kumactl` page](https://kuma.io/docs/2.2.x/production/install-kumactl/)

@johnharris85 Do we want to keep `kumactl install demo` as is?

https://github.com/kumahq/kuma-website/security/dependabot

Security advisories are thing that are [manually written and released by us](https://docs.github.com/en/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)

Potentially, but dependabot can't update every dependency if it's not compatible with the constraints we have.