Known Issues


Unintended behavior for commands when run by System administrator


Failures during template creation or installation


CSE service fails to start


CSE does not clean up after itself if something goes wrong.

When CSE installation is aborted for any reason, ensure temporary vApp is deleted in vCD before re-issuing the install command


CSE v1.1.x compatibility with vCD 8.20 requires the following package versions


CSE 1.2.6 and up are incompatible with vCD 9.0’


Cluster creation fails when vCD external network has a DNS suffix and the DNS server resolves localhost.my.suffix to a valid IP

This is due to a bug in etcd (More detail HERE, with the kubeadm config file contents necessary for the workaround specified in this comment).

The main issue is that etcd prioritizes the DNS server (if it exists) over the /etc/hosts file to resolve hostnames, when the conventional behavior would be to prioritize checking any hosts files before going to the DNS server. This becomes problematic when kubeadm attempts to initialize the master node using localhost. etcd checks the DNS server for any entry like localhost.suffix, and if this actually resolves to an IP, attempts to do some operations involving that incorrect IP, instead of localhost.

The workaround (More detail HERE is to create a kubeadm config file (no way to specify listen-peer-urls argument in command line), and modify the kubeadm init command in the CSE master script for the template of the cluster you are attempting to deploy. (mstr-ubuntu-16.04.sh or mstr-photon-16.04.sh).

Change command from: kubeadm init --kubernetes-version=v1.13.5 > /root/kubeadm-init.out

To: kubeadm init --config >/path/to/kubeadm.yaml > /root/kubeadm-init.out

Kubernetes version has to be specified within the configuration file itself, since --kubernetes-version and --config are incompatible.


NFS Limitations

Currently, NFS servers in a Kubernetes cluster are not only accessible by nodes of that cluster but also by any VM (outside of the cluster) residing in the same orgVdc. Ideal solution is to have vApp network created for each Kubernetes cluster, which is in our road-map to implement. Until then, please choose one of below workarounds to avert this problem if the need arises.


Enterprise PKS Limitations