mirror of
https://github.com/kubesphere/website.git
synced 2025-12-30 09:42:53 +00:00
Wording and format improvment of AKS installation guide
Signed-off-by: Sherlock113 <sherlockxu@yunify.com>
This commit is contained in:
Sherlock113
parent
682593752d
commit
8e529b8039
|
|
@ -1,76 +1,81 @@
|
|||
---
|
||||
title: "Deploy KubeSphere on AKS"
|
||||
keywords: "kubesphere, kubernetes, docker, Azure, AKS"
|
||||
keywords: "KubeSphere, Kubernetes, Installation, Azure, AKS"
|
||||
description: "How to deploy KubeSphere on AKS"
|
||||
|
||||
weight: 2270
|
||||
---
|
||||
|
||||
This guide walks you through the steps of deploying KubeSphere on [Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/).
|
||||
|
||||
## Prepare a AKS cluster
|
||||
|
||||
Azure can help you implement infrastructure as code by providing resource deployment automation options; the commonly adopted tool is “Arm templates”, one of the other options is Azure CLI. In this instruction we will use Azure CLI to create all the resources that are needed by kubesphere.
|
||||
Azure can help you implement infrastructure as code by providing resource deployment automation options. Commonly adopted tools include [ARM templates](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/overview) and [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/what-is-azure-cli?view=azure-cli-latest). In this guide, we will use Azure CLI to create all the resources that are needed for the installation of KubeSphere.
|
||||
|
||||
### Use Azure Cloud Shell
|
||||
You don't have to install the Azure CLI on your machine, Azure provided a web based terminal. Select the Cloud Shell button on the menu bar at the upper right in the Azure portal.
|
||||
You don't have to install Azure CLI on your machine as Azure provides a web-based terminal. Click the Cloud Shell button on the menu bar at the upper right corner in Azure portal.
|
||||
|
||||
|
||||
|
||||
Select the **Bash** Shell
|
||||
Select **Bash** Shell.
|
||||
|
||||
|
||||
### Create a resource group
|
||||
### Create a Resource Group
|
||||
|
||||
An Azure resource group is a logical group in which Azure resources are deployed and managed. The following example creates a resource group named KubeSphereRG in the westus location.
|
||||
An Azure resource group is a logical group in which Azure resources are deployed and managed. The following example creates a resource group named `KubeSphereRG` in the location `westus`.
|
||||
|
||||
```bash
|
||||
az group create --name KubeSphereRG --location westus
|
||||
```
|
||||
|
||||
### Create AKS cluster
|
||||
Use the **az aks create** command to create an AKS cluster. The following example creates a cluster named KuberSphereCluster with three nodes. This will take several minutes to complete.
|
||||
### Create a AKS Cluster
|
||||
Use the command `az aks create` to create an AKS cluster. The following example creates a cluster named `KuberSphereCluster` with three nodes. This will take several minutes to complete.
|
||||
|
||||
```bash
|
||||
az aks create --resource-group KubeSphereRG --name KuberSphereCluster --node-count 3 --enable-addons monitoring --generate-ssh-keys
|
||||
```
|
||||
> Notes:
|
||||
> - You can use --node-vm-size or -s option to change the Size of Kubernetes nodes. Default: Standard_DS2_v2( 2vCPU, 7GB memory).
|
||||
> - More options can be found at https://docs.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-create
|
||||
{{< notice note >}}
|
||||
|
||||
### Connect to the cluster
|
||||
To configure kubectl to connect to Kubernetes cluster, use the **az aks get-credentials** command. This command downloads credentials and configures the Kubernetes CLI to use them.
|
||||
You can use `--node-vm-size` or `-s` option to change the size of Kubernetes nodes. Default: Standard_DS2_v2 (2vCPU, 7GB memory). For more options, see [az aks create](https://docs.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-create).
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
### Connect to the Cluster
|
||||
|
||||
To configure kubectl to connect to the Kubernetes cluster, use the command `az aks get-credentials`. This command downloads credentials and configures the Kubernetes CLI to use them.
|
||||
|
||||
```bash
|
||||
az aks get-credentials --resource-group KubeSphereRG --name KuberSphereCluster
|
||||
```
|
||||
|
||||
```
|
||||
```bash
|
||||
kebesphere@Azure:~$ kubectl get nodes
|
||||
NAME STATUS ROLES AGE VERSION
|
||||
aks-nodepool1-23754246-vmss000000 Ready agent 38m v1.16.13
|
||||
```
|
||||
### Check Azure Resources in the Portal
|
||||
After we execute all the commands above. We should see there are 2 Resource Groups created in the Azure Portal.
|
||||
After you execute all the commands above, you can see there are 2 Resource Groups created in Azure Portal.
|
||||
|
||||
|
||||
|
||||
The Azure Kubernetes Services itself will be placed in the KubeSphereRG.
|
||||
|
||||
Azure Kubernetes Services itself will be placed in KubeSphereRG.
|
||||
|
||||
|
||||
|
||||
All the other Resources will be placed in MC_KubeSphereRG_KuberSphereCluster_westus, such as VMs, Load Balancer, Virtual Network, etc.
|
||||
All the other Resources will be placed in MC_KubeSphereRG_KuberSphereCluster_westus, such as VMs, Load Balancer and Virtual Network.
|
||||
|
||||
|
||||
|
||||
## Deploy KubeSphere
|
||||
To Start Deploying KubeSphere, using the following command.
|
||||
## Deploy KubeSphere on AKS
|
||||
To start deploying KubeSphere, use the following command.
|
||||
```bash
|
||||
kubectl apply -f https://raw.githubusercontent.com/kubesphere/ks-installer/master/deploy/kubesphere-installer.yaml
|
||||
```
|
||||
Download the cluster-configuration.yaml, so you can customize the configuration. You can also enable pluggable components by set the **enabled** property to **true** in this file.
|
||||
Download the cluster-configuration.yaml as below and you can customize the configuration. You can also enable pluggable components by setting the `enabled` property to `true` in this file.
|
||||
```bash
|
||||
wget https://raw.githubusercontent.com/kubesphere/ks-installer/master/deploy/cluster-configuration.yaml
|
||||
```
|
||||
The metrics-server was already installed on the AKS, you need disable the component in the cluster-configuration.yaml file.
|
||||
As `metrics-server` is already installed on AKS, you need to disable the component in the cluster-configuration.yaml file by changing `true` to `false` for `enabled`.
|
||||
```bash
|
||||
kebesphere@Azure:~$ vim ./cluster-configuration.yaml
|
||||
---
|
||||
|
|
@ -78,19 +83,25 @@ kebesphere@Azure:~$ vim ./cluster-configuration.yaml
|
|||
enabled: false
|
||||
---
|
||||
```
|
||||
Installation process will be started after the cluster configuration applied.
|
||||
The installation process will start after the cluster configuration is applied through the following command:
|
||||
```bash
|
||||
kubectl apply -f ./cluster-configuration.yaml
|
||||
```
|
||||
|
||||
## Access KubeSphere console
|
||||
You can inspect the logs of installation through the following command:
|
||||
|
||||
To access KubeSphere console from public ip address, you need change service type to LoadBalancer.
|
||||
```bash
|
||||
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f
|
||||
```
|
||||
|
||||
## Access KubeSphere Console
|
||||
|
||||
To access KubeSphere console from a public IP address, you need to change the service type to `LoadBalancer`.
|
||||
```bash
|
||||
kubectl edit service ks-console -n kubesphere-system
|
||||
```
|
||||
Find the following section, and change the type to **LoadBalancer**.
|
||||
```
|
||||
Find the following section and change the type to `LoadBalancer`.
|
||||
```bash
|
||||
spec:
|
||||
clusterIP: 10.0.78.113
|
||||
externalTrafficPolicy: Cluster
|
||||
|
|
@ -105,15 +116,16 @@ spec:
|
|||
tier: frontend
|
||||
version: v3.0.0
|
||||
sessionAffinity: None
|
||||
type: LoadBalancer # Change the NodePort to LoadBalancer
|
||||
type: LoadBalancer # Change NodePort to LoadBalancer
|
||||
status:
|
||||
loadBalancer: {}
|
||||
```
|
||||
After saved the ks-console Service, you can use the following command to get the public ip address.
|
||||
```
|
||||
After saving the configuration of ks-console service, you can use the following command to get the public IP address (under `EXTERNAL-IP`). Use the IP address to access the console with the default account and password (`admin/P@88w0rd`).
|
||||
```bash
|
||||
kebesphere@Azure:~$ kubectl get svc/ks-console -n kubesphere-system
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
ks-console LoadBalancer 10.0.181.93 13.86.xxx.xxx 80:30194/TCP 13m 6379/TCP 10m
|
||||
```
|
||||
## Enable Pluggable Components (Optional)
|
||||
Pluggable components are designed to be pluggable which means you can enable them either before or after installation. See [Enable Pluggable Components](https://github.com/kubesphere/ks-installer#enable-pluggable-components) for details.
|
||||
|
||||
The example above demonstrates the process of a default minimal installation. For pluggable components, you can enable them either before or after the installation. See [Enable Pluggable Components](https://github.com/kubesphere/ks-installer#enable-pluggable-components) for details.
|
||||
Loading…
Reference in New Issue