Google Kubernetes Engine vs. Linux Containers LXD

Google Kubernetes Engine is well suited for dynamic and large workloads since it can scale up with usage. It is easily configurable, which allows for flexibility. User interface is simple to navigate, which reduces roadblocks for a team with people unfamiliar with Kubernetes. Great if you are already using other GCP services as it integrates well with that.

Incentivized

Scenarios where you need an authentication server, a GIT repository the system works very well 'cause you don't need any scalability and the ease to configure and share the same Linux system image across the containers and the rollback process is quick. I didn't put any critical applications there not because of the limitations but due to a company policy.

Incentivized

• Deployment of a new GKE cluster is really fast in comparison to other cloud providers.
• GCP is ahead other vendors and always provide the most up to date Kubernetes version.
• GKE automation for master upgrade and the worker nodes pool works really well.

Incentivized

• GIT repositories.
• Authentication servers.
• Application instances.

Incentivized

• Not as intuitive as it could be
• Documentation could be better, especially for people using other Google Cloud tools
• Not the preferred Kubernetes Engine for many apps

Incentivized

• Ease of use.
• Copying containers from one machine to another.
• Creation of containers with config files similar to Docker.

Incentivized

It's a great product if you learn it. It has flexibility and is very strong. Autoscaling and Resource management make running huge applications a breeze. Using Helm with Kubernetes and Terraform for infrastructure creation can totally automate your CICD pipeline. You also get easy access to CUDA cores for machine learning.

Incentivized

Google support is excellent and helpful, but the first answer is always so bureaucratic no matter how many logs, evidence, and information you sent.

Incentivized

We had to move several products to Google Cloud, and the Google Kubernetes Engine was the option recommended to us, so we investigated it and ran with it. Back then (2019), we were not aware of Cloud Run-provisioned K8s clusters, so our other option was a completely self-managed K8s cluster on Compute Engine VMs, which we did not have the knowledge of and capacity to handle.

Incentivized

Linux Containers LXD feels like a more primitive version of docker, docker-compose and similar projects from the docker ecosystem. The Dockerfile and docker-compose.yml methods of specifying a container setup, as well as the network and file configurations afforded by Docker make working with containers much easier and more reproducible than with Linux Containers LXD.

Incentivized

• Compared to other big K8s providers it has the best price/performance factors.
• Upgrade process from stable to regular versions
• Old stable releases: 1.15/1.16 should be in a stable branch.

Incentivized

• Quicker development cycles.
• Reduced need for different physical machines or servers.
• Standardized development environment.

Incentivized