Install kubernetes oracle linux

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

To mannually install Kubernetes in Oracle OCI via Oracle Released Docker and Kubernetes version

HenryXie1/How-To-Manually-Install-Kubernetes-for-Oracle-Linux-in-Oracle-OCI

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

How To Manually Install Kubernetes for Oracle Linux in Oracle OCI

To mannually install Kubernetes in Oracle OCI via Oracle Released Docker and Kubernetes version from Oracle Container Registry Refer official doc

Please turn off TX checksum offload if you have VM in OCI with UEK4 kernel and Broadcomm driver. Refer doc

Preparation(All Kubernetes Nodes) (set http proxy if necessary in intranet):

• Assume Master nodes and worker nodes are in the same VCN. Otherwise we need to add access rules in OCI policy to let nodes communicate with each other. details in doc
• #yum update -y
• #yum-config-manager —enable ol7_addons
• #yum install docker-engine
• Add proxy for docker daemon and docker containers if necessary in intranet. refer my blog
• Move Docker Images OS Files From Default To Different OS Location for space concern. refer my blog
• #systemctl enable docker
• #systemctl start docker
• #docker login container-registry.oracle.com/kubernetes_developer . We can get free account from Oracle Container Registry
• #iptables -P FORWARD ACCEPT
• #firewall-cmd —add-masquerade —permanent
• #firewall-cmd —add-port=10250/tcp —permanent
• #firewall-cmd —add-port=8472/udp —permanent
• On Master Node only: # firewall-cmd —add-port=6443/tcp —permanent
• #systemctl restart firewalld
• #/usr/sbin/setenforce 0
• #vim /etc/selinux/config and set SELINUX=permissive

• #yum install kubeadm
• #export KUBE_REPO_PREFIX=container-registry.oracle.com/kubernetes_developer
• #kubeadm-setup.sh up

_.
Please wait .
— 75% completed
Waiting for the control plane to become ready .
.
100% completed
.
[===> PLEASE DO THE FOLLOWING STEPS BELOW: Your Kubernetes master has initialized successfully!
To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$ (id -g) $HOME/.kube/config

You can now join any number of machines by running the following on each node
as root:
export KUBE_REPO_PREFIX=container-registry.oracle.com/kubernetes_developer && kubeadm-setup.sh join 100.106.146.3:6443 —token ********** —discovery-token-ca-cert-hash sha256:****************

_

• groupadd k8sgroup; useradd -G k8ggroup k8suser ;
• visudo — to add «k8suser ALL=(ALL) ALL» below «root ALL=(ALL) ALL»
• su — k8suser
• mkdir -p $HOME/.kub
• sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
• sudo chown $(id -u):$ (id -g) $HOME/.kube/config
• echo ‘export KUBECONFIG=$HOME/.kube/config’ >> $HOME/.bashrc
• use this command to verify: $ kubectl get pods -n kube-system, output would be like

[k8suser@instance-cas-mt2 .kube]$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
etcd-instance-cas-mt2 1/1 Running 0 2h
kube-apiserver-instance-cas-mt2 1/1 Running 1 2h
kube-controller-manager-instance-cas-mt2 1/1 Running 0 2h
kube-dns-5c57c4787c-xzsgz 3/3 Running 0 2h
kube-flannel-ds-87xb9 1/1 Running 0 2h
kube-proxy-mwn46 1/1 Running 0 2h
kube-scheduler-instance-cas-mt2 1/1 Running 0 2h
kubernetes-dashboard-7df769d745-m4mgx 1/1 Running 0 2h

• #yum install kubeadm
• export KUBE_REPO_PREFIX=container-registry.oracle.com/kubernetes_developer && kubeadm-setup.sh join 100.106.146.3:6443 —token ******* —discovery-token-ca-cert-hash sha256:*********
• In the master node ,use kubeadm token list or kubeadm token create to get token
• In the master node, use below to get SHA256 CA certificate

# openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/^.* //' 

_Checking if env is ready .
Checking whether docker can pull busybox image .
Checking access to container-registry.oracle.com/kubernetes_developer .
Trying to pull repository container-registry.oracle.com/kubernetes_developer/kube-proxy-amd64 .
v1.10.5: Pulling from container-registry.oracle.com/kubernetes_developer/kube-proxy-amd64
Digest: sha256:*****
Status: Image is up to date for container-registry.oracle.com/ku bernetes_developer/kube-proxy-amd64:v1.10.5
Checking whether docker can run container .
Checking firewalld settings .
Checking iptables default rule .
Checking br_netfilter module .
Checking sysctl variables .
Enabling kubelet .
Created symlink from /etc/systemd/system/multi-user.target.wants /kubelet.service to /etc/systemd/system/kubelet.service.
Check successful, ready to run ‘join’ command .
[preflight] Running pre-flight checks.
[validation] WARNING: kubeadm doesn’t fully support multiple API Servers yet
[discovery] Trying to connect to API Server «100.106.146.3:6443»
[discovery] Trying to connect to API Server «100.106.146.3:6443»
[discovery] Created cluster-info discovery client, requesting info from «https://100.106.146.3:6443»
[discovery] Created cluster-info discovery client, requesting info from «https://100.106.146.3:6443»
[discovery] Requesting info from «https://100.106.146.3:6443» again to validate TLS against the pinned public key
[discovery] Requesting info from «https://100.106.146.3:6443» again to validate TLS against the pinned public key
[discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server «100.106.146.3:6443»
[discovery] Successfully established connection with API Server «100.106.146.3:6443»
[discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server «100.106.146.3:6443»
[discovery] Successfully established connection with API Server «100.106.146.3:6443»
This node has joined the cluster:

• Certificate signing request was sent to master and a response was received.
• The Kubelet was informed of the new secure connection details.
  Run ‘kubectl get nodes’ on the master to see this node join the cluster._
• kubectl get nodes

NAME STATUS ROLES AGE VERSION
instance-test-db2 Ready 5m v1.10.5+2.0.2.el7
instance-test-mt2 Ready master 3h v1.10.5+2.0.2.el7

• admin.conf controller-manager.conf kubelet.conf scheduler.conf plus pki and other manifests files can be found in host /etc/kubernetes/

Источник