AKS on Azure Stack HCI/Windows Serverの準備と監視 _ Preparing and monitoring AKS on...Norio Sashizaki
準備
- ウィルス対策における、AKS on Azure Stack HCI/Windows Server の除外パス
- Kubernetes クラスターの追加準備 – AD との SSO
- Get-AksHciCredential と kubectl.exe
監視
Kubernetes クラスターのリソース確認
- サービス アカウント ベアラー トークン/サービス アカウント トークン認証 で Azure Arc の Kubernetes クラスター を確認
- AKS on Azure Stack HCI/Kubernetes クラスターのモニター
- AKS on Azure Stack HCI 内でログを表示して、データを収集、確認する
AKS on Azure Stack HCI/Windows Server のアップグレード
まとめ
参考資料
---
Preparation
- Exclusion path for AKS on Azure Stack HCI/Windows Server in antivirus
- Prepare to add Kubernetes cluster - SSO with AD
- Get-AksHciCredential and kubectl.exe
Monitoring
Check Kubernetes cluster resources
- Check Kubernetes cluster in Azure Arc with Service Account Bearer Token / Service Account Token Authentication
- Monitor AKS on Azure Stack HCI/Kubernetes clusters
- View logs, collect and review data within AKS on Azure Stack HCI
Upgrade AKS on Azure Stack HCI/Windows Server
Summary
Reference material
The document provides an overview of Kubernetes and Rancher through a presentation given at a Rancher Meetup. It includes:
1. An introduction to market trends in Kubernetes adoption by major cloud providers.
2. An overview of Kubernetes architecture and components.
3. An introduction to Rancher and how it differs from previous versions in using Kubernetes as its core architecture.
4. Details on running a hands-on demo of deploying Kubernetes clusters and applications using Rancher.
The document provides a summary of KubeCon + CloudNativeCon China 2018 including key details such as the number of attendees, certified partners, and growth of cloud native adoption in China. It also outlines upcoming Rancher and Kubernetes events in China and findings from a survey investigating Kubernetes meetups in China.
KubeCon + CloudNativeCon China 2018 was held in Shanghai from November 13-15 with 2,500 attendees. There was a focus on cloud native projects from China and growth in certified Kubernetes and cloud native partners in China. A Service Mesh Enterprise Summit was co-hosted by Rancher Labs and Huawei in November 2018 to discuss enterprise adoption of Kubernetes and service meshes. Rancher continues to gain popularity in China for easily managing Kubernetes clusters.
Rio is a new open source project from Rancher Labs that aims to provide a simple, fun, and end-to-end container experience. Rio includes built-in technologies like Kubernetes, Istio, and Containerd so that users do not need to be experts in installing and managing these systems. The document provides an overview of Rio's concepts and components, demonstrates how to install and use Rio in standalone mode, and shows how to deploy and manage services using Rio's built-in service mesh capabilities.
Rancher v2.1.0 includes several new features such as improved support for Kubernetes clusters on Windows nodes in an experimental capacity, upgrades to Rancher High Availability, and support for Kubernetes 1.12. The document also advertises an upcoming webinar on migrating from Rancher 1.6 to 2.1 and provides information about an upcoming Japan Container Days conference in December 2018.
Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. Rancher is a container management platform that makes it easy to deploy and manage Kubernetes. This document provides an overview of Kubernetes and Rancher, demonstrates how to deploy a Kubernetes cluster using Rancher, and walks through running a sample Guestbook application on the cluster. It also discusses trends in adoption of Kubernetes by major cloud providers and how Rancher 2.0 simplifies cluster creation and management.
Rio is a new project from Rancher Labs that aims to provide a simple, end-to-end container experience. Rio includes built-in technologies like Kubernetes, Istio and Containerd to make deploying and running containers and services easy without needing expertise in those systems. The document discusses getting started with Rio, including downloading and installing Rio, running it in standalone mode or connecting to an existing Kubernetes cluster. It also demonstrates basic Rio commands and using the built-in service mesh to stage a new version of a service.
Rancher Server was used to deploy Rancher Kubernetes Engine (RKE) nodes and Google Kubernetes Engine (GKE) nodes. Etcd was used for distributed key-value storage. Various networking, storage, and security configurations were applied across the heterogeneous Kubernetes clusters. Monitoring and logging were established to observe cluster health and troubleshoot issues.
6. Recently kubernetes etc..
Introducing AKS (managed Kubernetes) and
Azure Container Registry improvements
by Microsoft Azure 2017.10.24
Azure Container Service (AKS)
Kubernetes環境を管理し、コンテナ
オーケストレーションの専門知識不要
で、コンテナ化されたアプリケーショ
ンを迅速かつ容易に展開および管理で
きます。
実行しているアプリケーションインス
タンス料金のみで、マネージドサービ
スとして提供されているkubernetesは
無料で提供されます。
7. Recently kubernetes etc..
Docker Platform and Moby Project add
Kubernetes by docker blog 2017.10.17
DockerCon17 EUで、次のDockerのバージョンからオーケストレータ
としてSwarmとKubernetesをサポートすると発表!!
まずは、Docker Enterprise Editionから!!
8. Recently kubernetes etc..
次バージョンのDocker for Win/Macでは、ローカ
ルにKubernetes環境も自動構築。DockerCon
Europe 2017 by Publickey 2017.10.18
インストールすると自動的にDocker環境とシングルクラスタによる
Kubernetesの開発環境がローカルに提供されます!!
9. Recently kubernetes etc..
コンテナオーケストレーションで「Kubernetes」が優勢
by ZDNet Japan 2017.6.5
マイクロソフト、アプリを自動的にDockerコンテナ化して
Kubernetesへデプロイしてくれる「Draft」をオープンソースで公開
by Publickey 2017.6.5
CoreOSがKubernetes-as-a-Service/etcd-as-a-Serviceなど
発表。どのクラウドでもオープンなコンテナプラットフォームを実現
by Publickey 2017.6.7
SUSE CaaS Platformが正式リリース。Kubernetes、
SLE MicroOS、Saltを統合したコンテナプラットフォーム
by Publickey 2017.6.21
11. Recently kubernetes etc..
GitHub Goes All in on Kubernetes
by THENEWSTACK 2017.8.16
SRE(Site Reliability Engineering)
の事例としても興味深い!!
12. Recently kubernetes etc..
Introducing Pivotal Container Service (PKS),
The Simple Way to Bring Kubernetes to
Enterprise Customers
by Pivotal 2017.8.28
企業レベルのKubernetesを簡単に導入及び運用、そしてコンテナベースのワーク
ロードに移行して VMware vSphereとGoogle Cloud Platform(GCP)上でも稼働。
51. 3.Bluemix CLIから以下のコマンドを実行します。
>bx plugin install container-service -r Bluemix
>bx login -a https://api.au-syd.bluemix.net
Email >
Password >
アカウントを選択します (または Enter キーを押してスキップします):
1.アカウント名's Account (aa1a87213f3f04723ea30ef1451088ae)
数値を入力してください> 1
ターゲットのアカウントアカウント名's Account (aa1a87213f3f04723ea30ef1451088ae)
ターゲットのリソース・グループ Default
API エンドポイント: https://api.au-syd.bluemix.net (API バージョン: 2.75.0)
地域: au-syd
ユーザー: Email address
アカウント: アカウント名's Account (aa1a87213f3f04723ea30ef1451088ae)
リソース・グループ: Default
組織:
スペース:
Tip: If you are managing Cloud Foundry applications and services
- Use 'bx target --cf' to target Cloud Foundry org/space interactively, or use 'bx target -o ORG -s SPACE' to
target the org/space.
- Use 'bx cf' if you want to run the Cloud Foundry CLI with current Bluemix CLI context.
自分の Bluemix アカウントにログインします。
Let’s import Bluemix Kubernetes Clusters
52. >bx cs init
Using default API endpoint: https://ap-south.containers.bluemix.net
OK
IBM Bluemix Container Service のプラグインを初期化します。
> bx cs cluster-config mycluster
OK
mycluster の構成は正常にダウンロードされました。 環境変数をエクス
ポートして Kubernetes の使用を開始してください。
SET KUBECONFIG=C:Usersy.ichikawa.bluemixpluginscontainer-
serviceclustersmyclusterkube-config-mel01-mycluster.yml
ターミナル・コンテキストをクラスターに設定します。
>SET KUBECONFIG=C:Usersy.ichikawa.bluemixpluginscontainer-serviceclustersmyclusterkube-config-mel01-mycluster.yml
Let’s import Bluemix Kubernetes Clusters
53. >kubectl get nodes
NAME STATUS AGE VERSION
10.118.243.175 Ready 1h v1.7.4-1+1540c973d4ff9d
Kubectlコマンドを実行します。
>kubectl proxy
Starting to serve on 127.0.0.1:8001
Kubernetes Dashboardも起動できます。
Let’s import Bluemix Kubernetes Clusters
60. $ az group create --name myResourceGroup --location westus2
Let’s import AKS Kubernetes Clusters
$ az aks create --resource-group myResourceGroup --name myK8sCluster --agent-count 1 --generate-ssh-keys
61. $ az aks install-cli
Let’s import AKS Kubernetes Clusters
$ az aks get-credentials --resource-group=myResourceGroup --name=myK8sCluster
$ kubectl get nodes
62. Let’s import AKS Kubernetes Clusters
3.Use existing Kubernetesの「Select」ボタンをクリックします。
64. Let’s import AKS Kubernetes Clusters
5. AKSのK8S Clusterがインポートできていることを確認します。
65. Get Started with Rancher 2.0
Step1 : Prepare a Linux Host
OS Ubuntu 16.04 (kernel 3.1.0 +) or RHEL/CentOS7.3
Mem 2GB +
Disk 80GB +
Docker Docker v1.12.6
Docker v1.13.1
Docker v17.03-ce
Docker v17.06-ce
Step2 : Start the server
sudo docker run -d --restart=unless-stopped -p 8080:8080 rancher/server:preview
Step3 : Browser Access
http://hostIP:8080
67. Document of Rancher 2.0
・Rancher Labs
https://rancher.com/announcing-rancher-2-0/
・Rancher Labs Japan
https://prtimes.jp/main/html/rd/p/000000003.000027827.html
Press Release
Rancher 2.0 Special Site
https://rancher.com/rancher2-0/
DEEP DIVE AND DEMO
https://www.youtube.com/watch?v=cATqiXBZ8MY&feature=youtu.be
TECHNICAL ARCHITECTURE
https://cdn2.hubspot.net/hubfs/468859/Whitepapers/Rancher%202
.0%20Technical%20Architecture%20-%20Sept%202017.pdf
69. Rancher Labs Sessions at kubeCon
Building Helm Charts From the Ground Up: An introduction to Kubernetes [I]
– Amy Chen 12/7 11:55am – 12:30am
Using Kubernetes API from Go [B]
– Alena Prokharchyk 12/7 4:35pm – 5:10pm
Webhooks for Automated Updates [B]
– Rajashree Mandaogane 12/8 11:55am – 12:30am