You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
What you expected to happen: When I delete a KuBo deployment, I expect the worker nodes to ignore the absence of a master node because it can be that this one gets deleted before the worker. There used to be a way to avoid this issue introduced in this commit: 79b6618#diff-34eaab0d59f5a3b9bd22cd961a1176d9
How to reproduce it (as minimally and precisely as possible): deploy cfcr with a lot of workers then delete it. Kubelet drain will fail rapidely.
Name name
UUID bc4044b2-ab6c-4f5f-942f-1330dc2f1989
Version 268.7.0 (00000000)
Director Stemcell ubuntu-xenial/250.29
CPI vsphere_cpi
Features compiled_package_cache: disabled
config_server: enabled
local_dns: enabled
power_dns: disabled
snapshots: disabled
User admin
What happened: I was not able to delete a KuBo deployment because the drain script failed since it could not reach the master node when it came to execute the
kubectl cordon
command (https://github.com/cloudfoundry-incubator/kubo-release/blob/master/jobs/kubelet/templates/bin/drain.erb#L21)What you expected to happen: When I delete a KuBo deployment, I expect the worker nodes to ignore the absence of a master node because it can be that this one gets deleted before the worker. There used to be a way to avoid this issue introduced in this commit: 79b6618#diff-34eaab0d59f5a3b9bd22cd961a1176d9
How to reproduce it (as minimally and precisely as possible): deploy cfcr with a lot of workers then delete it. Kubelet drain will fail rapidely.
Anything else we need to know?:
Environment:
vsphere
The text was updated successfully, but these errors were encountered: