Create join command for Kubernetes master
kubeadm token create --print-join-command
kubeadm token create --print-join-command
After cloned Ubuntu VM, some tasks are required.
/etc/hostname
/etc/hosts
rm /etc/ssh/ssh_host_*
dpkg-reconfigure openssh-server
After run init, following error was occurred.
dial tcp 127.0.0.1:10248: connect: connection refused.
Run following command to reinit kubernetes master or worker
sudo mkdir /etc/docker
cat <<EOF | sudo tee /etc/docker/daemon.json
{
"exec-opts": ["native.cgroupdriver=systemd"],
"log-driver": "json-file",
"log-opts": {
"max-size": "100m"
},
"storage-driver": "overlay2"
}
EOF
sudo systemctl enable docker
sudo systemctl daemon-reload
sudo systemctl restart docker
sudo kubeadm reset
sudo kubeadm init
Join cluster
kubeadm join ...
Label it as worker
kubectl label node kworker1 node-role.kubernetes.io/worker=worker
Following messages are printed to create pod network.
You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
Install Weave Net for NetworkPolicy.
kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"
Kubernetes kubeadm init fails due to dial tcp 127.0.0.1:10248: connect: connection refused
kubernetes cluster master node not ready
Weave Net for NetworkPolicy
There are many reasons that some dangling disk images files exists in Proxmox folder. To remove them from the Proxmox storage, might not be possible, and they might be not shown in VM hardware items as well.
This is to fix the following issues
qm rescan
If rescan can not fix the issue, rename the old disk or disk folder, then restart VM to confirm the disk file is not necessary. Then remove disk.
Run following command to convert vmdk to qcow2
qm importdisk <VM_ID> <Virtual Disk>.vmdk <storage> --format qcow2
Here, VM_ID is a number. After completed a newly created disk appears in VM
Double click the newly created disk, then select VirtIO Block device.
Select Write Back as cache method
Double click the newly created disk, then select SATA device.
Select Write Back as cache method
apt remove --auto-remove open-vm-tools
apt remove --auto-remove xserver-xorg-video-vmware
apt purge open-vm-tools
apt purge open-vm-tools-desktop
yum remove open-vm-tools open-vm-tools-desktop
Here, talking about physical RAM disk, not the software version.
There are three types interface for physical RAM disk, one is PCIe interface, another SATA, or the external drive.
There are two controllers on such board, one is to simulate device, second one is to address the RAM array.
Following web page shows the design of such board
The way we made an external PCIe RAM disk based on the DDR memory Cache
Testing result
Full overview of the new DDR RAM disk
SATA Interface
PCIe Interface
External Drive
If a stick of RAM is given a constant supply of power, could it be used as a permanent storage?