vshender microservices repository
- Added a pre-commit hook.
- Added a Github PR template.
- Added Github actions.
- Installed Docker.
- Experimented with various Docker commands.
- Created a Docker machine on a Yandex.Cloud VM.
- Built the application image and ran it.
- Pushed the application image to DockerHub.
- Implemented the application deployment.
Details
Install a pre-commit hook:
$ vim .pre-commit-config.yaml
$ pre-commit install
pre-commit installed at .git/hooks/pre-commit
Check Docker:
$ docker version
Client:
Cloud integration: v1.0.25
Version: 20.10.16
API version: 1.41
Go version: go1.17.10
Git commit: aa7e414
Built: Thu May 12 09:20:34 2022
OS/Arch: darwin/amd64
Context: default
Experimental: true
Server: Docker Desktop 4.9.1 (81317)
Engine:
Version: 20.10.16
API version: 1.41 (minimum version 1.12)
Go version: go1.17.10
Git commit: f756502
Built: Thu May 12 09:15:42 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.4
GitCommit: 212e8b6fa2f44b9c21b2798135fc6fb7c53efc16
runc:
Version: 1.1.1
GitCommit: v1.1.1-0-g52de29d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
$ docker info
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.8.2)
compose: Docker Compose (Docker Inc., v2.6.0)
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
scan: Docker Scan (Docker Inc., v0.17.0)
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 3
Server Version: 20.10.16
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 212e8b6fa2f44b9c21b2798135fc6fb7c53efc16
runc version: v1.1.1-0-g52de29d
init version: de40ad0
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 5.10.104-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 7.773GiB
Name: docker-desktop
ID: GA3U:AGYV:U6MS:ZAEP:OXSE:43GB:MILL:SIL6:LDUZ:IGJF:7SMA:7FUC
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5000
127.0.0.0/8
Live Restore Enabled: false
Run a first Docker container:
$ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:13e367d31ae85359f42d637adf6da428f76d75dc9afeb3c21faea0d976f5c651
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
79cb0bad4865 hello-world "/hello" About a minute ago Exited (0) About a minute ago funny_davinci
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
hello-world latest feb5d9fea6a5 9 months ago 13.3kB
Experimenting with the run, start, attach, and exec Docker commands:
$ docker run -it ubuntu:18.04 /bin/bash
Unable to find image 'ubuntu:18.04' locally
18.04: Pulling from library/ubuntu
09db6f815738: Pull complete
Digest: sha256:478caf1bec1afd54a58435ec681c8755883b7eb843a8630091890130b15a79af
Status: Downloaded newer image for ubuntu:18.04
root@f07a59f3e9a4:/# echo 'Hello world!' > /tmp/file
root@f07a59f3e9a4:/# exit
exit
$ docker run -it ubuntu:18.04 /bin/bash
root@07abba940540:/# cat /tmp/file
cat: /tmp/file: No such file or directory
root@07abba940540:/# exit
exit
$ docker ps -a --format "table {{.ID}}\t{{.Image}}\t{{.CreatedAt}}\t{{.Names}}"
CONTAINER ID IMAGE CREATED AT NAMES
07abba940540 ubuntu:18.04 2022-07-05 23:57:16 +0100 WEST keen_bhabha
f07a59f3e9a4 ubuntu:18.04 2022-07-05 23:56:52 +0100 WEST serene_wilbur
79cb0bad4865 hello-world 2022-07-05 23:54:42 +0100 WEST funny_davinci
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
07abba940540 ubuntu:18.04 "/bin/bash" 3 minutes ago Exited (1) 3 minutes ago keen_bhabha
f07a59f3e9a4 ubuntu:18.04 "/bin/bash" 4 minutes ago Exited (1) 4 minutes ago serene_wilbur
79cb0bad4865 hello-world "/hello" 6 minutes ago Exited (0) 6 minutes ago funny_davinci
$ docker start f07a59f3e9a4
f07a59f3e9a4
$ docker attach f07a59f3e9a4
root@f07a59f3e9a4:/# cat /tmp/file
Hello world!
root@f07a59f3e9a4:/# read escape sequence # Ctrl-p Ctrl-q
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
07abba940540 ubuntu:18.04 "/bin/bash" 3 minutes ago Exited (1) 3 minutes ago keen_bhabha
f07a59f3e9a4 ubuntu:18.04 "/bin/bash" 4 minutes ago Up 27 seconds serene_wilbur
79cb0bad4865 hello-world "/hello" 6 minutes ago Exited (0) 6 minutes ago funny_davinci
$ docker exec -it f07a59f3e9a4 bash
root@f07a59f3e9a4:/# ps afx
PID TTY STAT TIME COMMAND
12 pts/1 Ss 0:00 bash
23 pts/1 R+ 0:00 \_ ps afx
1 pts/0 Ss+ 0:00 /bin/bash
root@f07a59f3e9a4:/# exit
exit
Experimenting with the commit Docker command:
$ docker commit f07a59f3e9a4 vshender/ubuntu-tmp-file
sha256:2081712dd4de76fff23063e05869d96e288ce0be074b0840411c3636f7501e03
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
vshender/ubuntu-tmp-file latest 2081712dd4de 3 seconds ago 63.1MB
ubuntu 18.04 ad080923604a 4 weeks ago 63.1MB
hello-world latest feb5d9fea6a5 9 months ago 13.3kB
Examine output of the inspect Docker command:
$ docker inspect 2081712dd4de
...
$ docker inspect f07a59f3e9a4
...
(See docker_inspect_image.log and docker_inspect_container.log).
The output of docker inspect for container has the "State", "HostConfig", "LogPath", "Mounts", and "NetworkSettings" items containing information about a running container.
Experimenting with the ps, images, system, kill, rm, and rmi Docker commands:
$ docker ps -q
f07a59f3e9a4
$ docker kill $(docker ps -q)
f07a59f3e9a4
$ docker system df
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 3 2 63.16MB 63.15MB (99%)
Containers 3 0 88B 88B (100%)
Local Volumes 0 0 0B 0B
Build Cache 18 0 18.06MB 18.06MB
$ docker rm $(docker ps -a -q)
07abba940540
f07a59f3e9a4
79cb0bad4865
$ docker images -q
2081712dd4de
ad080923604a
feb5d9fea6a5
$ docker rmi $(docker images -q)
Untagged: vshender/ubuntu-tmp-file:latest
Deleted: sha256:2081712dd4de76fff23063e05869d96e288ce0be074b0840411c3636f7501e03
Deleted: sha256:770eca87c93b88ac6bd2e1ff801b821adb9ed79801e5cf37abc64138aef01fef
Untagged: ubuntu:18.04
Untagged: ubuntu@sha256:478caf1bec1afd54a58435ec681c8755883b7eb843a8630091890130b15a79af
Deleted: sha256:ad080923604aa54962e903125cd9a860605c111bc45afc7d491cd8c77dccc13b
Deleted: sha256:95129a5fe07e89c1898dc40a027b291d5fe33a67b35a88f0f0eaf51ea691f0b5
Untagged: hello-world:latest
Untagged: hello-world@sha256:13e367d31ae85359f42d637adf6da428f76d75dc9afeb3c21faea0d976f5c651
Deleted: sha256:feb5d9fea6a5e9606aa995e879d862b825965ba48de054caab5ef356dc6b3412
Deleted: sha256:e07ee1baac5fae6a26f30cabfe54a36d3402f96afda318fe0a96cec4ca393359
Create a Docker machine on a Yandex.Cloud VM:
$ yc compute instance create \
--name docker-host \
--zone ru-central1-a \
--network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
--create-boot-disk image-folder-id=standard-images,image-family=ubuntu-1804-lts,size=15 \
--ssh-key ~/.ssh/appuser.pub
done (36s)
id: fhmbrm0559oh9jgfsrds
folder_id: ...
created_at: "2022-07-11T14:42:35Z"
name: docker-host
zone_id: ru-central1-a
platform_id: standard-v2
resources:
memory: "2147483648"
cores: "2"
core_fraction: "100"
status: RUNNING
boot_disk:
mode: READ_WRITE
device_name: fhm83c85c1oab87bpunn
auto_delete: true
disk_id: fhm83c85c1oab87bpunn
network_interfaces:
- index: "0"
mac_address: d0:0d:bd:d8:05:2a
subnet_id: e9bqom95bd1o3fkemarr
primary_v4_address:
address: 10.128.0.28
one_to_one_nat:
address: 62.84.114.61
ip_version: IPV4
fqdn: fhmbrm0559oh9jgfsrds.auto.internal
scheduling_policy: {}
network_settings:
type: STANDARD
placement_policy: {}
$ docker-machine create \
--driver generic \
--generic-ip-address=62.84.114.61 \
--generic-ssh-user yc-user \
--generic-ssh-key ~/.ssh/appuser \
docker-host
Creating CA: /Users/vshender/.docker/machine/certs/ca.pem
Creating client certificate: /Users/vshender/.docker/machine/certs/cert.pem
Running pre-create checks...
Creating machine...
(docker-host) Importing SSH key...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env docker-host
$ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docker-host - generic Running tcp://62.84.114.61:2376 v20.10.17
$ eval $(docker-machine env docker-host)
Compare the output of htop:
$ docker run --rm -ti tehbilly/htop
Unable to find image 'tehbilly/htop:latest' locally
latest: Pulling from tehbilly/htop
1eae7a7426b0: Pull complete
ac2ca7632b9e: Pull complete
Digest: sha256:2284dc3e689c1db92163af48b329b93d4de8c778d411c0e6e375430736e57117
Status: Downloaded newer image for tehbilly/htop:latest
$ docker run --rm --pid host -ti tehbilly/htop
htop from the last command displays all processes of the Docker machine's VM.
Build the application image and run it:
$ cd docker/docker-monolith
$ docker build -t reddit:latest .
Sending build context to Docker daemon 18.94kB
Step 1/7 : FROM ubuntu:16.04
16.04: Pulling from library/ubuntu
58690f9b18fc: Pull complete
b51569e7c507: Pull complete
da8ef40b9eca: Pull complete
fb15d46c38dc: Pull complete
Digest: sha256:20858ebbc96215d6c3c574f781133ebffdc7c18d98af4f294cc4c04871a6fe61
Status: Downloaded newer image for ubuntu:16.04
---> b6f507652425
Step 2/7 : RUN apt-get update
---> Running in 978554bf973d
...
Step 10/11 : RUN chmod 0777 /start.sh
---> Running in 638c267016a6
Removing intermediate container 638c267016a6
---> 9bd35c0d173f
Step 11/11 : CMD ["/start.sh"]
---> Running in 3eb83e42f4ea
Removing intermediate container 3eb83e42f4ea
---> ee329dbecf6e
Successfully built ee329dbecf6e
Successfully tagged reddit:latest
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
reddit latest 42a6b2e06960 5 seconds ago 676MB
ubuntu 18.04 ad080923604a 5 weeks ago 63.1MB
ubuntu 16.04 b6f507652425 10 months ago 135MB
tehbilly/htop latest 4acd2b4de755 4 years ago 6.91MB
$ docker images -a
REPOSITORY TAG IMAGE ID CREATED SIZE
<none> <none> 3d3d06782304 15 seconds ago 676MB
reddit latest 42a6b2e06960 15 seconds ago 676MB
<none> <none> 12ce4f78fa32 17 seconds ago 676MB
<none> <none> dc066c50f7bb 32 seconds ago 660MB
<none> <none> c99d719dd6ec 32 seconds ago 660MB
<none> <none> ec6dec58fbe7 33 seconds ago 660MB
<none> <none> 2bdcf5ce9d40 33 seconds ago 660MB
<none> <none> 9dc5324bcfce 37 seconds ago 660MB
<none> <none> 251c190e19a9 About a minute ago 166MB
ubuntu 18.04 ad080923604a 5 weeks ago 63.1MB
ubuntu 16.04 b6f507652425 10 months ago 135MB
tehbilly/htop latest 4acd2b4de755 4 years ago 6.91MB
$ docker run --name reddit -d --network=host reddit:latest
480ef124283b116af29f76e0adc167c89e5db8610bce3e8befafa7cd6bcd34a1
Open http://62.84.114.61:9292/ and check the application.
Push the application image to DockerHub:
$ docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username: vshender
Password:
Login Succeeded
Logging in with your password grants your terminal complete access to your account.
For better security, log in with a limited-privilege personal access token. Learn more at https://docs.docker.com/go/access-tokens/
$ docker tag reddit:latest vshender/otus-reddit:1.0
$ docker push vshender/otus-reddit:1.0
The push refers to repository [docker.io/vshender/otus-reddit]
561d32163b5d: Pushed
4e468ef4e0d7: Pushed
e0b51e6e0b00: Pushed
c0e930ada599: Pushed
7e834663955a: Pushed
6abc2b3e7bb0: Pushed
7133d482fda6: Pushed
207ddfee0858: Pushed
1251204ef8fc: Pushed
47ef83afae74: Pushed
df54c846128d: Pushed
be96a3f634de: Pushed
1.0: digest: sha256:7b24122dde3b25e650192c096f228bd40136b24512db78444b254d8a794f2737 size: 2823
$ eval $(docker-machine env --unset)
$ docker run --name reddit -d -p 9292:9292 vshender/otus-reddit:1.0
Unable to find image 'vshender/otus-reddit:1.0' locally
1.0: Pulling from vshender/otus-reddit
58690f9b18fc: Pull complete
b51569e7c507: Pull complete
da8ef40b9eca: Pull complete
fb15d46c38dc: Pull complete
15ab9c91db51: Pull complete
2bf406696b28: Pull complete
ead2fc68327c: Pull complete
b4608768d268: Pull complete
081b5dd5e53c: Pull complete
d8be6b88f4d7: Pull complete
0712db74546f: Pull complete
9b5b1bbca7bd: Pull complete
Digest: sha256:7b24122dde3b25e650192c096f228bd40136b24512db78444b254d8a794f2737
Status: Downloaded newer image for vshender/otus-reddit:1.0
faacc704c59019ecff87bc57bb9ecc0dad9f8a14df6a9137548ae633e6efed9e
Open http://127.0.0.1:9292/ and test the application.
Destroy the Docker machine:
$ docker-machine rm docker-host
About to remove docker-host
WARNING: This action will delete both local reference and remote instance.
Are you sure? (y/n): y
Successfully removed docker-host
$ yc compute instance delete docker-host
done (15s)
Create infrastructure and deploy the application:
$ cd infra
$ packer build -var-file=packer/variables.json packer/docker-host.json
...
==> Wait completed after 5 minutes 17 seconds
==> Builds finished. The artifacts of successful builds are:
--> yandex: A disk image was created: docker-host-1658054613 (id: fd890m36h1ti7psoioh9) with family name docker-host
$ yc compute image list
+----------------------+----------------------------+-----------------+----------------------+--------+
| ID | NAME | FAMILY | PRODUCT IDS | STATUS |
+----------------------+----------------------------+-----------------+----------------------+--------+
...
| fd890m36h1ti7psoioh9 | docker-host-1658054613 | docker-host | f2ep34rv24tdc64fekvu | READY |
...
+----------------------+----------------------------+-----------------+----------------------+--------+
$ cd terraform
$ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding yandex-cloud/yandex versions matching "~> 0.73.0"...
- Finding latest version of hashicorp/local...
- Installing yandex-cloud/yandex v0.73.0...
- Installed yandex-cloud/yandex v0.73.0 (unauthenticated)
- Installing hashicorp/local v2.2.3...
- Installed hashicorp/local v2.2.3 (unauthenticated)
...
$ terraform apply -auto-approve
...
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
Outputs:
app_vm_ips = [
"51.250.91.72",
"62.84.116.253",
]
$ cd ../ansible
$ ansible-playbook --skip-tags install_docker site.yml
PLAY [Install Docker] ********************************************************************************************
PLAY [Deploy reddit application] *********************************************************************************
TASK [Run reddit app container] **********************************************************************************
changed: [reddit-app-0]
changed: [reddit-app-1]
PLAY RECAP *******************************************************************************************************
reddit-app-0 : ok=1 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
reddit-app-1 : ok=1 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Open http://51.250.91.72:9292/ and http://62.84.116.253:9292/ and check the application.
Destroy the application's infrastructure:
$ cd ../terraform
$ terraform destroy -auto-approve
...
Destroy complete! Resources: 3 destroyed.
- Added the reddit application microservices code.
- Added Dockerfiles for the application images.
- Built the application images.
- Ran the application.
- Ran the application containers using different network aliases.
- Optimized the
commentanduiimages using an Ubuntu base image. - Optimized the application images using an Alpine base image.
- Used a Docker volume to store MongoDB data.
Details
Prepare a Docker machine:
$ yc compute instance create \
--name docker-host \
--zone ru-central1-a \
--network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
--create-boot-disk image-folder-id=standard-images,image-family=ubuntu-1804-lts,size=15 \
--ssh-key ~/.ssh/appuser.pub
...
one_to_one_nat:
address: 62.84.119.234
...
$ docker-machine create \
--driver generic \
--generic-ip-address=62.84.119.234 \
--generic-ssh-user yc-user \
--generic-ssh-key ~/.ssh/appuser \
docker-host
...
$ eval $(docker-machine env docker-host)
Build the application images:
$ cd src
$ docker build -t vshender/post:1.0 -f Dockerfile.old ./post-py
...
Successfully built 8e9049ae34d6
Successfully tagged vshender/post:1.0
$ docker build -t vshender/comment:1.0 -f Dockerfile.ruby ./comment
...
Successfully built 6ba027cfeb81
Successfully tagged vshender/comment:1.0
$ docker build -t vshender/ui:1.0 -f Dockerfile.ruby ./ui
...
Successfully built fc53a1755fe2
Successfully tagged vshender/ui:1.0
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
vshender/ui 1.0 fc53a1755fe2 11 seconds ago 772MB
vshender/comment 1.0 6ba027cfeb81 About a minute ago 770MB
vshender/post 1.0 8e9049ae34d6 2 minutes ago 111MB
ruby 2.2 6c8e6f9667b2 4 years ago 715MB
python 3.6.0-alpine cb178ebbf0f2 5 years ago 88.6MB
Run the application:
$ docker network create reddit
fd5feff84899137daa764e9cb2a3094a85ea6dace71dfb54718364ab1d1fb802
$ docker run -d \
--network=reddit \
--network-alias=post_db \
--network-alias=comment_db \
mongo:latest
Unable to find image 'mongo:latest' locally
latest: Pulling from library/mongo
...
Digest: sha256:82302b06360729842acd27ab8a91c90e244f17e464fcfd366b7427af652c5559
Status: Downloaded newer image for mongo:latest
bda52d0c6a16860162e6b2c281ce5e5d03a7d68368e7895484e1972a24f17095
$ docker run -d \
--network=reddit \
--network-alias=post \
vshender/post:1.0
3523c4b38f96fe169ccbe7aab75e0cc3ff38d07edfb51b820b94a0770a7aca0a
$ docker run -d \
--network=reddit \
--network-alias=comment \
vshender/comment:1.0
eaf56f450bf1cf781e1d6cae175918aee6e5f0e59844cdea5e961f2194aaf5a6
$ docker run -d \
--network=reddit \
-p 9292:9292 \
vshender/ui:1.0
9ecc25b9e9830c1480279519f62818efc5c93eb13368b9fc2c6751cb6a8b0038
Open http://62.84.119.234:9292/ and test the application.
Run the application containers using different network aliases.
$ docker kill $(docker ps -q)
9ecc25b9e983
eaf56f450bf1
3523c4b38f96
bda52d0c6a16
$ docker run -d \
--network=reddit \
--network-alias=post_database \
--network-alias=comment_database \
mongo:latest
ccd828e9f1fcd9c1d01326ab5f78a73301fd9cd251d3b5dfa6c4571a1b31f7b0
$ docker run -d \
--network=reddit \
--network-alias=post_service \
-e POST_DATABASE_HOST=post_database \
vshender/post:1.0
33a8d0b88e3e96ca92159c865f157e3d9ade28619abce046bfe6d7dbb4cfa207
$ docker run -d \
--network=reddit \
--network-alias=comment_service \
-e COMMENT_DATABASE_HOST=comment_database \
vshender/comment:1.0
077c425687b739403cae90c0e8a3e4aef3e8675609369a53e08c5c52ed0b6c80
$ docker run -d \
--network=reddit \
-p 9292:9292 \
-e POST_SERVICE_HOST=post_service \
-e COMMENT_SERVICE_HOST=comment_service \
vshender/ui:1.0
68af4302524ca413be790ba976d75363217f0c77c205869a0cbbab7138d6d3f9
Open http://62.84.119.234:9292/ and test the application.
Optimize the comment and ui images using an Ubuntu base image and examine the image sizes:
$ docker build -t vshender/comment:2.0 -f Dockerfile.ubuntu ./comment
...
Successfully built a77efba79646
Successfully tagged vshender/comment:2.0
$ docker build -t vshender/ui:2.0 -f Dockerfile.ubuntu ./ui
...
Successfully built 25e1f3b0b53e
Successfully tagged vshender/ui:2.0
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
vshender/ui 2.0 25e1f3b0b53e 10 seconds ago 410MB
vshender/comment 2.0 a77efba79646 46 seconds ago 407MB
vshender/ui 1.0 fc53a1755fe2 30 minutes ago 772MB
vshender/comment 1.0 6ba027cfeb81 31 minutes ago 770MB
vshender/post 1.0 8e9049ae34d6 32 minutes ago 111MB
mongo latest c8b57c4bf7e3 4 weeks ago 701MB
ubuntu 16.04 b6f507652425 10 months ago 135MB
ruby 2.2 6c8e6f9667b2 4 years ago 715MB
python 3.6.0-alpine cb178ebbf0f2 5 years ago 88.6MB
Optimize the application images using an Alpine base image:
$ docker build -t vshender/post:2.0 ./post-py
...
Successfully built 9f025b407f1a
Successfully tagged vshender/post:2.0
$ docker build -t vshender/comment:3.0 ./comment
...
Successfully built 62859ed3f3bf
Successfully tagged vshender/comment:3.0
$ docker build -t vshender/ui:3.0 ./ui
...
Successfully built bb8fe4b4093a
Successfully tagged vshender/ui:3.0
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
vshender/ui 3.0 bb8fe4b4093a 9 seconds ago 71.6MB
vshender/comment 3.0 62859ed3f3bf 4 minutes ago 69.5MB
vshender/post 2.0 9f025b407f1a 5 minutes ago 107MB
vshender/ui 2.0 25e1f3b0b53e 25 minutes ago 410MB
vshender/comment 2.0 a77efba79646 26 minutes ago 407MB
vshender/ui 1.0 fc53a1755fe2 56 minutes ago 772MB
vhsender/comment 1.0 6ba027cfeb81 57 minutes ago 770MB
vshender/post 1.0 8e9049ae34d6 58 minutes ago 111MB
...
Use a Docker volume to store MongoDB data:
$ docker stop $(docker ps -q)
fdd93a8b764b
37fa1d2bbf3d
33a8d0b88e3e
ccd828e9f1fc
$ docker volume create reddit_db
reddit_db
$ docker run -d \
--network=reddit \
--network-alias=post_db \
--network-alias=comment_db \
-v reddit_db:/data/db \
mongo:latest
94862b88ecc864b188468c65729f0c9843f0e7b6e5ba91c5ecbce42a44fe3512
$ docker run -d \
--network=reddit \
--network-alias=post \
vshender/post:2.0
5129670cda53b9f1801c4a1af3e8a518cf74bf850562bcb074d866131f1b8e6b
$ docker run -d \
--network=reddit \
--network-alias=comment \
vshender/comment:3.0
9ac3d835180e961cf2e58dc40f24a343f7ce4034273ca448107ea6f137de455e
$ docker run -d \
--network=reddit \
-p 9292:9292 \
vshender/ui:3.0
393b0942a19c612998f50e8f5424be082c9fe0f51128748eaf3cc6bae0bb7c21
Open http://62.84.119.234:9292/ and create some posts and comments.
Restart a MongoDB container:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
...
94862b88ecc8 mongo:latest "docker-entrypoint.sβ¦" 2 minutes ago Up 2 minutes 27017/tcp serene_johnson
$ docker stop 94862b88ecc8
94862b88ecc8
$ docker run -d \
--network=reddit \
--network-alias=post_db \
--network-alias=comment_db \
-v reddit_db:/data/db \
mongo:latest
155c291afafe61b76d70f89f3579f70217394f42f3344a25df0d17b7dec0f350
Open http://62.84.119.234:9292/ and verify that the created data still exists.
Stop the application containers:
$ docker stop $(docker ps -q)
155c291afafe
393b0942a19c
9ac3d835180e
5129670cda53
Remove the created bridge network:
$ docker network rm reddit
reddit
- Compared the
noneandhostnetwork drivers. - Ran the application containers on two bridge networks so that the
uiservice didn't have access to the DB. - Added a
docker-compose.ymlfile to run the application. - Modified
docker-compose.ymlto run the application containers on two bridge networks. - Parameterized
docker-compose.yml. - Ran the application using the updated
docker-compose.ymland specifying a project name. - Added the
docker-compose.override.ymlfile that allows you to edit the application code and apply changes without rebuilding images.
Details
Compare the none and host network drivers:
$ eval $(docker-machine env docker-host)
$ docker run --rm --network none joffotron/docker-net-tools -c ifconfig
Unable to find image 'joffotron/docker-net-tools:latest' locally
...
Status: Downloaded newer image for joffotron/docker-net-tools:latest
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
$ docker run --rm --network host joffotron/docker-net-tools -c ifconfig
br-fd5feff84899 Link encap:Ethernet HWaddr 02:42:4B:75:B2:8B
inet addr:172.18.0.1 Bcast:172.18.255.255 Mask:255.255.0.0
inet6 addr: fe80::42:4bff:fe75:b28b%32622/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:281 errors:0 dropped:0 overruns:0 frame:0
TX packets:353 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:185211 (180.8 KiB) TX bytes:160578 (156.8 KiB)
docker0 Link encap:Ethernet HWaddr 02:42:8A:EC:37:51
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
inet6 addr: fe80::42:8aff:feec:3751%32622/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:52155 errors:0 dropped:0 overruns:0 frame:0
TX packets:85900 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4111194 (3.9 MiB) TX bytes:1236827460 (1.1 GiB)
eth0 Link encap:Ethernet HWaddr D0:0D:17:28:49:B7
inet addr:10.128.0.26 Bcast:10.128.0.255 Mask:255.255.255.0
inet6 addr: fe80::d20d:17ff:fe28:49b7%32622/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:224231 errors:0 dropped:0 overruns:0 frame:0
TX packets:119906 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3215951264 (2.9 GiB) TX bytes:11878584 (11.3 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%32622/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:100284 errors:0 dropped:0 overruns:0 frame:0
TX packets:100284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7388480 (7.0 MiB) TX bytes:7388480 (7.0 MiB)
$ docker-machine ssh docker-host sudo apt install -y net-tools && ifconfig
...
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
XHC1: flags=0<> mtu 0
XHC0: flags=0<> mtu 0
XHC20: flags=0<> mtu 0
VHC128: flags=0<> mtu 0
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
...
ap1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
...
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
...
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
...
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
...
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
...
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
...
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
...
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
...
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
...
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
...
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
...
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
...
en8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
...
Run the application containers on two bridge networks so that the ui service doesn't have access to the DB.
$ docker network create back_net --subnet=10.0.2.0/24
5f5f01466d0c881bed1f3c058ad049f3cc2a90aa09b8a6499c4da77fcf77c236
$ docker network create front_net --subnet=10.0.1.0/24
22bc170d24e9805cbdd8d7e6de6bea69f40529e901234d53df595910080ef173
$ docker network list
NETWORK ID NAME DRIVER SCOPE
5f5f01466d0c back_net bridge local
f580f42afc1e bridge bridge local
22bc170d24e9 front_net bridge local
ede3e8bcd3df host host local
6ac654ba85f4 none null local
$ docker run -d --network=front_net -p 9292:9292 --name ui vshender/ui:3.0
e2f912af502d56aa42a26623d1751c280999b9ee81b7c79d8a50c14822d1f81b
$ docker run -d --network=back_net --name comment vshender/comment:3.0
667d364af1a74e273785dbff6693cd87544c387dfd5bcecc827aaed4c8c9afc3
$ docker run -d --network=back_net --name post vshender/post:2.0
43fe9073a6bc21a267fe1aacf9092567e9f069057b62b409fae8ccd91e92fcd6
$ docker run -d --network=back_net --name mongo_db --network-alias=post_db --network-alias=comment_db -v reddit_db:/data/db mongo:latest
e280830eabede0a4a81f0ecd265d27c24c8c9832dda83315d0c05148d89f4672
$ docker network connect front_net post
$ docker network connect front_net comment
Open http://62.84.119.234:9292/ and check the application.
Examine network on Docker machine:
$ docker-machine ssh docker-host
Welcome to Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0-112-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
New release '20.04.4 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
yc-user@docker-host:~$ sudo apt update && sudo apt install bridge-utils
...
yc-user@docker-host:~$ sudo docker network ls
NETWORK ID NAME DRIVER SCOPE
5f5f01466d0c back_net bridge local
f580f42afc1e bridge bridge local
22bc170d24e9 front_net bridge local
ede3e8bcd3df host host local
6ac654ba85f4 none null local
yc-user@docker-host:~$ ifconfig | grep ^br
br-22bc170d24e9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
br-5f5f01466d0c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
yc-user@docker-host:~$ brctl show br-22bc170d24e9
bridge name bridge id STP enabled interfaces
br-22bc170d24e9 8000.024211a431d0 no veth6437a35
vethf4ab308
vethf91e4b1
yc-user@docker-host:~$ brctl show br-5f5f01466d0c
bridge name bridge id STP enabled interfaces
br-5f5f01466d0c 8000.024293451890 no veth2ebcd2d
vetha5ab886
vetha6fc845
yc-user@docker-host:~$ sudo iptables -nL -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DOCKER all -- 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type LOCAL
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DOCKER all -- 0.0.0.0/0 !127.0.0.0/8 ADDRTYPE match dst-type LOCAL
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- 10.0.1.0/24 0.0.0.0/0
MASQUERADE all -- 10.0.2.0/24 0.0.0.0/0
MASQUERADE all -- 172.17.0.0/16 0.0.0.0/0
MASQUERADE tcp -- 10.0.1.2 10.0.1.2 tcp dpt:9292
Chain DOCKER (2 references)
target prot opt source destination
RETURN all -- 0.0.0.0/0 0.0.0.0/0
RETURN all -- 0.0.0.0/0 0.0.0.0/0
RETURN all -- 0.0.0.0/0 0.0.0.0/0
DNAT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:9292 to:10.0.1.2:9292
yc-user@docker-host:~$ ps -ef | grep docker-proxy
root 20259 3730 0 18:46 ? 00:00:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9292 -container-ip 10.0.1.2 -container-port 9292
root 20266 3730 0 18:46 ? 00:00:00 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9292 -container-ip 10.0.1.2 -container-port 9292
yc-user 23759 22660 0 18:56 pts/0 00:00:00 grep --color=auto docker-proxy
yc-user@docker-host:~$ logout
Stop the application containers:
$ docker stop $(docker ps -q)
e280830eabed
43fe9073a6bc
667d364af1a7
e2f912af502d
Use the docker-compose.yml file to run the application:
$ cd src
$ export USERNAME=vshender
$ docker-compose up -d
Creating network "src_reddit" with the default driver
Creating volume "src_post_db" with default driver
Pulling db (mongo:3.2)...
...
Creating src_post_1 ... done
Creating src_comment_1 ... done
Creating src_ui_1 ... done
Creating src_db_1 ... done
$ docker-compose ps
Name Command State Ports
----------------------------------------------------------------------------------------------
src_comment_1 puma Up
src_db_1 docker-entrypoint.sh mongod Up 27017/tcp
src_post_1 python3 post_app.py Up
src_ui_1 puma Up 0.0.0.0:9292->9292/tcp,:::9292->9292/tcp
Open http://62.84.119.234:9292/ and check the application.
Shut down the application:
$ docker-compose down
Stopping src_comment_1 ... done
Stopping src_db_1 ... done
Stopping src_ui_1 ... done
Stopping src_post_1 ... done
Removing src_comment_1 ... done
Removing src_db_1 ... done
Removing src_ui_1 ... done
Removing src_post_1 ... done
Removing network src_reddit
Run the application using the updated docker-compose.yml and specifying a project name.
$ docker-compose -p reddit up -d
Creating network "reddit_back_net" with the default driver
Creating network "reddit_front_net" with the default driver
Creating reddit_comment_1 ... done
Creating reddit_db_1 ... done
Creating reddit_ui_1 ... done
Creating reddit_post_1 ... done
Open http://62.84.119.234:8000/ and check the application.
Shut down the application:
$ docker-compose -p reddit down
Stopping reddit_ui_1 ... done
Stopping reddit_post_1 ... done
Stopping reddit_db_1 ... done
Stopping reddit_comment_1 ... done
Removing reddit_ui_1 ... done
Removing reddit_post_1 ... done
Removing reddit_db_1 ... done
Removing reddit_comment_1 ... done
Removing network reddit_back_net
Removing network reddit_front_net
Destroy the Docker machine:
$ docker-machine rm docker-host
About to remove docker-host
WARNING: This action will delete both local reference and remote instance.
Are you sure? (y/n): y
Successfully removed docker-host
$ yc compute instance delete docker-host
done (15s)
- Implemented Gitlab deployment.
- Added a pipeline definition.
- Started and registered a Gitlab runner.
- Added the application code to the repository.
- Added a unit test for the application.
- Defined the
reviewstage and thedevenvironment. - Defined the
stagingand theproductionstages. - Restricted the
stagingand theproductionstages to run for tags only. - Added dynamic environments for branches.
- Implemented the application container building.
- Implemented the application container testing.
- Implemented testing environment creation and the application deployment for review.
- Implemented GitLab runners creation.
- Configured GitLab integration with Slack.
Details
Deploy Gitlab:
$ cd gitlab-ci/gitlab/infra/terraform
$ terraform init
...
$ terraform apply -auto-approve
...
Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
Outputs:
gitlab_external_ip = "84.201.130.130"
$ cd ../ansible
$ ansible-playbook playbooks/site.yml
...
TASK [Show Gitlab password] **************************************************************************************
ok: [gitlab] => {
"msg": "Gitlab credentials for the first login: username: root, password: ..."
}
PLAY RECAP *******************************************************************************************************
gitlab : ok=8 changed=5 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Configure Gitlab:
- Open http://84.201.130.130/
- Login using the provided credentials.
- Go to "Edit profile" -> "Password" and change the password, as the file containing the default password will be deleted after 24 hours.
- Go to "Menu" -> "Admin" -> "Settings" -> "General" -> "Sign-up restrictions" and disable sign-up.
Useful links:
Configure a repository for the application:
- Go to "+" -> "New group" and create a new private group named "homework".
- Create a new project named "example".
- Push the application repository:
$ git remote add gitlab http://84.201.130.130/homework/example.git
$ git push gitlab gitlab-ci-1
...
Go to "CI/CD" -> "Pipelines" and check that the pipeline status is "pending".
Go to "Settings" -> "CI/CD" -> "Runners" and get the runners registration token.
Start and register a Gitlab runner:
$ ssh -i ~/.ssh/appuser ubuntu@84.201.130.130
...
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker run -d --name gitlab-runner --restart always \
-v /srv/gitlab-runner/config:/etc/gitlab-runner \
-v /var/run/docker.sock:/var/run/docker.sock \
gitlab/gitlab-runner:latest
Unable to find image 'gitlab/gitlab-runner:latest' locally
latest: Pulling from gitlab/gitlab-runner
d7bfe07ed847: Already exists
fa6bd21be6f6: Pull complete
d4a2aca7780c: Pull complete
Digest: sha256:3c00590a96d46655560b6c19b898c2b70a87213b9de48364ae4d426861db807f
Status: Downloaded newer image for gitlab/gitlab-runner:latest
59bbae83e03c946cc004a82288865a6475252d4f8d3dfb50934ad86e57f5e3eb
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker exec -it gitlab-runner gitlab-runner register \
--url http://84.201.130.130/ \
--registration-token ... \
--non-interactive \
--locked=false \
--name DockerRunner \
--executor docker \
--docker-image alpine:latest \
--tag-list "linux,xenial,ubuntu,docker" \
--run-untagged
Runtime platform arch=amd64 os=linux pid=42 revision=32fc1585 version=15.2.1
Running in system-mode.
Registering runner... succeeded runner=GR1348941JkFNu6JQ
Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!
Configuration (with the authentication token) was saved in "/etc/gitlab-runner/config.toml"
ubuntu@fhmojvm426geln1lnl5m:~$ exit
logout
Go to "CI/CD" -> "Pipelines" and check that the pipeline status is "passed".
Add the application code to the repository:
$ cd ../../../
$ git clone https://github.com/express42/reddit.git && rm -rf ./reddit/.git
...
Push the code to the Gitlab repository, then go to "Deployment" -> "Environments" and check environments.
Go to "Settings" -> "CI/CD" -> "Variables" and add the DOCKER_HUB_LOGIN and the DOCKER_HUB_PASSWD variables needed for the application image building.
Go to "Settigns" -> "CI/CD" -> "Runners" and remove the previously registered runner.
Register a GitLab runner to use the docker image and privileged mode in order to be able to build Docker images:
$ ssh -i ~/.ssh/appuser ubuntu@84.201.130.130
...
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker stop gitlab-runner
gitlab-runner
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker rm gitlab-runner
gitlab-runner
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker run -d --name gitlab-runner --restart always \
-v /srv/gitlab-runner/config:/etc/gitlab-runner \
-v /var/run/docker.sock:/var/run/docker.sock \
gitlab/gitlab-runner:latest
1cb8f35f7242658d717803861255ee59e949212cfdbe80e47c8cc04ec86434b0
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker exec -it gitlab-runner gitlab-runner register \
--url http://84.201.130.130/ \
--registration-token ... \
--docker-privileged \
--non-interactive \
--locked=false \
--name DockerRunner \
--executor docker \
--docker-image docker:19.03.1 \
--tag-list "linux,xenial,ubuntu,docker" \
--run-untagged
Runtime platform arch=amd64 os=linux pid=29 revision=32fc1585 version=15.2.1
Running in system-mode.
Registering runner... succeeded runner=GR1348941JkFNu6JQ
Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!
Configuration (with the authentication token) was saved in "/etc/gitlab-runner/config.toml"
ubuntu@fhmojvm426geln1lnl5m:~$ exit
logout
Push the code to the Gitlab repository, then go to Docker Hub and check the built application image.
Useful links:
- Use Docker to build Docker images
- Update: Changes to GitLab CI/CD and Docker in Docker with Docker 19.03
Create a bucket for the terraform state storage:
$ cd gitlab-ci/gitlab/infra/terraform
$ terraform apply -auto-approve
...
Go to "Settings" -> "CI/CD" -> "Variables" and add the YC_OAUTH_TOKEN, YC_CLOUD_ID, YC_FOLDER_ID, YC_SUBNET_ID, YC_STATE_BUCKET_ACCESS_KEY, and YC_STATE_BUCKET_SECRET_KEY variables needed for testing environments creation.
Push a new branch to the Gitlab repository, then go to "Deployment" -> "Environments" and check the environment created for the branch.
Useful links:
Go to "Settigns" -> "CI/CD" -> "Runners" and remove the previously registered runner.
Stop the existing GitLab runner:
$ ssh -i ~/.ssh/appuser ubuntu@84.201.130.130
...
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker stop gitlab-runner
gitlab-runner
ubuntu@fhmojvm426geln1lnl5m:~$ sudo docker rm gitlab-runner
gitlab-runner
ubuntu@fhmojvm426geln1lnl5m:~$ exit
logout
Create and register new GitLab runners using Ansible playbook:
$ cd gitlab-ci/gitlab/infra/ansible
$ ansible-playbook playbooks/site.yml --extra-vars "runner_token=... runners_count=2" --tags create_runners
...
PLAY RECAP *******************************************************************************************************
gitlab : ok=2 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Go to "Settings" -> "Integrations" -> "Slack notifications" and configure Slack integration.
You can check GitLab notifications here.
- Got acquainted with Prometheus.
- Built a Prometheus Docker image to monitor the application.
- Added Prometheus service to the
docker/docker-compose.ymlfile. - Added node-exporter for host machine monitoring.
- Pushed the created application images to DockerHub.
- Implemented MongoDB monitoring using mongodb-exporter.
- Implemented Blackbox monitoring using blackbox-exporter.
- Added
Makefileto automate various actions.
Details
Create a Docker machine on a Yandex.Cloud VM:
$ yc compute instance create \
--name docker-host \
--zone ru-central1-a \
--network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
--create-boot-disk image-folder-id=standard-images,image-family=ubuntu-1804-lts,size=15 \
--ssh-key ~/.ssh/appuser.pub
done (21s)
id: fhmhfgr7hb4c9hepr9d3
...
network_interfaces:
- index: "0"
mac_address: d0:0d:11:7c:36:78
subnet_id: e9bqom95bd1o3fkemarr
primary_v4_address:
address: 10.128.0.4
one_to_one_nat:
address: 51.250.93.5
ip_version: IPV4
...
$ docker-machine create \
--driver generic \
--generic-ip-address=51.250.93.5 \
--generic-ssh-user yc-user \
--generic-ssh-key ~/.ssh/appuser \
docker-host
Running pre-create checks...
Creating machine...
(docker-host) Importing SSH key...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env docker-host
$ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docker-host * generic Running tcp://51.250.93.5:2376 v20.10.17
$ docker-machine ip docker-host
51.250.93.5
$ eval $(docker-machine env docker-host)
Run Prometheus:
$ docker run --name prometheus --rm -d -p 9090:9090 prom/prometheus
Unable to find image 'prom/prometheus:latest' locally
latest: Pulling from prom/prometheus
...
Status: Downloaded newer image for prom/prometheus:latest
8086c215b74860d75273a383d694d65525df1a3674c2d8ac88ee852e4c27b03b
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8086c215b748 prom/prometheus "/bin/prometheus --cβ¦" 15 seconds ago Up 12 seconds 0.0.0.0:9090->9090/tcp, :::9090->9090/tcp prometheus
Open http://51.250.93.5:9090/ and get acquainted with Prometheus.
Stop Prometheus:
$ docker stop prometheus
prometheus
Build a Prometheus Docker image to monitor the application:
$ cd monitoring/prometheus
$ export USERNAME=vshender
$ docker build -t $USERNAME/prometheus .
...
Build the application microservice images:
$ cd ../../
$ for srv in ui post-py comment; do cd src/$srv; USER_NAME=$USERNAME bash docker_build.sh; cd -; done
...
Run the application:
$ cd docker
$ cp .env.example .env
$ docker-compose up -d
[+] Running 7/7
β Ώ Network docker_front_net Created 0.1s
β Ώ Network docker_back_net Created 0.1s
β Ώ Container docker-db-1 Started 2.3s
β Ώ Container docker-post-1 Started 3.8s
β Ώ Container docker-ui-1 Started 3.4s
β Ώ Container docker-comment-1 Started 4.7s
β Ώ Container docker-prometheus-1 Started
...
- Open http://51.250.93.5:9292/ and check the application.
- Open http://51.250.93.5:9090/ adn check the Prometheus.
Rebuild the Prometheus Docker image with the node-exporter configuration added:
$ cd ../monitoring/prometheus
$ docker build -t $USERNAME/prometheus .
...
Rerun the application:
$ cd ../../docker
$ docker-compose down
[+] Running 7/7
β Ώ Container docker-post-1 Removed 2.9s
β Ώ Container docker-prometheus-1 Removed 3.0s
β Ώ Container docker-ui-1 Removed 2.3s
β Ώ Container docker-db-1 Removed 2.1s
β Ώ Container docker-comment-1 Removed 3.0s
β Ώ Network docker_front_net Removed 0.1s
β Ώ Network docker_back_net Removed 0.1s
$ docker-compose up -d
[+] Running 8/8
β Ώ Network docker_back_net Created 0.1s
β Ώ Network docker_front_net Created 0.1s
β Ώ Container docker-db-1 Started 3.0s
β Ώ Container docker-post-1 Started 4.9s
β Ώ Container docker-node-exporter-1 Started 2.2s
β Ώ Container docker-comment-1 Started 3.7s
β Ώ Container docker-ui-1 Started 4.1s
β Ώ Container docker-prometheus-1 Started 2.7s
-
Open http://51.250.93.5:9090/targets and check the node-exporter target.
-
Check the
node_load1metric: http://51.250.93.5:9090/graph?g0.range_input=1h&g0.expr=node_load1&g0.tab=0. -
Add load:
$ docker-machine ssh docker-host ... yc-user@docker-host:~$ yes > /dev/null ^C yc-user@docker-host:~$ exit logout -
Check the
node_load1metric again.
Push the created application images to DockerHub:
$ docker login
Authenticating with existing credentials...
Login Succeeded
...
$ for image in ui comment post prometheus; do docker push $USERNAME/$image; done
...
DockerHub profile: https://hub.docker.com/u/vshender.
Build the mongodb-exporter image:
$ cd ../monitoring/mongodb
$ docker build -t $USERNAME/mongodb-exporter .
...
Rebuild the Prometheus Docker image with the mongodb-exporter configuration added:
$ cd ../prometheus
$ docker build -t $USERNAME/prometheus .
...
Rerun the application:
$ cd ../../docker
$ docker-compose down
[+] Running 8/8
β Ώ Container docker-comment-1 Removed 1.9s
β Ώ Container docker-prometheus-1 Removed 2.5s
β Ώ Container docker-post-1 Removed 2.4s
β Ώ Container docker-node-exporter-1 Removed 1.9s
β Ώ Container docker-db-1 Removed 1.7s
β Ώ Container docker-ui-1 Removed 2.5s
β Ώ Network docker_front_net Removed 0.1s
$ docker-compose up -d
[+] Running 9/9
β Ώ Network docker_back_net Created 0.1s
β Ώ Network docker_front_net Created 0.1s
β Ώ Container docker-ui-1 Started 3.0s
β Ώ Container docker-prometheus-1 Started 3.2s
β Ώ Container docker-db-1 Started 4.8s
β Ώ Container docker-node-exporter-1 Started 3.4s
β Ώ Container docker-post-1 Started 6.6s
β Ώ Container docker-comment-1 Started 5.5s
β Ώ Container docker-mongodb-exporter-1 Started 4.2s
Open http://51.250.93.5:9090/targets and check the mongodb-exporter target.
Build the blackbox-exporter image:
$ cd ../monitoring/blackbox
$ docker build -t $USERNAME/blackbox-exporter .
...
Rebuild the Prometheus Docker image with the blackbox-exporter configuration added:
$ cd ../prometheus
$ docker build -t $USERNAME/prometheus .
...
Rerun the application:
$ cd ../../docker
$ docker-compose down
[+] Running 9/9
β Ώ Container docker-db-1 Removed 1.5s
β Ώ Container docker-ui-1 Removed 1.2s
β Ώ Container docker-post-1 Removed 2.1s
β Ώ Container docker-comment-1 Removed 2.1s
β Ώ Container docker-node-exporter-1 Removed 1.1s
β Ώ Container docker-prometheus-1 Removed 1.8s
β Ώ Container docker-mongodb-exporter-1 Removed 1.0s
β Ώ Network docker_front_net Removed 0.1s
β Ώ Network docker_back_net Removed 0.1s
$ docker-compose up -d
[+] Running 10/10
β Ώ Network docker_back_net Created 0.1s
β Ώ Network docker_front_net Created 0.3s
β Ώ Container docker-db-1 Started 2.1s
β Ώ Container docker-blackbox-exporter-1 Started 2.6s
β Ώ Container docker-ui-1 Started 4.8s
β Ώ Container docker-post-1 Started 4.3s
β Ώ Container docker-comment-1 Started 5.6s
β Ώ Container docker-prometheus-1 Started 3.5s
β Ώ Container docker-node-exporter-1 Started 3.0s
β Ώ Container docker-mongodb-exporter-1 Started 6.6s
Open http://51.250.93.5:9090/targets and check the blackbox-exporter target.
Destroy the Docker machine:
$ docker-machine rm docker-host
About to remove docker-host
WARNING: This action will delete both local reference and remote instance.
Are you sure? (y/n): y
Successfully removed docker-host
$ yc compute instance delete docker-host
done (14s)
- Updated the application code.
- Created a Docker machine on a Yandex.Cloud VM.
- Built a fluentd image.
- Ran the application using the updated application images.
- Used fluentd logging driver for the
postmicroservice. - Added fluentd filter in order to parse
logfield ofpostlogs. - Used fluentd logging driver for the
uimicroservice. - Added fluentd filter in order to parse unstructured
uilogs. - Used grok patterns for unstructured
uilogs parsing. - Implemented tracing using Zipkin.
- Analyzed the bugged application using Zipkin. The
find_postmethod of thepostmicroservice contains atime.sleepcall.
Details
Build the application images with the updated code and push them to DockerHub:
$ make build
...
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
vshender/post logging 7c6673f5424f About a minute ago 107MB
vshender/comment logging 5d35a3a0218d 5 minutes ago 67.4MB
vshender/ui logging 10402a268405 8 minutes ago 67.3MB
...
$ make push
...
Create a Docker machine on a Yandex.Cloud VM:
$ yc compute instance create \
--name logging \
--zone ru-central1-a \
--network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
--create-boot-disk image-folder-id=standard-images,image-family=ubuntu-1804-lts,size=15 \
--memory 4 \
--ssh-key ~/.ssh/appuser.pub
done (18s)
id: fhmrfnngep220ofl957l
...
one_to_one_nat:
address: 51.250.92.236
ip_version: IPV4
...
$ docker-machine create \
--driver generic \
--generic-ip-address=51.250.92.236 \
--generic-ssh-user yc-user \
--generic-ssh-key ~/.ssh/appuser \
logging
...
$ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
logging - generic Running tcp://51.250.92.236:2376 v20.10.17
$ docker-machine ip logging
51.250.92.236
$ eval $(docker-machine env docker-host)
Build a fluentd image:
$ cd logging/fluentd
$ docker build -t $USERNAME/fluentd .
...
Successfully built 4e485cf07051
Successfully tagged vshender/fluentd:latest
Run the application and look at the post microservice logs:
$ cd ../../docker
$ docker-compose up -d
[+] Running 12/12
β Ώ Network docker_back_net Created 0.1s
β Ώ Network docker_front_net Created 0.1s
β Ώ Volume "docker_post_db" Created 0.0s
β Ώ Volume "docker_prometheus_data" Created 0.0s
β Ώ Container docker-comment-1 Started 7.4s
β Ώ Container docker-db-1 Started 7.9s
β Ώ Container docker-post-1 Started 6.7s
β Ώ Container docker-node-exporter-1 Started 8.7s
β Ώ Container docker-ui-1 Started 7.1s
β Ώ Container docker-blackbox-exporter-1 Started 5.4s
β Ώ Container docker-mongodb-exporter-1 Started 6.3s
β Ώ Container docker-prometheus-1 Started 9.2s
$ docker-compose logs -f post
docker-post-1 | {"addr": "192.168.80.3", "event": "request", "level": "info", "method": "GET", "path": "/healthcheck?", "request_id": null, "response_status": 200, "service": "post", "timestamp": "2022-08-13 09:39:45"}
docker-post-1 | {"addr": "192.168.80.3", "event": "request", "level": "info", "method": "GET", "path": "/healthcheck?", "request_id": null, "response_status": 200, "service": "post", "timestamp": "2022-08-13 09:39:50"}
...
docker-post-1 | {"event": "find_all_posts", "level": "info", "message": "Successfully retrieved all posts from the database", "params": {}, "request_id": "d340ecb8-ecef-4bf5-8cb3-df631a77562b", "service": "post", "timestamp": "2022-08-13 09:40:14"}
docker-post-1 | {"addr": "192.168.80.3", "event": "request", "level": "info", "method": "GET", "path": "/posts?", "request_id": "d340ecb8-ecef-4bf5-8cb3-df631a77562b", "response_status": 200, "service": "post", "timestamp": "2022-08-13 09:40:14"}
docker-post-1 | {"addr": "192.168.80.3", "event": "request", "level": "info", "method": "GET", "path": "/healthcheck?", "request_id": "d340ecb8-ecef-4bf5-8cb3-df631a77562b", "response_status": 200, "service": "post", "timestamp": "2022-08-13 09:40:15"}
...
docker-post-1 | {"event": "post_create", "level": "info", "message": "Successfully created a new post", "params": {"link": "https://pandadoc.com", "title": "PandaDoc"}, "request_id": "387f5fd6-9982-4dd9-a3ad-fdc6a42dd7af", "service": "post", "timestamp": "2022-08-13 09:40:53"}
...
Run the logging infrastructure and restart the application in order to send post logs to fluentd:
$ docker-compose -f docker-compose-logging.yml up -d
[+] Running 18/18
β Ώ kibana Pulled 55.5s
β Ώ d8d02d457314 Pull complete 7.6s
β Ώ a2a6340cc578 Pull complete 15.9s
β Ώ bee982052bff Pull complete 17.2s
β Ώ ee697e306b93 Pull complete 17.8s
β Ώ 1b9dfb8cf65d Pull complete 49.5s
β Ώ bf2fd386ca4c Pull complete 49.6s
β Ώ 09854d164e14 Pull complete 49.7s
β Ώ 57db629d98b8 Pull complete 49.8s
β Ώ 3de4bbd85ab2 Pull complete 49.9s
β Ώ 9503e61c9325 Pull complete 51.4s
β Ώ elasticsearch Pulled 38.3s
β Ώ a0fe4757966a Pull complete 16.6s
β Ώ af323c430ce5 Pull complete 17.7s
β Ώ 2a71ef3bd98b Pull complete 34.5s
β Ώ 1e56fdd350c5 Pull complete 34.7s
β Ώ 16d320661b98 Pull complete 35.4s
[+] Running 0/0
[+] Running 4/4er_default Creating 0.0s
β Ώ Network docker_default Created 0.1s
β Ώ Container docker-elasticsearch-1 Started 4.3s
β Ώ Container docker-kibana-1 Started 3.5s
β Ώ Container docker-fluentd-1 Started 4.6s
$ docker-compose down
[+] Running 10/10
β Ώ Container docker-blackbox-exporter-1 Removed 1.6s
β Ώ Container docker-db-1 Removed 1.7s
β Ώ Container docker-prometheus-1 Removed 2.3s
β Ώ Container docker-ui-1 Removed 1.2s
β Ώ Container docker-post-1 Removed 2.4s
β Ώ Container docker-node-exporter-1 Removed 1.7s
β Ώ Container docker-mongodb-exporter-1 Removed 1.6s
β Ώ Container docker-comment-1 Removed 2.4s
β Ώ Network docker_back_net Removed 0.1s
β Ώ Network docker_front_net Removed 0.1s
$ docker-compose up -d
[+] Running 10/10_front_net Created 0.1s
β Ώ Network docker_front_net Created 0.1s
β Ώ Network docker_back_net Created 0.1s
β Ώ Container docker-comment-1 Started 4.1s
β Ώ Container docker-blackbox-exporter-1 Started 6.0s
β Ώ Container docker-node-exporter-1 Started 3.3s
β Ώ Container docker-mongodb-exporter-1 Started 2.4s
β Ώ Container docker-ui-1 Started 3.9s
β Ώ Container docker-prometheus-1 Started 5.1s
β Ώ Container docker-db-1 Started 3.0s
β Ώ Container docker-post-1 Started 5.6s
- Open http://51.250.92.236:9292/ and create several posts in order to produce some logs.
- Open http://51.250.92.236:5601/, go to "Discover" -> "Index Patterns", and click "Create index pattern".
- Enter "fluentd-* in the "Index pattern name" field and click "Next step".
- Set "@timestamp" as a value of the "Time field" and click "Create index pattern".
- Go to "Discover" and look at logs.
Rebuild the fluentd image and restart fluentd:
$ cd ../logging/fluentd
$ docker build -t $USERNAME/fluentd .
...
$ cd ../../docker
$ docker-compose -f docker-compose-logging.yml up -d fluentd
[+] Running 1/1
β Ώ Container docker-fluentd-1 Started 3.9s
- Open http://51.250.92.236:9292/ and create several posts in order to produce some logs.
- Open http://51.250.92.236:5601/, go to "Discover", and look at the logs.
- Now you can filter, for example, by event type: "event: post_create".
Restart the ui microservice:
$ docker-compose up -d
...
- Open http://51.250.92.236:9292/ and perform several actions in order to produce some logs.
- Open http://51.250.92.236:5601/, go to "Discover", enter the "container_name: ui" query, and check that log messages from
uiare unstructured.
Rebuild the fluentd image and restart fluentd:
$ cd ../logging/fluentd
$ docker build -t $USERNAME/fluentd .
...
$ cd ../../docker
$ docker-compose -f docker-compose-logging.yml up -d fluentd
[+] Running 1/1
β Ώ Container docker-fluentd-1 Started 5.3s
- Open http://51.250.92.236:9292/ and perform several actions in order to produce some logs.
- Open http://51.250.92.236:5601/, go to "Discover", enter the "@log_name: service.ui" query, and check that log messages from
uiare now structured.
Rebuild the fluentd image and restart fluentd:
$ cd ../logging/fluentd
$ docker build -t $USERNAME/fluentd .
...
$ cd ../../docker
$ docker-compose -f docker-compose-logging.yml up -d fluentd
[+] Running 1/1
β Ώ Container docker-fluentd-1 Started 4.5s
- Open http://51.250.92.236:9292/ and perform several actions in order to produce some logs.
- Open http://51.250.92.236:5601/, go to "Discover", and check that grok pattens parse logs properly.
Useful links:
Restart the logging infrastructure and the application in order to enable tracing:
$ docker-compose -f docker-compose-logging.yml up -d
[+] Running 13/13
β Ώ zipkin Pulled 10.8s
β Ώ 24f0c933cbef Pull complete 0.9s
β Ώ 69e2f037cdb3 Pull complete 1.6s
β Ώ 1a3f070d750b Pull complete 2.0s
β Ώ 3e010093287c Pull complete 2.4s
β Ώ 7df9dcce0a60 Pull complete 2.6s
β Ώ 824016db13c8 Pull complete 2.9s
β Ώ fd2668db6e0d Pull complete 3.0s
β Ώ 6453a70a5672 Pull complete 5.2s
β Ώ 71ee7774b52d Pull complete 5.7s
β Ώ 89855adca250 Pull complete 5.9s
β Ώ fa57359ed425 Pull complete 7.8s
β Ώ 092e376cad15 Pull complete 7.9s
[+] Running 4/4
β Ώ Container docker-zipkin-1 Started 2.7s
β Ώ Container docker-kibana-1 Running 0.0s
β Ώ Container docker-elasticsearch-1 Running 0.0s
β Ώ Container docker-fluentd-1 Running 0.0s
$ docker-compose up -d
[+] Running 8/8
β Ώ Container docker-db-1 Running 0.0s
β Ώ Container docker-mongodb-exporter-1 Running 0.0s
β Ώ Container docker-blackbox-exporter-1 Running 0.0s
β Ώ Container docker-prometheus-1 Running 0.0s
β Ώ Container docker-node-exporter-1 Running 0.0s
β Ώ Container docker-ui-1 Started 8.6s
β Ώ Container docker-comment-1 Started 9.6s
β Ώ Container docker-post-1 Started 10.6s
- Open http://51.250.92.236:9292/ and refresh the page several times.
- Open http://51.250.92.236:9411/ and look at traces.
Destroy the Docker machine:
$ docker-machine rm logging
About to remove logging
WARNING: This action will delete both local reference and remote instance.
Are you sure? (y/n): y
Successfully removed logging
$ yc compute instance delete logging
done (26s)
- Added Kubernetes manifests for the application.
- Deployed Kubernetes.
- Deployed Kubernetes using Terraform and Ansible.
Details
Create VMs for Kubernetes:
$ yc compute instance create \
--name k8s-master \
--zone ru-central1-a \
--network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
--create-boot-disk image-folder-id=standard-images,image-family=ubuntu-2204-lts,size=40 \
--cores 4 \
--memory 4 \
--ssh-key ~/.ssh/appuser.pub
...
one_to_one_nat:
address: 51.250.67.222
ip_version: IPV4
...
$ yc compute instance create \
--name k8s-worker \
--zone ru-central1-a \
--network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
--create-boot-disk image-folder-id=standard-images,image-family=ubuntu-1804-lts,size=40 \
--cores 4 \
--memory 4 \
--ssh-key ~/.ssh/appuser.pub
...
one_to_one_nat:
address: 51.250.87.182
ip_version: IPV4
...
Install Docker on the created nodes:
$ ssh -i ~/.ssh/appuser yc-user@51.250.67.222
...
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo apt update && sudo apt install -y apt-transport-https ca-certificates curl
...
yc-user@fhmja07lrbaa1ida6rnp:~$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
yc-user@fhmja07lrbaa1ida6rnp:~$ echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo apt-get update && sudo apt install -y docker-ce docker-ce-cli containerd.io
yc-user@fhmja07lrbaa1ida6rnp:~$ exit
logout
$ ssh -i ~/.ssh/appuser yc-user@51.250.87.182
...
yc-user@fhmj0766iu802i9bp78m:~$ sudo apt update && sudo apt install -y apt-transport-https ca-certificates curl
...
yc-user@fhmj0766iu802i9bp78m:~$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
yc-user@fhmj0766iu802i9bp78m:~$ echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
yc-user@fhmj0766iu802i9bp78m:~$ sudo apt-get update && sudo apt install docker-ce docker-ce-cli containerd.io -y
...
yc-user@fhmj0766iu802i9bp78m:~$ exit
logout
Install Kubernetes on the created nodes:
$ ssh -i ~/.ssh/appuser yc-user@51.250.67.222
...
yc-user@fhmja07lrbaa1ida6rnp:~$ curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -o /usr/share/keyrings/k8s-archive-keyring.gpg
yc-user@fhmja07lrbaa1ida6rnp:~$ echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/k8s-archive-keyring.gpg] http://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/k8s.list > /dev/null
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo apt update && sudo apt install -y kubelet kubeadm kubectl
...
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo apt-mark hold kubelet kubeadm kubectl
kubelet set on hold.
kubeadm set on hold.
kubectl set on hold.
yc-user@fhmja07lrbaa1ida6rnp:~$ containerd config default | sudo tee /etc/containerd/config.toml > /dev/null 2>&1
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo sed -i 's/SystemdCgroup \= false/SystemdCgroup \= true/g' /etc/containerd/config.toml
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo systemctl restart containerd
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo systemctl enable containerd
yc-user@fhmja07lrbaa1ida6rnp:~$ exit
logout
$ ssh -i ~/.ssh/appuser yc-user@51.250.87.182
...
yc-user@fhmj0766iu802i9bp78m:~$ curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -o /usr/share/keyrings/k8s-archive-keyring.gpg
yc-user@fhmj0766iu802i9bp78m:~$ echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/k8s-archive-keyring.gpg] http://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/k8s.list > /dev/null
yc-user@fhmj0766iu802i9bp78m:~$ sudo apt update && sudo apt install -y kubelet kubeadm kubectl
...
yc-user@fhmj0766iu802i9bp78m:~$ containerd config default | sudo tee /etc/containerd/config.toml > /dev/null 2>&1
yc-user@fhmj0766iu802i9bp78m:~$ sudo sed -i 's/SystemdCgroup \= false/SystemdCgroup \= true/g' /etc/containerd/config.toml
yc-user@fhmj0766iu802i9bp78m:~$ sudo systemctl restart containerd
yc-user@fhmj0766iu802i9bp78m:~$ sudo systemctl enable containerd
yc-user@fhmlribunv8eqphcamlk:~$ exit
logout
Initialize Kubernetes cluster on the master node:
$ ssh -i ~/.ssh/appuser yc-user@51.250.67.222
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo kubeadm init --apiserver-cert-extra-sans=51.250.67.222 \
--apiserver-advertise-address=0.0.0.0 \
--control-plane-endpoint=51.250.67.222 \
--pod-network-cidr=10.244.0.0/16
...
Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run:
export KUBECONFIG=/etc/kubernetes/admin.conf
You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
You can now join any number of control-plane nodes by copying certificate authorities
and service account keys on each node and then running the following as root:
kubeadm join 51.250.67.222:6443 --token z8ytqi.ezf3m1goe8i8ao89 \
--discovery-token-ca-cert-hash sha256:16adbfc10cb9cbbed5a4fd89e40fde045a89179b25d9d365fe246d5536995cf8 \
--control-plane
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 51.250.67.222:6443 --token z8ytqi.ezf3m1goe8i8ao89 \
--discovery-token-ca-cert-hash sha256:16adbfc10cb9cbbed5a4fd89e40fde045a89179b25d9d365fe246d5536995cf8
yc-user@fhmja07lrbaa1ida6rnp:~$ mkdir -p $HOME/.kube
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
yc-user@fhmja07lrbaa1ida6rnp:~$ sudo chown $(id -u):$(id -g) $HOME/.kube/config
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl cluster-info
Kubernetes control plane is running at https://51.250.67.222:6443
CoreDNS is running at https://51.250.67.222:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
fhmja07lrbaa1ida6rnp NotReady control-plane 18m v1.25.0
yc-user@fhmja07lrbaa1ida6rnp:~$ exit
logout
Join a worker node:
$ ssh -i ~/.ssh/appuser yc-user@51.250.87.182
...
yc-user@fhmj0766iu802i9bp78m:~$ sudo kubeadm join 51.250.67.222:6443 --token z8ytqi.ezf3m1goe8i8ao89 \
--discovery-token-ca-cert-hash sha256:16adbfc10cb9cbbed5a4fd89e40fde045a89179b25d9d365fe246d5536995cf8
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.
Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
yc-user@fhmj0766iu802i9bp78m:~$ exit
logout
Install Calico Pod Network Add-on on the master node:
$ ssh -i ~/.ssh/appuser yc-user@51.250.67.222
...
yc-user@fhmja07lrbaa1ida6rnp:~$ curl https://projectcalico.docs.tigera.io/manifests/calico.yaml -O
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 229k 100 229k 0 0 563k 0 --:--:-- --:--:-- --:--:-- 563k
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl apply -f calico.yaml
poddisruptionbudget.policy/calico-kube-controllers created
serviceaccount/calico-kube-controllers created
serviceaccount/calico-node created
configmap/calico-config created
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/caliconodestatuses.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipreservations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created
clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrole.rbac.authorization.k8s.io/calico-node created
clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrolebinding.rbac.authorization.k8s.io/calico-node created
daemonset.apps/calico-node created
Verify the status of pods in kube-system namespace and check the nodes status:
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-7bdf4bf59d-q9vf2 0/1 ContainerCreating 0 25s
calico-node-p4tsl 0/1 Init:2/3 0 25s
calico-node-z4dkh 0/1 Init:2/3 0 25s
coredns-565d847f94-5bkzv 0/1 ContainerCreating 0 53m
coredns-565d847f94-kbhwp 0/1 ContainerCreating 0 53m
etcd-fhmja07lrbaa1ida6rnp 1/1 Running 0 54m
kube-apiserver-fhmja07lrbaa1ida6rnp 1/1 Running 0 54m
kube-controller-manager-fhmja07lrbaa1ida6rnp 1/1 Running 0 54m
kube-proxy-4d6v9 1/1 Running 0 19m
kube-proxy-sbcms 1/1 Running 0 53m
kube-scheduler-fhmja07lrbaa1ida6rnp 1/1 Running 0 54m
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
fhmj0766iu802i9bp78m Ready <none> 19m v1.25.0
fhmja07lrbaa1ida6rnp Ready control-plane 55m v1.25.0
yc-user@fhmja07lrbaa1ida6rnp:~$ exit
logout
Apply the application manifests:
$ scp -i ~/.ssh/appuser -r kubernetes/reddit yc-user@51.250.67.222:/home/yc-user
...
$ ssh -i ~/.ssh/appuser yc-user@51.250.67.222
...
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl apply -f reddit/mongo-deployment.yml
deployment.apps/mongo-deployment created
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl apply -f reddit/post-deployment.yml
deployment.apps/post-deployment created
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl apply -f reddit/comment-deployment.yml
deployment.apps/comment-deployment created
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl apply -f reddit/ui-deployment.yml
deployment.apps/ui-deployment created
yc-user@fhmja07lrbaa1ida6rnp:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
comment-deployment-7b567f8548-lxqwn 1/1 Running 0 48s
mongo-deployment-7547584d88-k5pdm 1/1 Running 0 69s
post-deployment-745d9777d4-chdng 1/1 Running 0 59s
ui-deployment-666c9c944d-97qpt 1/1 Running 0 40s
yc-user@fhmja07lrbaa1ida6rnp:~$ exit
logout
Destroy the VMs:
$ yc compute instance list
+----------------------+------------+---------------+---------+---------------+-------------+
| ID | NAME | ZONE ID | STATUS | EXTERNAL IP | INTERNAL IP |
+----------------------+------------+---------------+---------+---------------+-------------+
| fhmj0766iu802i9bp78m | k8s-worker | ru-central1-a | RUNNING | 51.250.87.182 | 10.128.0.20 |
| fhmja07lrbaa1ida6rnp | k8s-master | ru-central1-a | RUNNING | 51.250.67.222 | 10.128.0.10 |
+----------------------+------------+---------------+---------+---------------+-------------+
$ yc compute instance delete fhmj0766iu802i9bp78m
done (18s)
$ yc compute instance delete fhmja07lrbaa1ida6rnp
done (14s)
Useful links:
- How to Install Docker on Ubuntu 22.04 / 20.04 LTS
- How to Install Kubernetes Cluster on Ubuntu 22.04
- Install Calico networking and network policy for on-premises deployments
- Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead
Create a Kubernetes cluster using Terraform and Ansible:
$ cd kubernetes/terraform
$ terraform init
...
$ terraform apply -auto-approve
...
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
Outputs:
k8s_master_external_ip = "84.201.129.45"
k8s_worker_external_ip = "84.201.133.30"
$ cd ../ansible
$ ansible-galaxy install -r requirements.yml
...
$ ansible-playbook playbooks/site.yml
...
PLAY RECAP *******************************************************************************************************
k8s-master : ok=25 changed=21 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
k8s-worker : ok=19 changed=14 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Check the created cluster:
$ ssh -i ~/.ssh/appuser ubuntu@84.201.129.45
...
ubuntu@fhmiq2dui6ok8d6nkm4o:~$ kubectl cluster-info
Kubernetes control plane is running at https://84.201.129.45:6443
CoreDNS is running at https://84.201.129.45:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
ubuntu@fhmiq2dui6ok8d6nkm4o:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
fhmiq2dui6ok8d6nkm4o Ready control-plane 77m v1.25.0
fhmklbk7p5jpd55nmj5i Ready <none> 22m v1.25.0
ubuntu@fhmiq2dui6ok8d6nkm4o:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
comment-deployment-7b567f8548-l54cm 1/1 Running 0 41s
mongo-deployment-7547584d88-cp4lx 1/1 Running 0 3m34s
post-deployment-745d9777d4-tj8zd 1/1 Running 0 49s
ui-deployment-666c9c944d-g2j7w 1/1 Running 0 33s
ubuntu@fhmiq2dui6ok8d6nkm4o:~$ exit
logout
Destory the created cluster:
$ cd ../terraform
$ terraform destroy -auto-approve
...
- Started a local Kubernetes cluster using minikube.
- Started the application in the minikube cluster.
- Started minikube dashboard.
- Created the
devnamespace. - Started the application in a Yandex.Cloud managed Kubernetes cluster.
- Created a Yandex.Cloud managed Kubernetes cluster using Terraform.
Details
Start a local Kubernetes cluster using minikube:
$ minikube start --cpus=6 --memory=6g --vm-driver=virtualbox
π minikube v1.26.1 on Darwin 12.5.1
π Kubernetes 1.24.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.24.3
β¨ Using the virtualbox driver based on existing profile
πΏ Downloading VM boot image ...
> minikube-v1.26.1-amd64.iso....: 65 B / 65 B [---------] 100.00% ? p/s 0s
> minikube-v1.26.1-amd64.iso: 270.83 MiB / 270.83 MiB 100.00% 1.33 MiB p/
π Starting control plane node minikube in cluster minikube
πΎ Downloading Kubernetes v1.23.3 preload ...
> preloaded-images-k8s-v18-v1...: 400.43 MiB / 400.43 MiB 100.00% 1.05 Mi
π Restarting existing virtualbox VM for "minikube" ...
π³ Preparing Kubernetes v1.23.3 on Docker 20.10.12 ...
βͺ kubelet.housekeeping-interval=5m
βͺ Using image gcr.io/k8s-minikube/storage-provisioner:v5
βͺ Using image k8s.gcr.io/ingress-nginx/controller:v1.1.1
βͺ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
βͺ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1
π Verifying Kubernetes components...
π Verifying ingress addon...
π Enabled addons: storage-provisioner, default-storageclass, ingress
β /usr/local/bin/kubectl is version 1.25.0, which may have incompatibilites with Kubernetes 1.23.3.
βͺ Want kubectl v1.23.3? Try 'minikube kubectl -- get pods -A'
π Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready control-plane,master 107d v1.23.3
$ cat ~/.kube/config
apiVersion: v1
clusters:
- cluster:
certificate-authority: /Users/vshender/.minikube/ca.crt
extensions:
- extension:
last-update: Sat, 27 Aug 2022 23:07:51 +03
provider: minikube.sigs.k8s.io
version: v1.26.1
name: cluster_info
server: https://192.168.59.101:8443
name: minikube
contexts:
- context:
cluster: minikube
extensions:
- extension:
last-update: Sat, 27 Aug 2022 23:07:51 +03
provider: minikube.sigs.k8s.io
version: v1.26.1
name: context_info
namespace: default
user: minikube
name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
user:
client-certificate: /Users/vshender/.minikube/profiles/minikube/client.crt
client-key: /Users/vshender/.minikube/profiles/minikube/client.key
$ kubectl config current-context
minikube
$ kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
* minikube minikube minikube default
Start the ui deployment:
$ cd kubernetes/reddit
$ kubectl apply -f ui-deployment.yml
deployment.apps/ui created
$ kubectl get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
ui 3/3 3 3 2m50s
$ kubectl get pods --selector component=ui
NAME READY STATUS RESTARTS AGE
ui-5df8d9f844-d7m74 1/1 Running 0 10m
ui-5df8d9f844-f6227 1/1 Running 0 10m
ui-5df8d9f844-gxdft 1/1 Running 0 10m
$ kubectl port-forward ui-5df8d9f844-d7m74 8080:9292
Forwarding from 127.0.0.1:8080 -> 9292
Forwarding from [::1]:8080 -> 9292
Handling connection for 8080
...
Open http://localhost:8080/ and check the ui component.
Start the comment service:
$ kubectl apply -f comment-deployment.yml
deployment.apps/comment created
$ kubectl apply -f comment-service.yml
service/comment created
$ kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
comment ClusterIP 10.98.27.148 <none> 9292/TCP 6s
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 107d
$ kubectl describe service comment | grep Endpoints
Endpoints: 172.17.0.7:9292,172.17.0.8:9292,172.17.0.9:9292
$ kubectl exec -it ui-5df8d9f844-d7m74 -- nslookup comment
Server: 10.96.0.10
Address: 10.96.0.10:53
** server can't find comment.cluster.local: NXDOMAIN
Name: comment.default.svc.cluster.local
Address: 10.101.78.94
...
Start the whole application:
$ kubectl apply \
-f comment-deployment.yml \
-f comment-mongodb-service.yml \
-f comment-service.yml \
-f mongo-deployment.yml \
-f mongo-service.yml \
-f post-deployment.yml \
-f post-mongodb-service.yml \
-f post-service.yml \
-f ui-deployment.yml
deployment.apps/comment unchanged
service/comment-db created
service/comment unchanged
deployment.apps/mongo created
service/mongodb created
deployment.apps/post created
service/post-db created
service/post created
deployment.apps/ui unchanged
$ kubectl port-forward ui-5df8d9f844-d7m74 8080:9292
Forwarding from 127.0.0.1:8080 -> 9292
Forwarding from [::1]:8080 -> 9292
Handling connection for 8080
Open http://localhost:8080/ and check the application.
Start the ui service that uses NodePort:
$ kubectl apply -f ui-service.yml
service/ui created
; minikube service list
|---------------|------------------------------------|--------------|-----------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|---------------|------------------------------------|--------------|-----------------------------|
| default | comment | No node port |
| default | comment-db | No node port |
| default | kubernetes | No node port |
| default | mongodb | No node port |
| default | post | No node port |
| default | post-db | No node port |
| default | ui | 9292 | http://192.168.59.101:31833 |
| ingress-nginx | ingress-nginx-controller | http/80 | http://192.168.59.101:32622 |
| | | https/443 | http://192.168.59.101:32430 |
| ingress-nginx | ingress-nginx-controller-admission | No node port |
| kube-system | kube-dns | No node port |
|---------------|------------------------------------|--------------|-----------------------------|
Open http://192.168.59.101:31833 (or execute minikube service ui) and check the application:
$ minikube service ui
|-----------|------|-------------|-----------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|-----------|------|-------------|-----------------------------|
| default | ui | 9292 | http://192.168.59.101:31833 |
|-----------|------|-------------|-----------------------------|
π Opening service default/ui in default browser...
Show minikube addon list:
$ minikube addons list
|-----------------------------|----------|--------------|--------------------------------|
| ADDON NAME | PROFILE | STATUS | MAINTAINER |
|-----------------------------|----------|--------------|--------------------------------|
| ambassador | minikube | disabled | 3rd party (Ambassador) |
| auto-pause | minikube | disabled | Google |
| csi-hostpath-driver | minikube | disabled | Kubernetes |
| dashboard | minikube | disabled | Kubernetes |
| default-storageclass | minikube | enabled β
| Kubernetes |
| efk | minikube | disabled | 3rd party (Elastic) |
| freshpod | minikube | disabled | Google |
| gcp-auth | minikube | disabled | Google |
| gvisor | minikube | disabled | Google |
| headlamp | minikube | disabled | 3rd party (kinvolk.io) |
| helm-tiller | minikube | disabled | 3rd party (Helm) |
| inaccel | minikube | disabled | 3rd party (InAccel |
| | | | [info@inaccel.com]) |
| ingress | minikube | enabled β
| Kubernetes |
| ingress-dns | minikube | disabled | Google |
| istio | minikube | disabled | 3rd party (Istio) |
| istio-provisioner | minikube | disabled | 3rd party (Istio) |
| kong | minikube | disabled | 3rd party (Kong HQ) |
| kubevirt | minikube | disabled | 3rd party (KubeVirt) |
| logviewer | minikube | disabled | 3rd party (unknown) |
| metallb | minikube | disabled | 3rd party (MetalLB) |
| metrics-server | minikube | disabled | Kubernetes |
| nvidia-driver-installer | minikube | disabled | Google |
| nvidia-gpu-device-plugin | minikube | disabled | 3rd party (Nvidia) |
| olm | minikube | disabled | 3rd party (Operator Framework) |
| pod-security-policy | minikube | disabled | 3rd party (unknown) |
| portainer | minikube | disabled | 3rd party (Portainer.io) |
| registry | minikube | disabled | Google |
| registry-aliases | minikube | disabled | 3rd party (unknown) |
| registry-creds | minikube | disabled | 3rd party (UPMC Enterprises) |
| storage-provisioner | minikube | enabled β
| Google |
| storage-provisioner-gluster | minikube | disabled | 3rd party (Gluster) |
| volumesnapshots | minikube | disabled | Kubernetes |
|-----------------------------|----------|--------------|--------------------------------|
Start minikube dashboard:
$ minikube dashboard
π Enabling dashboard ...
βͺ Using image kubernetesui/metrics-scraper:v1.0.8
βͺ Using image kubernetesui/dashboard:v2.6.0
π€ Verifying dashboard health ...
π Launching proxy ...
π€ Verifying proxy health ...
π Opening http://127.0.0.1:49442/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/ in your default browser...
^C
$ kubectl get all -n kubernetes-dashboard --selector k8s-app=kubernetes-dashboard
NAME READY STATUS RESTARTS AGE
pod/kubernetes-dashboard-cd7c84bfc-mlv95 1/1 Running 0 10m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes-dashboard ClusterIP 10.104.177.141 <none> 80/TCP 10m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/kubernetes-dashboard 1/1 1 1 10m
NAME DESIRED CURRENT READY AGE
replicaset.apps/kubernetes-dashboard-cd7c84bfc 1 1 1 10m
Create the dev namespace and start the application in that namespace:
$ kubectl delete -f .
deployment.apps "comment" deleted
service "comment-db" deleted
service "comment" deleted
deployment.apps "mongo" deleted
service "mongodb" deleted
deployment.apps "post" deleted
service "post-db" deleted
service "post" deleted
deployment.apps "ui" deleted
service "ui" deleted
$ kubectl apply -f dev-namespace.yml
namespace/dev created
$ kubectl apply -n dev -f .
$ kubectl get pods
No resources found in default namespace.
$ kubectl get pods -n dev
NAME READY STATUS RESTARTS AGE
comment-5bdb65d65b-5t682 1/1 Running 0 14s
comment-5bdb65d65b-f2gvd 1/1 Running 0 14s
comment-5bdb65d65b-qvxdc 1/1 Running 0 14s
mongo-67685ddb89-cn57z 1/1 Running 0 14s
post-b7857bb4d-22zzw 1/1 Running 0 13s
post-b7857bb4d-gm79j 1/1 Running 0 13s
post-b7857bb4d-zz8z2 0/1 ContainerCreating 0 13s
ui-8878d5c7d-7nz5v 0/1 ContainerCreating 0 13s
ui-8878d5c7d-fjtmp 0/1 ContainerCreating 0 13s
ui-8878d5c7d-svs6t 0/1 ContainerCreating 0 13s
Execute minikube service ui and check the application:
$ minikube service ui -n dev
|-----------|------|-------------|-----------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|-----------|------|-------------|-----------------------------|
| dev | ui | 9292 | http://192.168.59.101:30582 |
|-----------|------|-------------|-----------------------------|
π Opening service dev/ui in default browser...
Delete the application:
$ kubectl delete -n dev -f .
kubectl delete -n dev -f .
deployment.apps "comment" deleted
service "comment-db" deleted
service "comment" deleted
Warning: deleting cluster-scoped resources, not scoped to the provided namespace
namespace "dev" deleted
deployment.apps "mongo" deleted
service "mongodb" deleted
deployment.apps "post" deleted
service "post-db" deleted
service "post" deleted
deployment.apps "ui" deleted
service "ui" deleted
Obtain credentials for the created Yandex.Cloud managed Kubernetes cluster:
$ yc managed-kubernetes cluster get-credentials test-cluster --external
Context 'yc-test-cluster' was added as default to kubeconfig '/Users/vshender/.kube/config'.
Check connection to cluster using 'kubectl cluster-info --kubeconfig /Users/vshender/.kube/config'.
Note, that authentication depends on 'yc' and its config profile 'default'.
To access clusters using the Kubernetes API, please use Kubernetes Service Account.
$ kubectl config current-context
yc-test-cluster
$ kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
minikube minikube minikube default
* yc-test-cluster yc-managed-k8s-catds6ugdigmi36t9331 yc-managed-k8s-catds6ugdigmi36t9331
Start the application in the Yandex.Cloud managed Kubernetes cluster:
$ kubectl apply -f dev-namespace.yml
namespace/dev created
$ kubectl apply -n dev -f .
deployment.apps/comment created
service/comment-db created
service/comment created
namespace/dev unchanged
deployment.apps/mongo created
service/mongodb created
deployment.apps/post created
service/post-db created
service/post created
deployment.apps/ui created
service/ui created
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
cl19n73v3eg48lc5v71n-omim Ready <none> 7m30s v1.22.6 10.128.0.21 51.250.8.149 Ubuntu 20.04.4 LTS 5.4.0-117-generic containerd://1.6.6
cl19n73v3eg48lc5v71n-ukor Ready <none> 7m41s v1.22.6 10.128.0.16 62.84.118.232 Ubuntu 20.04.4 LTS 5.4.0-117-generic containerd://1.6.6
$ kubectl describe service ui -n dev | grep NodePort
Type: NodePort
NodePort: <unset> 30089/TCP
Open http://51.250.8.149:30089/ and check the application.
Delete the application:
$ kubectl delete -n dev -f .
kubectl delete -n dev -f .
deployment.apps "comment" deleted
service "comment-db" deleted
service "comment" deleted
Warning: deleting cluster-scoped resources, not scoped to the provided namespace
namespace "dev" deleted
deployment.apps "mongo" deleted
service "mongodb" deleted
deployment.apps "post" deleted
service "post-db" deleted
service "post" deleted
deployment.apps "ui" deleted
service "ui" deleted
Switch back to the minikube context:
$ kubectl config use-context minikube
Switched to context "minikube".
$ kubectl config current-context
minikube
Create a Yandex.Cloud managed Kubernetes cluster using Terraform:
$ cd ../terraform_ykc
$ terraform init
...
$ terraform apply -auto-approve
...
Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
Outputs:
kubeconfig = <<EOT
apiVersion: v1
clusters:
- cluster:
server: https://84.201.175.39
certificate-authority-data: ...
name: yc-managed-k8s-catmil589ak21jvv065o
contexts:
- context:
cluster: yc-managed-k8s-catmil589ak21jvv065o
user: yc-managed-k8s-catmil589ak21jvv065o
name: yc-reddit-k8s
current-context: yc-reddit-k8s
kind: Config
preferences: {}
users:
- name: yc-managed-k8s-catmil589ak21jvv065o
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
args:
- k8s
- create-token
- --profile=default
command: yc
env: null
interactiveMode: IfAvailable
provideClusterInfo: false
EOT
$ yc managed-kubernetes cluster get-credentials reddit-k8s --external
Context 'yc-reddit-k8s' was added as default to kubeconfig '/Users/vshender/.kube/config'.
Check connection to cluster using 'kubectl cluster-info --kubeconfig /Users/vshender/.kube/config'.
$ kubectl config current-context
yc-reddit-k8s
Deploy the application:
$ cd ../reddit
$ kubectl apply -f dev-namespace.yml
namespace/dev created
$ kubectl apply -n dev -f .
deployment.apps/comment created
service/comment-db created
service/comment created
namespace/dev unchanged
deployment.apps/mongo created
service/mongodb created
deployment.apps/post created
service/post-db created
service/post created
deployment.apps/ui created
service/ui created
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
cl1uup9l8cjjkjmftnr5-ahad Ready <none> 17m v1.19.15 192.168.10.26 130.193.49.66 Ubuntu 20.04.4 LTS 5.4.0-117-generic containerd://1.6.6
$ kubectl describe service ui -n dev | grep NodePort
Type: NodePort
NodePort: <unset> 30079/TCP
Open http://130.193.49.66:30079 and check the application.
Delete the application and destroy the created Kubernetes cluster:
$ kubectl delete -n dev -f .
kubectl delete -n dev -f .
deployment.apps "comment" deleted
service "comment-db" deleted
service "comment" deleted
Warning: deleting cluster-scoped resources, not scoped to the provided namespace
namespace "dev" deleted
deployment.apps "mongo" deleted
service "mongodb" deleted
deployment.apps "post" deleted
service "post-db" deleted
service "post" deleted
deployment.apps "ui" deleted
service "ui" deleted
$ kubectl config use-context minikube
Switched to context "minikube".
$ cd ../terraform_ykc
$ terraform destroy -auto-approve
...
Destroy complete! Resources: 4 destroyed.