node-cidr | Javascript library for manipulating IP addresses | TCP library

This is a known issue which unfortunately is not going to be fixed as the feature is planned to be deprecated. Also, see this source:

I wouldn't expect a change for this issue. Upstream Kubernetes wants to deprecate component status and does not plan on enhancing it. If you need to check for cluster health using other monitoring sources is recommended.

kubernetes/kubernetes#93171 - 'fix component status server address' which is getting recommendation to close due to deprecation talk.

kubernetes/enhancements#553 - Deprecate ComponentStatus

kubernetes/kubeadm#2222 - kubeadm default init and they are looking to 'start printing a warning in kubect get componentstatus that this API object is no longer supported and there are plans to remove it.'

This context deadline exceeded generally happens because of

1. Using wrong certificates. You could be using peer certificates instead of client certificates. You need to check the Kubernetes API Server parameters which will tell you where are the client certificates located because Kubernetes API Server is a client to ETCD. Then you can use those same certificates in the etcdctl command from the node.

2. The etcd cluster is not operational anymore because peer members are down.

You can provide the supplementalGroups under securityContexts section.

Looks like you have started the api-server with flag --insecure-bind-address=127.0.0.1. Port 8080 is not free on your host, hence it is failing to start.

Serving insecurely on 127.0.0.1:8080 failed to listen on 127.0.0.1:8080: listen tcp 127.0.0.1:8080: bind: address already in use