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.Dismiss alert
Copy file name to clipboardExpand all lines: samples/features/azure-arc/deployment/kubeadm/ubuntu-single-node-vm/README.md
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,17 @@ Using this sample bash script, you will deploy a single node Kubernetes cluster
6
6
## Pre-requisites
7
7
8
8
1. A vanilla Ubuntu 16.04 or 18.04 virtual or physical machine. All dependencies will be setup by the script. Using Azure Linux VMs is not yet supported.
9
-
1. Machine should have at least 8 CPUs, 64GB RAM and 100GB disk space. After installing the images you will be left with 50GB for data/logs across all components.
9
+
1. Machine should have at least 8 CPUs, 32GB RAM and 128GB disk space. After installing the images you will be left with 50GB for data/logs across all components.
10
10
1. Update existing packages using commands below to ensure that the OS image is up to date
11
11
12
12
```bash
13
-
sudo apt update&&apt upgrade -y
13
+
sudo apt update&& sudo apt upgrade -y
14
14
sudo systemctl reboot
15
15
```
16
16
17
17
## Recommended Virtual Machine settings
18
18
19
-
1. Use static memory configuration for the virtual machine. For example, in hyper-v installations do not use dynamic memory allocation but instead allocate the recommended 64 GB or higher.
19
+
1. Use static memory configuration for the virtual machine. For example, in hyper-v installations do not use dynamic memory allocation but instead allocate the recommended 32 GB or higher.
20
20
21
21
1. Use checkpoint or snapshot capability in your hyper visor so that you can rollback the virtual machine to a clean state.
3. Run the script (make sure you are running with sudo)
37
+
3. Run the script
38
38
39
39
```bash
40
-
sudo ./setup-controller.sh
40
+
./setup-controller.sh
41
41
```
42
42
43
-
When prompted, provide your input for the password that will be used for all external endpoints: controller, SQL Server master and gateway. The password should be sufficiently complex based on existing rules for SQL Server password. The controller username is defaulted to *controlleradmin*.
43
+
When prompted, provide your input for the password that will be used for all external endpoints: controller, SQL Server master and gateway. The password should be sufficiently complex based on existing rules for SQL Server password.
44
+
In case the setup-controller.sh fails and does not complete successfully, you should cleanup your enviroment using [cleanup-controller.sh](cleanup-controller.sh/) before retrying the deployment.
44
45
45
46
## Cleanup
46
47
47
48
1. The [cleanup-controller.sh](cleanup-controller.sh/) script is provided as convenience to reset the environment in case of errors. However, we recommend that you use a virtual machine for testing purposes and use the snapshot capability in your hyper-visor to rollback the virtual machine to a clean state.
0 commit comments