Architect Developer Advocate/Technical Evangelist Infrastructure Engineer Frontend Engineer Community Music,Live,FES !! Take a picture !! https://www.flickr.com/photos/cyberblack ISBN-10: 4798155373 ISBN-13: 978-4798155371 I wrote the Chapter 6 Rancher 2.0 part. Release on March 15,2018 #rancherjp #kujiraya #deepcn
New regions, more features, increased productivity by Microsoft Azure Blog 2018.6.13 • 「Microsoft Build 2018」にて「Azure Container Service」から「Azure Kubernetes Service」と改名 • オーストラリア東部、英国南部、米国西部、米国西部2、北ヨーロッパの各 リージョンで利用可能。今後数カ月以内に10のリージョンでの追加展開が 予定
Cloud Next ’18 by Publickey 2018.7.25 • ユーザのオンプレミス環境にGKE(Google Kubernetes Engine)と同等の Kubernetes環境を構築できる。 • Google Cloud ConsoleでオンプレミスのKubernetesクラスタの管理が可能 • Google Cloud Platform MarketplaceのKubernetes対応アプリの配布も対応
Runtime kubeletから操作され、イメージの取得とコンテナーの実行を行います。Kubernetesはコンテナーランタイムの取 替が可能なため、Docker、containerd、rkt、cri-oなどのコンテナーランタイムを利用できます。 Kube-proxy 各Nodeで動作する、Serviceオブジェクトが持つCluster IPを転送するためのネットワークProxyです。デフォル トではiptablesが利用されます。 Master Kube-proxy Container Runtime Kubelet Node 1,2,3,n Pod Image Registry Pod Pod Pod Pod Pod Pod Pod Pod
Docker Darren Shepherd Co-founder and Chief Architect at Rancher Labs, Inc. @ibuildthecloud https://github.com/rancher/rio https://www.slideshare.net/cyberblackvoom/whats-rio-112779732 Rioの資料はこちら!!
(64-bit) Memory: 4GB • 1.12.6 • 1.13.1 • 17.03.2 Red Hat Enterprise Linux 7.5 (64-bit) RancherOS 1.3.0 (64-bit) Step 2: Start the server $ sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher Web Access!! https://<server_ip> Step 1: Prepare a Linux Host
apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook/all-in-one/guestbook-all-in-one.yaml service "redis-master" created deployment.apps "redis-master" created service "redis-slave" created deployment.apps "redis-slave" created service "frontend" created deployment.apps "frontend" created 2.デプロイの確認 > kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE frontend ClusterIP 10.43.161.216 <none> 80/TCP 24s kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 1h redis-master ClusterIP 10.43.169.190 <none> 6379/TCP 24s redis-slave ClusterIP 10.43.85.124 <none> 6379/TCP 24s
metadata: name: redis-slave labels: app: redis tier: backend role: slave spec: ports: - port: 6379 selector: app: redis tier: backend role: slave --- apiVersion: apps/v1 # for k8s versions before 1.9.0 use apps/v1beta2 and before 1.8.0 use extensions/v1beta1 kind: Deployment metadata: name: redis-slave spec: selector: matchLabels: app: redis role: slave tier: backend replicas: 2 template: metadata: labels: app: redis role: slave tier: backend spec: containers: - name: slave image: gcr.io/google_samples/gb-redisslave:v1 resources: requests: cpu: 100m memory: 100Mi env: - name: GET_HOSTS_FROM value: dns # If your cluster config does not include a dns service, then to # instead access an environment variable to find the master # service's host, comment out the 'value: dns' line above, and # uncomment the line below: # value: env ports: - containerPort: 6379 ---
metadata: name: frontend labels: app: guestbook tier: frontend spec: # if your cluster supports it, uncomment the following to automatically create # an external load-balanced IP for the frontend service. # type: LoadBalancer ports: - port: 80 selector: app: guestbook tier: frontend --- apiVersion: apps/v1 # for k8s versions before 1.9.0 use apps/v1beta2 and before 1.8.0 use extensions/v1beta1 kind: Deployment metadata: name: frontend spec: selector: matchLabels: app: guestbook tier: frontend replicas: 3 template: metadata: labels: app: guestbook tier: frontend spec: containers: - name: php-redis image: gcr.io/google-samples/gb-frontend:v4 resources: requests: cpu: 100m memory: 100Mi env: - name: GET_HOSTS_FROM value: dns # If your cluster config does not include a dns service, then to # instead access environment variables to find service host # info, comment out the 'value: dns' line above, and uncomment the # line below: # value: env ports: - containerPort: 80