InfoQ Homepage Kubernetes Content on InfoQ
-
InfoQ's 2019, and Software Predictions for 2020
We take a look back at what we saw on InfoQ in 2019, and think about what the next year might bring.
-
Quarkus, a Kubernetes Native Java Framework, Reaches Version 1.0: Q&A with Thomas Qvarnstrom
Quarkus, a Kubernetes native Java framework tailored for GraalVM and OpenJDK HotSpot, has reached version 1.0. Quarkus is an Open Source stack for writing Java applications, offering unparalleled startup time, memory footprint and developer experience. InfoQ spoke with Thomas Qvarnstrom, senior principal product manager at Red Hat, in order to learn about the Quarkus journey, extensions, and more.
-
Containers in 2019: They're Calling it a [Hypervisor] Comeback
The 2019 news cycle within the "cloud native" corner of the world has been abuzz with a word previously thought outmoded by the rapid rise of containers: “hypervisor.” This article explores the motivations behind this, focusing on security, user experience, and isolation flexibility, and concludes by speculating on the future direction of development within the cloud and container industry.
-
Implementing Policies in Kubernetes
The author explains what Kubernetes policies are, and how they can help you manage and secure the Kubernetes cluster. We will also look at why we need a policy engine to author and manage policies.
-
Cellery: A Code-First Approach to Deploy Applications on Kubernetes
Cellery is a code-first approach to building, integrating, running, and managing composite applications on Kubernetes, using a cell-based architecture. Learn what cells are, how Cellery works, and see how an existing Kubernetes application written by Google can be deployed, managed, and observed using Cellery.
-
Kubernetes Workloads in the Serverless Era: Architecture, Platforms, and Trends
Explore how microservices architecture has evolved into cloud-native architecture, where many of the infrastructure concerns are provided by Kubernetes in combination with additional abstractions provided by service mesh and serverless frameworks. In addition, the serverless ecosystem is evolving by exploring standard and open packaging, runtimes, and event formats.
-
API Gateways and Service Meshes: Opening the Door to Application Modernisation
Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.
-
To Multicluster, or Not to Multicluster: Inter-Cluster Communication Using a Service Mesh
Communication within Kubernetes clusters is a solved issue, but communication across clusters requires more design and operational overhead. Before deciding on whether to implement multicluster support, you should understand your communication use case.
-
DevOps and Cloud InfoQ Trends Report - February 2019
An overview of how the “cloud computing” and DevOps space is evolving in 2019 including updates on Kubernetes, Chaos Engineering, Service meshes and more.
-
Four Techniques Serverless Platforms Use to Balance Performance and Cost
There are two aspects that have been key to the rapid adoption of serverless computing: the performance and the cost model. This article looks at those aspects, the tradeoffs, and opportunity ahead.
-
Ambassador: Building a Control Plane for an Envoy-Powered API Gateway on Kubernetes
This article provides an insight into the creation of the Ambassador open source API gateway for Kubernetes, and discusses the technical challenges and lessons learned from building a developer-focused control plane for managing ingress or "edge" traffic within microservice-based applications.
-
Service Catalog and Kubernetes
Cloud-native applications do not just live inside Kubernetes—they also benefit from using the available cloud managed services. Similar to Kubernetes' declarative object configuration model, the Open Service Broker API with the Service Catalog provides a declarative way to describe cross-platform/cross-cloud managed service dependencies.