-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provisionning fails with RKE 1.5.9 when extra_env
is used for kube-api
service
#3587
Comments
This bug prevents us from upgrading as kube-apiserver has environment variables set (like the |
hi @tmsdce, thank you for reporting the issue. I can confirm that this is a bug. Root Cause This bug occurs in RKE v1.5.9. If extra_env is set for kube-api as below in the cluster config file, the
Workaround If your cluster is stuck in the failed status, remove the extra_env for kube-api from the cluster config and run If you need to set the extra_env for kube-api, please use RKE v1.5.8 for now until the bug is fixed in the coming release. |
the fix can be validated by using https://github.com/rancher/rke/releases/tag/v1.6.0-rc6 Root causePreviously, we declared the Env slice with the size of the What was fixed, or what changes have occurredWe fix this issue by declaring the Env variable as an empty slice. Areas or cases that should be testedcluster provisioning and upgrading What areas could experience regressions?cluster provisioning and upgrading Are the repro steps accurate/minimal?yes We should validate that setting extra env does not cause the reported error when either creating a new cluster or updating an existing cluster.
|
Description
I'm trying to create a cluster with extra_env specified for the kube-api service. This works fine with RKE 1.5.8 but fails with RKE 1.5.9. I think the following commit might be involved : 2e767c8
RKE version: 1.5.9
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
VirtualBox but also fails on vSphere (the RKE terraform provider is used in this case)
cluster.yml file:
Steps to Reproduce:
rke up
and wait for it to crash when trying to start thekube-apiserver
container (see logs below)Results:
The text was updated successfully, but these errors were encountered: