-
Wipe the following directories so that there are no conflicts:
- `assets/cluster-assets/`
- `assets/terraform-modules/`
Every time user run `lokoctl cluster apply` these files can be deleted fr…
-
Make `asset_dir` an optional variable by adding default value as `assets`.
This will be one less variable user has to provide when starting out.
-
Currently, when one tries to uninstall component, which is not configured, `lokoctl` will happily proceed with it. It _seems_ to me, that we should return an error in such case, as this is similar to …
-
## General
Right now when a user runs `lokoctl cluster apply`, by default no Terraform output is shown. I think this isn't ideal for the following reasons:
- When things fail, the user may miss …
-
## General
Our current way of handling cloud credentials in `lokoctl` is inconsistent and confusing to the user. For example, the Packet [reference](https://github.com/kinvolk/lokomotive/blob/maste…
-
Currently, it is quite confusing: #698.
```
Applying component 'metallb'...
cluster.lokocfg:77,18-39: Unsupported attribute; This object does not have an attribute named "metallb_address_pool"., …
-
In #839 we found some limitations of our existing way we set up LBs for Ingress on AWS, which we should address.
See also #372.
-
**Description**
If we un-install kubernetes controlplane component via helm, on re-applying cluster it does not creates required resources and times out
**Impact**
In-availability of Kubernet…
-
When using S3 as a storage for the terraform state and assets we don't need local dir on the disk. Terraform needs a temporary dir to have all the files on the disk. But this dir can be deleted.
So…
-
## General
We want to have a well-defined structure for the Lokomotive configuration for the following reasons:
- We want to be able to evolve the configuration structure over time in a way whic…