# Gke Google Kubernetes Engine (GKE) is a Google Cloud product for creating and managing Kubernetes clusters and deploying workloads. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Scaling Smarter: Maximizing Density and Efficiency with Fermyon Platform for Kubernetes and GKE Autopilot DevFeed: [Scaling Smarter: Maximizing Density and Efficiency with Fermyon Platform for Kubernetes and GKE Autopilot]() Original publisher: [Read original article]() Author: MacKenzie Adam Published: 2025-04-09T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Gke](), [autoscaling](), [Kubernetes](), [WebAssembly]() Tags: [autoscaling](), [gke](), [kubernetes](), [webassembly]() ### AI overview The article describes combining GKE Autopilot with Fermyon's Platform for Kubernetes and its high-density WebAssembly runtime to scale thousands of applications per node without overprovisioning. ### Source excerpt Unlock faster, more efficient autoscaling by combining GKE Autopilot with Fermyon's Platform for Kubernetes high-density WebAssembly runtime--scaling thousands of apps per node without overprovisioning. ## Fermyon at Google Cloud Next 2025 DevFeed: [Fermyon at Google Cloud Next 2025]() Original publisher: [Read original article]() Author: Jasmine Mae Alindayu Published: 2025-04-02T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Gke](), [Google]() Tags: [2025](), [cloud-next](), [generation](), [gke](), [google](), [running](), [team]() ### AI overview Fermyon will attend Google Cloud Next 2025 and showcase next-generation scaling and density running on GKE. ### Source excerpt The Fermyon team will be at Google Cloud Next, where we will be showcasing next generation scaling and density running on GKE. ## Blog: Introducing Falco 0.39.2 DevFeed: [Blog: Introducing Falco 0.39.2]() Original publisher: [Read original article]() Published: 2024-11-21T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [eBPF](), [Kernel](), [Gke](), [Docker](), [Process]() Tags: [aws](), [container-images](), [docker](), [ebpf](), [falco](), [gke](), [kernel](), [release]() ### AI overview Falco 0.39.2 is a small patch release that fixes modern eBPF driver issues, including compatibility with GKE and kernel versions 6.11.4 and later. ### Source excerpt Today we announce the release of Falco 0.39.2 🦅! Fixes Falco's 0.39.2 is a small patch release that includes some important bugfixes for modern eBPF driver: check cred field is not NULL before the access; this enables Falco back with modern eBPF driver to work on GKE address verifier issues on kernel versions >=6.11.4: there was a kernel-breaking change in the tail call ebpf API merged into the 6.11.4 to fix a CVE. Adapt our code to work again on these new versions. Thanks to everyone in the community for helping us spot these annoying bugs and improving Falco every day 🐛! You make Falco successful 🦅! Thanks as always to the Falco maintainers for their support and effort during the entire release process. Try it! 🏎 As usual, in case you just want to try out the stable Falco 0.39.2, you can install its packages following the process outlined in the docs: CentOS/Amazon Linux Debian/Ubuntu openSUSE Linux binary package Prefer to use a container image? No problem at all! 🐳 You can read more about running Falco with Docker in the docs. You can also find the Falcosecurity container images on the public AWS ECR gallery: falco falco-no-driver falco-driver-loader Let's meet 🤝 We meet every Wednesday in our community calls, if you want to know the latest and the greatest, you should join us there! If you have any questions Join the #falco channel on the Kubernetes Slack Join the Falco mailing list Thanks to all the amazing contributors! Enjoy 😎, Federico ## Blog: Adding runtime threat detection to Google Kubernetes Engine with Falco DevFeed: [Blog: Adding runtime threat detection to Google Kubernetes Engine with Falco]() Original publisher: [Read original article]() Published: 2023-11-20T00:00:00Z Content type: tutorial Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Gke](), [threat detection](), [Kubernetes](), [Containers](), [eBPF](), [Google Cloud Platform (GCP)]() Tags: [cloud-marketplace](), [ebpf](), [falco](), [gke](), [google-cloud](), [google-kubernetes-engine](), [helm](), [kubernetes](), [threat-detection]() ### AI overview This tutorial explains how to add Falco runtime threat detection to Google Kubernetes Engine clusters. It describes Falco's syscall monitoring, its use of Kubernetes and container-runtime context, example security rules, installation through Google Cloud Marketplace or Helm, and constraints involving Autopilot, privileged containers, and eBPF drivers. ### Source excerpt One of the big advantages of running your workloads on a managed Kubernetes service like Google Kubernetes Engine (GKE) is that Google ensures your clusters are being deployed and managed following industry best practices. While GKE clusters are incredibly secure and reliable, there is always room for improvement. In this blog, we're going to describe how you can enhance GKE's already great security by adding runtime threat detection with Falco. What is Falco? Falco is a Cloud Native Computing Foundation project that provides runtime threat detection. Out of the box, Falco examines syscalls to alert you to any suspicious activity. And, since containers share the same kernel as their host, Falco can monitor not only activity on the host but also activity on all of the containers running on that host. Moreover, Falco pulls data from both Kubernetes and the container runtime to add additional context to its alerts. With Falco running on your GKE clusters you can be notified of a wide variety of events, such as: Did someone start a container with high privileges? Has someone shelled into a running container? Has an executable been added to the container after it was deployed? These are just a few examples. Falco has over 80 rules that can be used to make you aware of not only external threats but also when clusters aren't being operated in accordance with industry best practices. GKE Installation considerations There are two different ways to install Falco on GKE. The first is using the prepackaged click-to-run offering in the Google Cloud Marketplace. The second is using Falco's helm chart. The click-to-run offering is probably the simplest way to get up and running with Falco on GKE, but the drawback is that the version offered often lags behind the latest release. It's also important to note that as of this writing, you cannot run Falco on GKE clusters running in Autopilot mode. This is primarily because Falco uses an init container running with privileged access to ## GKE using Traefik as the ingress controller DevFeed: [GKE using Traefik as the ingress controller]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2020-02-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Gke](), [traefik](), [Kubernetes](), [Cloudflare]() Tags: [cloudflare](), [gke](), [ingress](), [kubernetes](), [load-balancer](), [traefik]() ### AI overview The article explains how using Traefik as the ingress controller in a GKE Kubernetes cluster caused intermittent Cloudflare HTTP 520 errors. A load balancer sent traffic to preemptible nodes that did not run Traefik; if a node was preempted during a slow request, the request ended prematurely. The proposed fix is to configure load-balancer health checks so only nodes running Traefik receive traffic. ### Source excerpt I recently fell into a trap using Traefik as the ingress controller in one cluster. I decided to write about it with hopes it maybe help someone else. ## GKE in production DevFeed: [GKE in production]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2017-07-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Gke](), [Google Cloud Platform (GCP)](), [Kubernetes](), [Amazon Web Services](), [Digital Ocean]() Tags: [aws](), [cloud-sql](), [digitalocean](), [gke](), [google-cloud](), [health-checks](), [heroku](), [ingress](), [kubernetes](), [postfix](), [sendgrid](), [spinnaker]() ### AI overview A developer describes deploying small applications on GKE and lessons learned from moving between AWS and Google Cloud. The article covers SSL with Kubernetes Ingress, email delivery through SendGrid, Cloud SQL access through a sidecar container, and deployment with a shell script or Spinnaker. ### Source excerpt I've been working with DigitalOcean, Heroku and AWS for some years now.