Install nginx-ingress-controller for kubernetes
helm upgrade --install ingress-nginx ingress-nginx \
--repo https://kubernetes.github.io/ingress-nginx \
--namespace ingress-nginx --create-namespaceHelm Basic
Helm Basic
Installation
Script
Pros
- The script will be in
/usr/local/bin, same location askubectl, can be run by normal user
Cons
- No auto update
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
chmod 700 get_helm.sh
./get_helm.shPackage Manager
Pros
- The script will be in
/usr/sbin, it is difficult to be run by normal user if path is not defined $PATH.
Cons
- With auto update using
apt
curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -
sudo apt-get install apt-transport-https --yes
echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list
sudo apt-get update
sudo apt-get install helmSnap
Pros
- No change on system configuration, such as package repo, etc.
- Easy to remove as well
sudo snap install helm --classicReferences
Kubernetes Service External IPs
Kubernetes Service External IPs
After external service created in Kubernetes, the external IPs are not assigned unless the underlying infrastructure supports the automatic creation of Load Balancers and have the respective support in Kubernetes, as is the case with the Google Cloud Platform and AWS.
In such case, all internal IPs are able to be accessed using service port. This is the same as Docker Swarm.
Minikube
Run following command to assign an external IP
minikube service <service_name>Another one is to run minikube tunnel to assign the IP.
kubeadm
Manually assign IP using following configuration file
spec:
type: LoadBalancer
externalIPs:
- 192.168.0.10MetalLB
MetalLB hooks into your Kubernetes cluster, and provides a network load-balancer implementation.
References
Kubernetes service external ip pending
Using minikube tunnel
Ingress class
Load Balancer Service type for Kubernetes
Service Mesh - Kubernetes LoadBalancer Service External IP pending
MetalLB
Service Mesh - Build Kubernetes & Istio environment with kubeadm and MetalLB
2022-01-28 – Jogging
2022-01-28 – Jogging
Quite fast but tired.
Result
2022-01-30 – Swimming
2022-01-30 – Swimming
The speed is 2'44"/100M with 69 strokes, faster than before again.
Result
Windows 7 File Recovery for Windows 10/11
Windows 7 File Recovery for Windows 10/11
class invalid
The error is shown as below
The validation information class requested was invalid. (0x80070544).To fix this issue, prefix the username with target system name. For example
truenas\backup_userLocation cannot be used
The error is shown as below
0x80070544: The specified network location cannot be used.This is because no write access to the target folder.
References
Error code 0x80070544 when attempting to back up Windows 8 onto NAS over Samba
Correct VIM auto indent issue for YAML files
Correct VIM auto indent issue for YAML files
Add following lines in ~/.vimrc
filetype plugin indent on
autocmd FileType yaml setlocal ts=2 sts=2 sw=2 expandtabReferences
Proxmox VM with AVX support
Proxmox VM with AVX support
To install MongoDB in Proxmox VM, the CPU needs to have AVX support. Otherwise, following error appears
WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!Solution
Change CPU type to host, which by pass the CPU simulation.
For container cluster, such as docker swarm, kubernetes, MongoDB might need to be run on specific worker node which have CPU type equals to host.
Impact
Once the CPU set to be host, the live migration may not work, because the hosts have different CPU type. But host will give maximum performance.
References
AVX2
KVM: Which CPU for VM ('host' vs 'kvm64') to use for web load?
Remove entry in ~/.ssh/known_hosts
Remove entry in ~/.ssh/known_hosts
This is required if host key replaced in target server.
ssh-keygen -R HOSTNAME
ssh-keygen -R IP_ADDRESSReferences
Create join command for Kubernetes master
Create join command for Kubernetes master
kubeadm token create --print-join-command