Deploy Dockerized Node/Express to Compute Engine (with Load Balancer and SSL termination)

Подписаться 1,4 тыс.

Просмотров 1,2 тыс.

50% 1

Ad: If you need help with a Google Cloud deployment, you can book a consultation with me. Fees and contact info are available on my channel page.
In this video we will write a basic Node.js/Express project, then build a docker image out and deploy this image to Compute Engine in Google Cloud. We will serve this deployment to the internet using a Global Load Balancer in Google Cloud.
Source code and URLs:
github.com/titus58/youtube-tu...
Chapters:
00:00 Introduction
02:01 Write the Express project from scratch
07:33 Add logging using Winston
09:58 Dockerize the project
14:05 Create the Google Cloud project and enable APIs
15:22 Push the Docker image to Artifact Registry
17:59 Reserve public and private static IPs
20:32 Deploy docker image to Compute Engine
32:13 Comparison of NEGs and Instance Groups
34:21 Create the Network Entity Group
36:45 Create instance group
44:28 Create the Global Load Balancer
54:25 Add URL rewriting in the load balancer

Опубликовано:

16 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 13

@tayelolu_bells8241 10 месяцев назад

Learnt a lot from this. Thank you

@shubhamtribhuvan9086 Год назад

Useful content if ur are serious Dev🔥

@vladsavecoding4111 Год назад

Thank you 🙏

@shubhamtribhuvan9086 Год назад

❤️🔥👍

@KePaco-mf1bf 6 месяцев назад

Hi, I'm a BE newbie, this video is such help to me, let me have a direction for how to configurations Google services But seem if I don't have a domain, it wouldn't be able to access from the public IP of the VM, I follow all of the steps with the video. But i just got stuck with domain and seem it's failed all the time when i try to run the docker with ssh sheel

@vladsavecoding4111 6 месяцев назад

If you just want to access by IP, then skip the Load Balancer and assign the public IP to the VM. Also make sure you set that PORT environment variable to 80. Otherwise the server will run on port 3000 and you will not be able to access it because port 3000 is blocked by the firewall

@krkashwan 11 месяцев назад

Hi, an excellent tutorial on the topic. I have repeated it and it works fine. The page is accessible via domain name with SSL. But what I observed is - the page is also accessible via IP address of instance group. Is this a case of bypass of load balancer. If so, what are implications and actually why is it so?

@vladsavecoding4111 11 месяцев назад

Interesting. Yes, you are right. This is because the global load balancer in Google Cloud works with external IP addresses. Ideally these ports should not be exposed but I don't think there's a security risk. It should be possible to add a firewall rule that blocks port 80 access on these public IPs. However, you need to make sure the Load Balancer can still access them. So maybe two rules.

@mystikyogi 3 месяца назад

How can we scale the containers and set up an auto CI/CD GitHub push trigger? I thought we were going to use Docker Swarm.

@vladsavecoding4111 3 месяца назад

Instance groups can be auto scaled. Why would you think it's using Docker swarm? There's a diagram at the beginning of the video, there's no mention of docker swarm

@krkashwan 7 месяцев назад

Hi! If we put database connection string (we know that it contains password to access database) into container environment variable as key-value pair, will it pose security breach? If so, what is the best way to pass database connection string on code while deploying docker image?

@vladsavecoding4111 7 месяцев назад

Environment variable is safe. You can also take a look at Secret Manager if you want to hide the database password inside your org

@krkashwan 7 месяцев назад

Thank you!