Mateusz Gozdek
Mateusz Gozdek
That can be done in https://github.com/flexkube/libflexkube/blob/ef0532aae1ea0c4dff9a6b5a137a35886973d02a/pkg/container/containers.go#L322-L340, maybe we could create a config container or something using new image?
This for example, should allow to spawn kubelets on their own during node creation and then K8s operator could pick up their management, without getting the container ID somehow.
However, this may result in potentially removing containers, which were not created using flexkube.
Also relevant #98.
See also https://github.com/etcd-io/etcd/issues/8458.
This will actually also allow multi-tenancy, assuming different port are used.
I also got: ``` Error: Provider produced inconsistent final plan When expanding the plan for flexkube_controlplane.bootstrap to include new values learned so far during apply, provider "registry.terraform.io/-/flexkube" produced an invalid...
Except the error above, with upcoming fixes, adding new controller node works fine.
The same errors appears when removing new controller node. But running Terraform twice fixes it.
>Still ends each API call with "?timeout=32s" This is the timeout for individual requests, which I'd expect `client-go` to retry performing. This timeout is also configured when creating rest client...