{"id":18133,"date":"2020-07-17T09:09:00","date_gmt":"2020-07-17T06:09:00","guid":{"rendered":"https:\/\/fatihboy.com\/?p=18133"},"modified":"2020-07-17T09:09:00","modified_gmt":"2020-07-17T06:09:00","slug":"rancher-kubernetes-engine-rke-kubernetes-kurulumu","status":"publish","type":"post","link":"https:\/\/fatihboy.com\/en\/rancher-kubernetes-engine-rke-kubernetes-kurulumu\/","title":{"rendered":"Rancher Kubernetes Engine (RKE) ile Kubernetes Kurulumu"},"content":{"rendered":"

Rancher Kubernetes Engine<\/strong> (RKE) tamamen Docker \u00fczerinde \u00e7al\u0131\u015fan ve CNCF sertifikal\u0131 bir Kubernetes da\u011f\u0131t\u0131m\u0131d\u0131r. Rancher Kubernetes Engine’in sadece Docker ba\u011f\u0131ml\u0131l\u0131\u011f\u0131na sahip olmas\u0131, h\u0131zl\u0131ca y\u00f6netilebilir bir Kubernetes Cluster’\u0131na sahip olma a\u00e7\u0131s\u0131ndan \u00f6nemli bir avantaj sa\u011flamakta. Bu yaz\u0131m\u0131zda Rancher Kubernetes Engine yard\u0131m\u0131yla bir Kubernetes Cluster’\u0131n\u0131 nas\u0131l olu\u015fturabilece\u011finizi bulabilirsiniz.<\/p>\n\n\n\n

\u00d6n Gereksinim<\/strong><\/h2>\n\n\n\n

Rancher Kubernetes Engine, Kubernetes gerekli olan Cluster bile\u015fenlerini Linux da\u011f\u0131t\u0131mlar\u0131nda docker \u00fczerinde aya\u011fa kald\u0131rmaktad\u0131r. Dolay\u0131s\u0131yla \u00fczerinde Docker \u00e7al\u0131\u015fan herhangi bir Linux da\u011f\u0131t\u0131m\u0131 \u00fczerine kurulabilir. A\u015fa\u011f\u0131daki ad\u0131mlar\u0131 takip ederek kurulumu ve \u00e7al\u0131\u015fmas\u0131 i\u00e7in \u00f6n gereksinimleri kurabilirsiniz.<\/p>\n\n\n\n

Yerel Kullan\u0131c\u0131<\/h3>\n\n\n\n

\u00d6ncelikle t\u00fcm node\u2019larda kullan\u0131c\u0131 olu\u015fturulmal\u0131d\u0131r. Bunun i\u00e7in a\u015fa\u011f\u0131daki komut her bir Kubernetes Cluster \u00fcyesi node’da \u00e7al\u0131\u015ft\u0131r\u0131l\u0131r;<\/p>\n\n\n\n

useradd [KULLANICI_ADI]\npasswd [KULLANICI_ADI]<\/pre>\n\n\n\n
Swap Kullan\u0131m\u0131<\/strong><\/h3>\n\n\n\n
K\u00fcme \u00fcyesi Worker Node\u2019larda swap kullan\u0131m\u0131 kapat\u0131lmal\u0131d\u0131r. A\u015fa\u011f\u0131daki komutlar sunucularda swap kullan\u0131m\u0131 kapat\u0131l\u0131r;<\/p>\n\n\n\n
swapoff -a\nvi \/etc\/fstab<\/pre>\n\n\n\n
a\u00e7\u0131lan ekranda swap sat\u0131r\u0131 # ile comment edilir;<\/p>\n\n\n\n
\"\"
\/etc\/fstab dosyas\u0131 a\u00e7\u0131larak swap tan\u0131m\u0131 kapat\u0131l\u0131r<\/figcaption><\/figure>\n\n\n\n
Docker Kurulumu<\/h3>\n\n\n\n
Rancher taraf\u0131ndan haz\u0131rlanan docker kurulum beti\u011fi i\u015fletim sistemine uygun Docker kurulumunu ger\u00e7ekle\u015ftirecektir. Bu betik a\u015fa\u011f\u0131daki komutla indirilerek \u00e7al\u0131\u015ft\u0131r\u0131labilir;<\/p>\n\n\n\n
curl https:\/\/releases.rancher.com\/install-docker\/18.09.sh | sh<\/pre>\n\n\n\n
\u00d6nceki ad\u0131mlarda olu\u015fturdu\u011fumuz kullan\u0131c\u0131 Docker \u00fczerinde de i\u015flemler yapaca\u011f\u0131 i\u00e7in docker kullan\u0131c\u0131 grubuna \u00fcye olmal\u0131d\u0131r.<\/p>\n\n\n\n
usermod -aG docker [KULLANICI_ADI]<\/pre>\n\n\n\n
SSH Yap\u0131land\u0131rmas\u0131<\/h3>\n\n\n\n
Rancher Kubernetes Engine’in otomatik kurulum yapabilmesi i\u00e7in kurulum yap\u0131lacak sunuculara \u015fifresiz ssh eri\u015fimi olmal\u0131d\u0131r. A\u015fa\u011f\u0131daki komutu kullanarak \u00f6ncelikle bir ssh anahtar\u0131 olu\u015fturulur. Bu komut kurulumu y\u00f6netecek makinede (genellikle yerel makinede<\/em>) \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n\n\n\n
ssh-keygen -q -f ~\/.ssh\/id_rsa -N \"\"<\/pre>\n\n\n\n
Bu anahtar\u0131 kurulum yap\u0131lan sunucular\u0131n tan\u0131mas\u0131 ve bu anahtarla giri\u015fe izin vermeleri gereklidir. Bunun i\u00e7in yine ayn\u0131 makinede a\u015fa\u011f\u0131daki komutla ssh anahtar\u0131 t\u00fcm node’lara kopyalan\u0131r;<\/p>\n\n\n\n
ssh-copy-id [KULLANICI_ADI]@[SUNUCU_IP]<\/pre>\n\n\n\n
Yukar\u0131daki komut kurulum yap\u0131lacak her bir sunucu bilgileri ile \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r. Node 22\u2019den farkl\u0131 bir port \u00fczerinden ssh hizmeti veriyorsa bu komut a\u015fa\u011f\u0131daki \u015fekilde \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n\n\n\n
ssh-copy-id -p [SSH_PORTU] [KULLANICI_ADI]@[SUNUCU_IP]<\/pre>\n\n\n\n
Rancher Kubernetes Engine kurulum ve yap\u0131land\u0131rma s\u0131ras\u0131nda TCP forwarding kulland\u0131\u011f\u0131 i\u00e7in kurulum yap\u0131lacak cluster node\u2019lar\u0131nda \/etc\/ssh\/sshd_config<\/strong> dosyas\u0131nda a\u015fa\u011f\u0131daki girdinin oldu\u011funa emin olunmal\u0131;<\/p>\n\n\n\n
AllowTcpForwarding yes<\/pre>\n\n\n\n
Rancher Kubernetes Engine Binary Kurulumu<\/strong><\/h2>\n\n\n\n
Yukar\u0131daki \u00f6n haz\u0131rl\u0131klar ard\u0131ndan g\u00fcncel Rancher Kubernetes Engine binary\u2019si https:\/\/github.com\/rancher\/rke\/releases<\/a> adresinden yerele indirilir. Linux bazl\u0131 sistemlerde dosya a\u015fa\u011f\u0131daki komutla \u00e7al\u0131\u015ft\u0131r\u0131labilir olarak i\u015faretlenir;<\/p>\n\n\n\n
chmod +x rke<\/pre>\n\n\n\n
\u0130ndirilen dosya path\u2019te tan\u0131ml\u0131 olan bir dizine kopyalan\u0131r.  \u00d6rne\u011fin Linux sistemlerde;<\/p>\n\n\n\n
sudo mv rke \/usr\/local\/bin<\/pre>\n\n\n\n
\u0130\u015flem a\u015fa\u011f\u0131daki komutla do\u011frulan\u0131r;<\/p>\n\n\n\n
rke --version<\/pre>\n\n\n\n
MacOS Alternatif kurulum<\/strong><\/h3>\n\n\n\n
HomeBrew<\/strong><\/h4>\n\n\n\n
MacOS sistemlerde yukar\u0131daki ad\u0131mlara alternatif olarak a\u015fa\u011f\u0131daki komut kullan\u0131larak homebrew yard\u0131m\u0131yla kurulum kolayl\u0131kla ger\u00e7ekle\u015ftirilebilir;<\/p>\n\n\n\n
brew install rke<\/pre>\n\n\n\n
Benzer \u015fekilde, mevcut bir kurulum a\u015fa\u011f\u0131daki komutla g\u00fcncellenebilir;<\/p>\n\n\n\n
brew upgrade rke<\/pre>\n\n\n\n
MacPorts<\/strong><\/h4>\n\n\n\n
MacOs sistemlerde homebrew kurulumuna alternatif olarak MacPorts\u2019da kullan\u0131labilir. MacPorts kurulu sistemde a\u015fa\u011f\u0131daki komut yard\u0131m\u0131yla Rancher Kubernetes Engine kurulabilir;<\/p>\n\n\n\n
port install rke<\/pre>\n\n\n\n
Yine homebrew\u2019a benzer \u015fekilde a\u015fa\u011f\u0131daki komutla mevcut bir RKE kurulumu g\u00fcncellenebilir;<\/p>\n\n\n\n
port upgrade rke<\/pre>\n\n\n\n
Cluster Yap\u0131land\u0131rma Dosyas\u0131<\/strong><\/h2>\n\n\n\n
Rancher Kubernetes Engine cluster yap\u0131land\u0131rmalar\u0131nda k\u00fcme sunucular\u0131n\u0131n hangileri oldu\u011fu ve Kubernetes\u2019in nas\u0131l kurulaca\u011f\u0131na dair bilgiler i\u00e7in cluster.yml<\/strong> ad\u0131yla bir yap\u0131land\u0131rma dosyas\u0131n\u0131 kullan\u0131r. A\u015fa\u011f\u0131daki tek node\u2019lu bir kurulum i\u00e7in en basit haliyle \u00f6rnek cluster.yml<\/strong> dosyas\u0131 bulunmakta;<\/p>\n\n\n\n
nodes:\n    - address: [NODE_IP]\n      user: [SSH_KULLANICI_ADI]\n      role:\n        - controlplane\n        - etcd\n        - worker<\/pre>\n\n\n\n
A\u015fa\u011f\u0131daki \u00f6rnekte ise t\u00fcm de\u011ferleri verilmi\u015f haliyle \u00f6rnek cluster.yml<\/strong> dosyas\u0131 bulunabilir;<\/p>\n\n\n\n
nodes:\n    - address: 1.1.1.1\n      user: ubuntu\n      role:\n        - controlplane\n        - etcd\n      ssh_key_path: \/home\/user\/.ssh\/id_rsa\n      port: 2222\n    - address: 2.2.2.2\n      user: ubuntu\n      role:\n        - worker\n      ssh_key: |-\n        -----BEGIN RSA PRIVATE KEY-----\n        -----END RSA PRIVATE KEY-----\n    - address: example.com\n      user: ubuntu\n      role:\n        - worker\n      hostname_override: node3\n      internal_address: 192.168.1.6\n      labels:\n        app: ingress\n# If set to true, RKE will not fail when unsupported Docker version\n# are found\nignore_docker_version: false\n# Cluster level SSH private key\n# Used if no ssh information is set for the node\nssh_key_path: ~\/.ssh\/test\n# Enable use of SSH agent to use SSH private keys with passphrase\n# This requires the environment `SSH_AUTH_SOCK` configured pointing\n#to your SSH agent which has the private key added\nssh_agent_auth: true\n# List of registry credentials\n# If you are using a Docker Hub registry, you can omit the `url`\n# or set it to `docker.io`\n# is_default set to `true` will override the system default\n# registry set in the global settings\nprivate_registries:\n     - url: registry.com\n       user: Username\n       password: password\n       is_default: true\n# Bastion\/Jump host configuration\nbastion_host:\n    address: x.x.x.x\n    user: ubuntu\n    port: 22\n    ssh_key_path: \/home\/user\/.ssh\/bastion_rsa\n# or\n#   ssh_key: |-\n#     -----BEGIN RSA PRIVATE KEY-----\n#\n#     -----END RSA PRIVATE KEY-----\n# Set the name of the Kubernetes cluster  \ncluster_name: mycluster\n# The Kubernetes version used. The default versions of Kubernetes\n# are tied to specific versions of the system images.\n#\n# For RKE v0.2.x and below, the map of Kubernetes versions and their system images is\n# located here:\n# https:\/\/github.com\/rancher\/types\/blob\/release\/v2.2\/apis\/management.cattle.io\/v3\/k8s_defaults.go\n#\n# For RKE v0.3.0 and above, the map of Kubernetes versions and their system images is\n# located here:\n# https:\/\/github.com\/rancher\/kontainer-driver-metadata\/blob\/master\/rke\/k8s_rke_system_images.go\n#\n# In case the kubernetes_version and kubernetes image in\n# system_images are defined, the system_images configuration\n# will take precedence over kubernetes_version.\nkubernetes_version: v1.10.3-rancher2\n# System Images are defaulted to a tag that is mapped to a specific\n# Kubernetes Version and not required in a cluster.yml. \n# Each individual system image can be specified if you want to use a different tag.\n#\n# For RKE v0.2.x and below, the map of Kubernetes versions and their system images is\n# located here:\n# https:\/\/github.com\/rancher\/types\/blob\/release\/v2.2\/apis\/management.cattle.io\/v3\/k8s_defaults.go\n#\n# For RKE v0.3.0 and above, the map of Kubernetes versions and their system images is\n# located here:\n# https:\/\/github.com\/rancher\/kontainer-driver-metadata\/blob\/master\/rke\/k8s_rke_system_images.go\n#\nsystem_images:\n    kubernetes: rancher\/hyperkube:v1.10.3-rancher2\n    etcd: rancher\/coreos-etcd:v3.1.12\n    alpine: rancher\/rke-tools:v0.1.9\n    nginx_proxy: rancher\/rke-tools:v0.1.9\n    cert_downloader: rancher\/rke-tools:v0.1.9\n    kubernetes_services_sidecar: rancher\/rke-tools:v0.1.9\n    kubedns: rancher\/k8s-dns-kube-dns-amd64:1.14.8\n    dnsmasq: rancher\/k8s-dns-dnsmasq-nanny-amd64:1.14.8\n    kubedns_sidecar: rancher\/k8s-dns-sidecar-amd64:1.14.8\n    kubedns_autoscaler: rancher\/cluster-proportional-autoscaler-amd64:1.0.0\n    pod_infra_container: rancher\/pause-amd64:3.1\nservices:\n    etcd:\n      # if external etcd is used\n      # path: \/etcdcluster\n      # external_urls:\n      #   - https:\/\/etcd-example.com:2379\n      # ca_cert: |-\n      #   -----BEGIN CERTIFICATE-----\n      #   xxxxxxxxxx\n      #   -----END CERTIFICATE-----\n      # cert: |-\n      #   -----BEGIN CERTIFICATE-----\n      #   xxxxxxxxxx\n      #   -----END CERTIFICATE-----\n      # key: |-\n      #   -----BEGIN PRIVATE KEY-----\n      #   xxxxxxxxxx\n      #   -----END PRIVATE KEY-----\n    # Note for Rancher v2.0.5 and v2.0.6 users: If you are configuring\n    # Cluster Options using a Config File when creating Rancher Launched\n    # Kubernetes, the names of services should contain underscores\n    # only: `kube_api`.\n    kube-api:\n      # IP range for any services created on Kubernetes\n      # This must match the service_cluster_ip_range in kube-controller\n      service_cluster_ip_range: 10.43.0.0\/16\n      # Expose a different port range for NodePort services\n      service_node_port_range: 30000-32767    \n      pod_security_policy: false\n      # Add additional arguments to the kubernetes API server\n      # This WILL OVERRIDE any existing defaults\n      extra_args:\n        # Enable audit log to stdout\n        audit-log-path: \"-\"\n        # Increase number of delete workers\n        delete-collection-workers: 3\n        # Set the level of log output to debug-level\n        v: 4\n    # Note for Rancher 2 users: If you are configuring Cluster Options\n    # using a Config File when creating Rancher Launched Kubernetes,\n    # the names of services should contain underscores only:\n    # `kube_controller`. This only applies to Rancher v2.0.5 and v2.0.6.\n    kube-controller:\n      # CIDR pool used to assign IP addresses to pods in the cluster\n      cluster_cidr: 10.42.0.0\/16\n      # IP range for any services created on Kubernetes\n      # This must match the service_cluster_ip_range in kube-api\n      service_cluster_ip_range: 10.43.0.0\/16\n    kubelet:\n      # Base domain for the cluster\n      cluster_domain: cluster.local\n      # IP address for the DNS service endpoint\n      cluster_dns_server: 10.43.0.10\n      # Fail if swap is on\n      fail_swap_on: false\n      # Set max pods to 250 instead of default 110\n      extra_args:\n        max-pods: 250\n      # Optionally define additional volume binds to a service\n      extra_binds:\n        - \"\/usr\/libexec\/kubernetes\/kubelet-plugins:\/usr\/libexec\/kubernetes\/kubelet-plugins\"\n# Currently, only authentication strategy supported is x509.\n# You can optionally create additional SANs (hostnames or IPs) to\n# add to the API server PKI certificate.\n# This is useful if you want to use a load balancer for the\n# control plane servers.\nauthentication:\n    strategy: x509\n    sans:\n      - \"10.18.160.10\"\n      - \"my-loadbalancer-1234567890.us-west-2.elb.amazonaws.com\"\n# Kubernetes Authorization mode\n# Use `mode: rbac` to enable RBAC\n# Use `mode: none` to disable authorization\nauthorization:\n    mode: rbac\n# If you want to set a Kubernetes cloud provider, you specify\n# the name and configuration\ncloud_provider:\n    name: aws\n# Add-ons are deployed using kubernetes jobs. RKE will give\n# up on trying to get the job status after this timeout in seconds..\naddon_job_timeout: 30\n# Specify network plugin-in (canal, calico, flannel, weave, or none)\nnetwork:\n    plugin: canal\n# Specify DNS provider (coredns or kube-dns)\ndns:\n    provider: coredns\n# Currently only nginx ingress provider is supported.\n# To disable ingress controller, set `provider: none`\n# `node_selector` controls ingress placement and is optional\ningress:\n    provider: nginx\n    node_selector:\n      app: ingress\n      \n# All add-on manifests MUST specify a namespace\naddons: |-\n    ---\n    apiVersion: v1\n    kind: Pod\n    metadata:\n      name: my-nginx\n      namespace: default\n    spec:\n      containers:\n      - name: my-nginx\n        image: nginx\n        ports:\n        - containerPort: 80\naddons_include:\n    - https:\/\/raw.githubusercontent.com\/rook\/rook\/master\/cluster\/examples\/kubernetes\/rook-operator.yaml\n    - https:\/\/raw.githubusercontent.com\/rook\/rook\/master\/cluster\/examples\/kubernetes\/rook-cluster.yaml\n    - \/path\/to\/manifest<\/pre>\n\n\n\n
Cluster.yml dosyas\u0131nda kullan\u0131labilecek t\u00fcm de\u011ferler i\u00e7in https:\/\/rancher.com\/docs\/rke\/latest\/en\/config-options\/<\/a> adresindeki dok\u00fcmantasyon incelenebilir.<\/p>\n\n\n\n
Cluster.yml dosyas\u0131 i\u00e7in alternatif bir yolda rke uygulamas\u0131n\u0131 kullanmakt\u0131r. Varsay\u0131lan de\u011ferlerle  bo\u015f bir cluster.yml dosyas\u0131 olu\u015fturmak isterseniz a\u015fa\u011f\u0131daki komutu kullanabilirsiniz;<\/p>\n\n\n\n
rke config --empty --name cluster.yml<\/pre>\n\n\n\n
Daha basit ve y\u00f6nlendirici olan bu bir di\u011fer y\u00f6ntemde rke config<\/strong> komutu ile size sorulan sorulara yan\u0131t verilir. Verilen yan\u0131tlar do\u011frultusunda cluster.yml dosyas\u0131 otomatik olarak olu\u015fturulur.<\/p>\n\n\n\n
rke config --name cluster.yml<\/pre>\n\n\n\n
Y\u00fcksek eri\u015filebilirlik i\u00e7in birden fazla node\u2019a controlplane<\/strong> rol\u00fc atayabilirsiniz. Rancher Kubernetes Engine controlplane rol\u00fcne sahip t\u00fcm node\u2019lara Kubernetes\u2019in master bile\u015fenlerini yerle\u015ftirecektir. Kurulumu yap\u0131lan kubelet\u2019ler ba\u011flant\u0131 adresi olarak 127.0.0.1:6443<\/strong> olacak \u015fekilde yap\u0131land\u0131r\u0131lacaklard\u0131r. Bu adres node \u00fczerinde kurulan nginx-proxy<\/strong> taraf\u0131ndan kar\u015f\u0131lanacakt\u0131r. nginx-proxy kar\u015f\u0131lad\u0131\u011f\u0131 talebi t\u00fcm master node\u2019lara da\u011f\u0131tacak \u015fekilde yap\u0131land\u0131r\u0131lm\u0131\u015ft\u0131r.<\/p>\n\n\n\n
cluster.yml<\/strong> dosyas\u0131n\u0131n haz\u0131rlanmas\u0131 ard\u0131ndan bu dosyayla ayn\u0131 dizinde a\u015fa\u011f\u0131daki komut \u00e7al\u0131\u015ft\u0131r\u0131larak Kubernetes cluster\u2019\u0131 kurularak yap\u0131land\u0131r\u0131l\u0131r;<\/p>\n\n\n\n
rke up<\/pre>\n\n\n\n
\u0130\u015flemlerin ba\u015far\u0131yla tamamlanmas\u0131 ard\u0131nda kubeconfig bilgileri kube_config_cluster.yml<\/strong> i\u00e7erisine saklanacakt\u0131r.<\/p>\n\n\n\n
A\u015fa\u011f\u0131daki komut yard\u0131m\u0131yla olu\u015fturulan Kubernetes Cluster\u2019\u0131na ba\u011flanmak i\u00e7in gerekli yap\u0131land\u0131rmay\u0131 kube config dosyas\u0131na ekleyebilirsiniz;<\/p>\n\n\n\n
KUBECONFIG=~\/.kube\/config:.\/kube_config_cluster.yml kubectl config view --merge --flatten > ~\/.kube\/config<\/pre>\n\n\n\n
Bak\u0131m, problem \u00e7\u00f6z\u00fcm\u00fc ve y\u00fckseltme i\u015flemleri i\u00e7in a\u015fa\u011f\u0131daki dosyalar\u0131n saklanmas\u0131 gerekmektedir;<\/p>\n\n\n\n