When list docker containers using docker ps -a command, there is nothing in the list, but using systemctl status docker can see running processes. And the docker container services are running in the servers.
The issue was fixed by removing docker and lxc from snap.
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/aio/deploy/recommended.yamlhelm upgrade --install ingress-nginx ingress-nginx \
--repo https://kubernetes.github.io/ingress-nginx \
--namespace ingress-nginx --create-namespacePros
/usr/local/bin, same location as kubectl, can be run by normal userCons
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
chmod 700 get_helm.sh
./get_helm.shPros
/usr/sbin, it is difficult to be run by normal user if path is not defined $PATH.Cons
aptcurl 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 helmPros
sudo snap install helm --classicAfter 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.
Run following command to assign an external IP
minikube service <service_name>Another one is to run minikube tunnel to assign the IP.
Manually assign IP using following configuration file
spec:
type: LoadBalancer
externalIPs:
- 192.168.0.10MetalLB hooks into your Kubernetes cluster, and provides a network load-balancer implementation.
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
Quite fast but tired.
The speed is 2'44"/100M with 69 strokes, faster than before again.
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_userThe error is shown as below
0x80070544: The specified network location cannot be used.This is because no write access to the target folder.
Error code 0x80070544 when attempting to back up Windows 8 onto NAS over Samba