-
When I try to install the components defined in the `.lokocfg` file that also has cluster information (`cluster "packet" {`) then I get following error.
```console
$ lokoctl component install prom…
-
We should ship NetworkPolicies limiting what control plane components can connect to by default.
-
Currently fails with the following error:
```
Applying component 'metallb'...
cluster.lokocfg:77,18-39: Unsupported attribute; This object does not have an attribute named "metallb_address_pool"., …
-
So I had a cluster with Dex and Gangway installed. And post installation I also added those flags to the apiserver daemonset.
```yaml
- --oidc-issuer-url=https://dex.foobar.io
- -…
-
We should be deleting the components in CI before destroying the cluster. This would increase the running time for a CI job but it also adds checks for `lokoctl component delete` which we currently do…
-
Right now when deleting the component it always asks for permission and there is no way to suppress it. So add flag similar as `lokoctl cluster apply/destroy`.
-
Currently installing from `packet-testing` file results in following error:
```
Applying component 'metallb'...
cluster.lokocfg:72,18-39: Unsupported attribute; This object does not have an attribu…
-
## General
In some cases, it looks like when deploying a cluster on Packet the k8s control plane doesn't converge properly.
## Symptoms
- `lokoctl cluster apply` finishes successfully, howeve…
-
Today, dex&gangway configuration mention a Let's Encrtypt Issuer in their configuration and they assume they have a specific name.
That works fine when the cert-manager is deployed via lokoctl, but…
-
When we Ctrl+C out of a `lokoctl cluster apply` operation (and likely `destroy`, too), the lokoctl process terminates without killing its child processes. As a result, depending on the exact stage in …