While creating a duplicate deployment system for testing purposes we may require to install a very old version of helm
I have done this by using the below steps.
# curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3
# chmod +x get_helm.sh
# ./get_helm.sh -v v3.1.2
# helm version
version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}
While executing the command "vagrant up" you will see the following error message.
Box 'generic/ubuntu2004' could not be found. Attempting to find and install...
servername: Box Provider: virtualbox
servername: Box Version: 3.3.0
The box 'generic/ubuntu2004' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://atlas.hashicorp.com/generic/ubuntu2004"]
Error: The requested URL returned error: 404 Not Found
So the issue is with your vagrant version (1.8.7), so here we would require the last Vagrant version 2
On your Ubuntu 16.04LTS vagrant binay download will show the following error.
ajeesh@Aspire-A515-51G:~/Downloads/vagr$ ./vagrant --help
/tmp/.mount_vagranhKrhmD/usr/bin/ruby2.6: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_vagranhKrhmD/usr/lib/x86_64-linux-gnu/libruby-2.6.so.2.6)
/tmp/.mount_vagranhKrhmD/usr/bin/ruby2.6: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_vagranhKrhmD/usr/lib/x86_64-linux-gnu/libruby-2.6.so.2.6)
[vagrant@kmaster ~]$ kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
scheduler Unhealthy Get "http://127.0.0.1:10251/healthz": dial tcp 127.0.0.1:10251: connect: connection refused
controller-manager Unhealthy Get "http://127.0.0.1:10252/healthz": dial tcp 127.0.0.1:10252: connect: connection refused
etcd-0 Healthy {"health":"true"}
And other commands everything works fine.
[ajeesh@kmaster ~]$ kubectl cluster-info
Kubernetes master is running at https://172.42.42.100:6443
KubeDNS is running at https://172.42.42.100:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
[ajeesh@kmaster ~]$ kubectl get pods --all-namespacesNAMESPACE NAME READY STATUS RESTARTS AGEkube-system calico-kube-controllers-56b44cd6d5-27smn 1/1 Running 0 6m43skube-system calico-kube-controllers-56b44cd6d5-g6gfw 0/1 NodeAffinity 0 118dkube-system calico-node-rv52x 1/1 Running 0 6m42skube-system calico-node-tq84v 1/1 Running 4 118dkube-system calico-node-wg8h9 1/1 Running 0 6m42skube-system coredns-f9fd979d6-69dhx 1/1 Running 2 118dkube-system coredns-f9fd979d6-rff6t 1/1 Running 2 118dkube-system etcd-kmaster.example.com 1/1 Running 3 118dkube-system kube-apiserver-kmaster.example.com 1/1 Running 3 118dkube-system kube-controller-manager-kmaster.example.com 1/1 Running 2 118dkube-system kube-proxy-7psvh 1/1 Running 2 118dkube-system kube-proxy-mf4hx 1/1 Running 2 118dkube-system kube-proxy-ndnk6 1/1 Running 2 118dkube-system kube-scheduler-kmaster.example.com 1/1 Running 2 118d[vagrant@kmaster ~]$
This issue is shown in my test Kubernetes cluster and while checking the kube-controller-manager.yaml and kube-scheduler.yaml 0 is the default port number used. So I have commented on that line and fixed the issue.
vi /etc/kubernetes/manifests/kube-controller-manager.yaml
- --leader-elect=true
- --node-cidr-mask-size=24
# - --port=0
- --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt
vi /etc/kubernetes/manifests/kube-scheduler.yaml
- --kubeconfig=/etc/kubernetes/scheduler.conf
- --leader-elect=true
# - --port=0
image: k8s.gcr.io/kube-scheduler:v1.19.4
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 8
@kmaster vagrant]# service kubelet restart
@kmaster ~]$ kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-0 Healthy {"health":"true"}
As of now 12-17-2020 K8S V1.20 - Kubelet start showing a warning message1.21 - will also show the same warning message1.22 - will also show the same warning message1.23 - dockershim will remove
Master : curl -sfL https://get.k3s.io | sh -
Worker : curl -sfL https://get.k3s.io | K3S_URL=https://myserver:6443 K3S_TOKEN=mynodetoken sh -
- You can install in Raspberry Pi Hardware
- By default, the data is keeping in SQLite no ETCD, But you can configure
- It is using Flannel network
- It is using Containerd not Docker
- Just needs Linux Kernel and Cgroup
root@testing:/home/ubuntu# docker pull minio/minioVELERO SETUP:
Using default tag: latest
latest: Pulling from minio/minio
4167d3e14976: Already exists
275c32df8f5e: Pull complete
cf0c84ce4772: Pull complete
70885164616a: Pull complete
Digest: sha256:6f8db3d7a1060cb1fcd6855791e9befe2d7f51644be65183680c1189eb196177
Status: Downloaded newer image for minio/minio:latest
root@testing:/home/ubuntu# docker run --name minio -p 9000:9000 -v data:/data minio/minio server /data
Endpoint: http://172.17.0.3:9000 http://127.0.0.1:9000
Browser Access:
http://172.17.0.3:9000 http://127.0.0.1:9000
Object API (Amazon S3 compatible):
Go: https://docs.min.io/docs/golang-client-quickstart-guide
Java: https://docs.min.io/docs/java-client-quickstart-guide
Python: https://docs.min.io/docs/python-client-quickstart-guide
JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide
.NET: https://docs.min.io/docs/dotnet-client-quickstart-guide
Detected default credentials 'minioadmin:minioadmin', please change the credentials immediately using 'MINIO_ACCESS_KEY' and 'MINIO_SECRET_KEY'
# cat <root@Aspire-A515-51G:> minio.credentials
> [default]
> aws_access_key_id=minioadmin
> aws_secret_access_key=minioadmin
> EOF
ajeesh@Aspire-A515-51G:~$ velero backup describe namespacenginx
Name: namespacenginx
Namespace: velero
Labels:
Annotations:
Phase: New
Namespaces:
Included: nginxtest
Excluded:
Resources:
Included: *
Excluded:
Cluster-scoped: auto
Label selector:
Storage Location:
Snapshot PVs: auto
TTL: 720h0m0s
Hooks:
Backup Format Version: 0
Started:
Completed:
Expiration:
Persistent Volumes:
ajeesh@Aspire-A515-51G:~$
# export ETCDCTL_API=3
# etcdctl --endpoints=https://127.0.0.1:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/healthcheck-client.crt --key=/etc/kubernetes/pki/etcd/healthcheck-client.key snapshot save etcd-snapshot-$(date +%Y-%m-%d_%H:%M:%S_%Z).db
{"level":"warn","ts":"2020-05-10T17:01:10.150Z","caller":"clientv3/retry_interceptor.go:116","msg":"retry stream intercept"}
Snapshot saved at etcd-snapshot-2020-05-10_17:01:10_UTC.db
#du -shc etcd-snapshot-2020-05-10_17:01:10_UTC.db
3.9M etcd-snapshot-2020-05-10_17:01:10_UTC.db
3.9M total
#
ajeesh@Aspire-A515-51G:~/Downloads/helm$ tar -zxvf helm-v3.0.0-linux-amd64.tar.gz
linux-amd64/
linux-amd64/helm
linux-amd64/README.md
linux-amd64/LICENSE
ajeesh@Aspire-A515-51G:~/Downloads/helm$ cd linux-amd64/
ajeesh@Aspire-A515-51G:~/Downloads/helm/linux-amd64$ ls
helm LICENSE README.md
ajeesh@Aspire-A515-51G:~/Downloads/helm/linux-amd64$ sudo mv helm /usr/local/bin/
ajeesh@Aspire-A515-51G:~/Downloads/helm/linux-amd64$ helm --help
The Kubernetes package manager
Common actions for Helm:
- helm search: search for charts
- helm pull: download a chart to your local directory to view
- helm install: upload the chart to Kubernetes
- helm list: list releases of charts
ajeesh@Aspire-A515-51G:~/Downloads/helm/linux-amd64$ helm version --short
v3.0.0+ge29ce2a
ajeesh@Aspire-A515-51G:~$ helm plugin install https://github.com/helm/helm-2to3Downloading and installing helm-2to3 v0.2.0 ...
https://github.com/helm/helm-2to3/releases/download/v0.2.0/helm-2to3_0.2.0_linux_amd64.tar.gz
Installed plugin: 2to3
ajeesh@Aspire-A515-51G:~$ helm plugin listNAME VERSION DESCRIPTION
2to3 0.2.0 migrate and cleanup Helm v2 configuration and releases in-place to Helm v3
ajeesh@Aspire-A515-51G:~$ helm 2to3 --helpMigrate and Cleanup Helm v2 configuration and releases in-place to Helm v3
helm 2to3 move
helm 2to3 convert jenkins
helm 2to3 convert wordpress
helm 2to3 cleanup : this will delete your tiller pods from your Kubernetes cluster.
ajeesh@Aspire-A515-51G:~$ helm repo add stable https://kubernetes-charts.storage.googleapis.com"stable" has been added to your repositories
ajeesh@Aspire-A515-51G:~$ helm repo listNAME URL
stable https://kubernetes-charts.storage.googleapis.com
ajeesh@Aspire-A515-51G:~$ helm search repo jenkins
NAME CHART VERSION APP VERSION DESCRIPTION
stable/jenkins 1.9.7
ajeesh@Aspire-A515-51G:~$ helm install myblog stable/wordpress
NAME: myblog
LAST DEPLOYED: Tue Dec 3 22:48:56 2019
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
1. Get the WordPress URL:
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
kmaster.example.com Ready master 10d v1.16.2 172.42.42.100CentOS Linux 7 (Core) 3.10.0-957.12.2.el7.x86_64 docker://19.3.4
kworker1.example.com Ready10d v1.16.2 172.42.42.101 CentOS Linux 7 (Core) 3.10.0-957.12.2.el7.x86_64 docker://19.3.4
kworker2.example.com Ready10d v1.16.2 172.42.42.102 CentOS Linux 7 (Core) 3.10.0-957.12.2.el7.x86_64 docker://19.3.4
kubectl apply -f https://raw.githubusercontent.com/google/metallb/v0.8.3/manifests/metallb.yaml2. cat metallb.yml
apiVersion: v1
kind: ConfigMap
metadata:
namespace: metallb-system
name: config
data:
config: |
address-pools:
- name: default
protocol: layer2
addresses:
- 172.42.42.110-172.42.42.120 --> Add your IP ranges
# apt-get install nfs-kernel-server
# mkdir -p /srv/nfs/kubedata
# chmod -R 777 /srv/nfs/
# cat /etc/exports
/srv/nfs/kubedata *(rw,sync,no_subtree_check,insecure)
# exportfs -rav
exporting *:/srv/nfs/kubedata
# exportfs -v
/srv/nfs/kubedata
(rw,wdelay,insecure,root_squash,no_subtree_check,sec=sys,rw,insecure,root_squash,no_all_squash)
# showmount -e
Export list for ubuntu-01:
/srv/nfs/kubedata *
Then you need to test the NFS mounting in all your k8s nodes.
# showmount -e 172.42.42.10
Export list for 172.42.42.10:
/srv/nfs/kubedata *
# mount -t nfs 172.42.42.10:/srv/nfs/kubedata /mnt
# mount | grep kubedata
172.42.42.10:/srv/nfs/kubedata on /mnt type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.42.42.101,local_lock=none,addr=172.42.42.10)
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv-nfs-manual
labels:
type: local
spec:
storageClassName: manual
capacity:
storage: 1Gi
accessModes:
- ReadWriteMany
nfs:
server: 172.42.42.10
path: "/srv/nfs/kubedata/nfs_manual"
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-nfs-manual
spec:
storageClassName: manual
accessModes:
- ReadWriteMany --> need to check
resources:
requests:
storage: 800Mi --> need check
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
persistentvolume/pv-nfs-manual 1Gi RWX Retain Bound default/pvc-nfs-manual manual 53m
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
persistentvolumeclaim/pvc-nfs-manual Bound pv-nfs-manual 1Gi RWX manual 53m
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
run: nginx
name: nginx-deploy
spec:
replicas: 1
selector:
matchLabels:
run: nginx
template:
metadata:
labels:
run: nginx
spec:
volumes:
- name: www --> this name should be same as Volumemounts name
persistentVolumeClaim:
claimName: pvc-nfs-manual
containers:
- image: nginx
name: nginx
volumeMounts:
- name: www --> need to be same as above name
mountPath: /usr/share/nginx/html
apiVersion: v1
kind: Service
metadata:
name: nginx
spec:
ports:
- name: http
port: 8080
protocol: TCP
targetPort: 80
selector:
app: nginx
type: LoadBalancer
NAME READY STATUS RESTARTS AGE
pod/nginx-deploy-f5bd4749b-nftg9 1/1 Running 0 51m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1443/TCP 10d
service/nginx LoadBalancer 10.103.153.86 172.42.42.110 8080:32012/TCP 11s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/nginx-deploy 1/1 1 1 51m
NAME DESIRED CURRENT READY AGE
replicaset.apps/nginx-deploy-f5bd4749b 1 1 1 51m
sudo apt-get update
sudo apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io
$ wget https://dl.google.com/go/go1.13.4.linux-amd64.tar.gz3. kubectl
$sudo tar -C /usr/local -xzf go1.13.4.linux-amd64.tar.gz
$ export PATH=$PATH:/usr/local/go/bin
$ go version
go version go1.13.4 linux/amd64
$ curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 44.5M 100 44.5M 0 0 1209k 0 0:00:37 0:00:37 --:--:-- 1182k
$ chmod +x ./kubectl
$ sudo mv ./kubectl /usr/local/bin/kubectl
$ GO111MODULE="on" go get sigs.k8s.io/kind@v0.5.1
go: finding sigs.k8s.io v0.5.1
$ rm go1.13.4.linux-amd64.tar.gz
$ export PATH=$PATH:/home/ajeesh/go/bin
$ kind version
v0.5.1
$ kind create cluster
Creating cluster "kind" ...
✓ Ensuring node image (kindest/node:v1.15.3) 🖼
✓ Preparing nodes 📦
✓ Creating kubeadm config 📜
✓ Starting control-plane 🕹️
✓ Installing CNI 🔌
✓ Installing StorageClass 💾
Cluster creation complete. You can now use the cluster with:
export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
kubectl cluster-info
$ export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
$ kind get kubeconfig-path
/home/ajeesh/.kube/kind-config-kind
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b52ee9180210 kindest/node:v1.15.3 "/usr/local/bin/entr…" 14 minutes ago Up 13 minutes 35507/tcp, 127.0.0.1:35507->6443/tcp kind-control-plane
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
kind-control-plane Ready master 17m v1.15.3
$ kind delete cluster$ docker ps
Deleting cluster "kind" ...
$KUBECONFIG is still set to use /home/ajeesh/.kube/kind-config-kind even though that file has been deleted, remember to unset it
$ unset KUBECONFIG
This will delete the kubeconfig file on your .kube folder.
/.kube$ ls
cache http-cache
$ cat multi-node-kind.yml
kind: Cluster
apiVersion: kind.sigs.k8s.io/v1alpha3
nodes:
- role: control-plane
- role: control-plane
- role: control-plane
- role: worker
- role: worker
- role: worker
~$ kind create cluster --config multi-node-kind.yml
Creating cluster "kind" ...
✓ Ensuring node image (kindest/node:v1.15.3) 🖼
✓ Preparing nodes 📦📦📦📦📦
✓ Configuring the external load balancer ⚖️
✓ Creating kubeadm config 📜
✓ Starting control-plane 🕹️
✓ Installing CNI 🔌
✓ Installing StorageClass 💾
✓ Joining more control-plane nodes 🎮
✓ Joining worker nodes 🚜
Cluster creation complete. You can now use the cluster with:
export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
kubectl cluster-info
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
kind-control-plane Ready master 2m20s v1.15.3
kind-control-plane2 Ready master 106s v1.15.3
kind-worker Ready46s v1.15.3
:~$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a0e52dd3effa kindest/node:v1.15.3 "/usr/local/bin/entr…" 4 minutes ago Up 3 minutes kind-worker
2a6c8833c3cb kindest/node:v1.15.3 "/usr/local/bin/entr…" 4 minutes ago Up 3 minutes 35213/tcp, 127.0.0.1:35213->6443/tcp kind-control-plane2
4e38366ad4a7 kindest/haproxy:2.0.0-alpine "/docker-entrypoint.…" 4 minutes ago Up 4 minutes 37331/tcp, 127.0.0.1:37331->6443/tcp kind-external-load-balancer
8a0ce1959722 kindest/node:v1.15.3 "/usr/local/bin/entr…" 4 minutes ago Up 3 minutes 36145/tcp, 127.0.0.1:36145->6443/tcp kind-control-plane
:~$ kind get nodes
kind-worker
kind-control-plane2
kind-external-load-balancer
kind-control-plane
~$ kubectl -n kube-system get all
NAME READY STATUS RESTARTS AGE
pod/coredns-5c98db65d4-hmrxc 1/1 Running 0 4m31s
pod/coredns-5c98db65d4-vgj9w 1/1 Running 0 4m31s
pod/etcd-kind-control-plane 1/1 Running 0 3m36s
pod/etcd-kind-control-plane2 1/1 Running 0 4m12s
pod/kindnet-7754r 1/1 Running 1 4m13s
pod/kindnet-9c4rt 1/1 Running 1 4m31s
pod/kindnet-b2td4 1/1 Running 1 3m13s
pod/kube-apiserver-kind-control-plane 1/1 Running 0 3m36s
pod/kube-apiserver-kind-control-plane2 1/1 Running 0 4m12s
pod/kube-controller-manager-kind-control-plane 1/1 Running 1 3m58s
pod/kube-controller-manager-kind-control-plane2 1/1 Running 0 3m58s
pod/kube-proxy-c628w 1/1 Running 0 4m13s
pod/kube-proxy-p9787 1/1 Running 0 4m31s
pod/kube-proxy-zf6pm 1/1 Running 0 3m13s
pod/kube-scheduler-kind-control-plane 1/1 Running 1 3m58s
pod/kube-scheduler-kind-control-plane2 1/1 Running 0 4m12s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kube-dns ClusterIP 10.96.0.1053/UDP,53/TCP,9153/TCP 4m46s
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/kindnet 3 3 3 3 34m43s
daemonset.apps/kube-proxy 3 3 3 3 3 beta.kubernetes.io/os=linux 4m45s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/coredns 2/2 2 2 4m46s
NAME DESIRED CURRENT READY AGE
replicaset.apps/coredns-5c98db65d4 2 2 2 4m31s
