These sections list the known limitations with Juke Multicloud Release 2.2.1 and Juke Multicloud Release 2.2.
Known Behavior in Juke Multicloud Release 2.2.1
This section lists known limitations with Juke Multicloud Release 2.2.1.
JUKE-906 Unable to delete a node—You can not delete a node because of a glitch.
As a workaround, create new nodes and then delete the ones that are no longer needed.
JUKE-910—When a user attaches a node to a worker in a cluster, the master and ETCD can not be modified. This is triggered when a user and an admin creates a Kubernetes cluster using the same nodes. However, the node is unavailable for other users after the Kubernetes cluster is completed.
There is no workaround.
Known Behavior in Juke Multicloud Release 2.2
This section lists known limitations with Juke Multicloud Release 2.2.
JUKE-813 Storage replication—Cloud storage rules allow a maximum of 120 replicas (copies) of a storage volume to be taken. Currently there is no limit on the number of replicas that are taken. When more than 120 replicas are requested, the storage volume will fail to restart when the server is rebooted.
JUKE-816 Adding a node to a Kubernetes cluster —Once a Kubernetes node has been removed from a cluster, the node can not be added to the same cluster or another cluster.
JUKE-822 Enabling a region in AWS—When you enable a region in AWS, the default VPC provided in AWS is used. When the default VPC is not present, the region is not enabled.