<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployments on Layer5 Documentation</title><link>/tags/deployments/</link><description>Recent content in Deployments on Layer5 Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/deployments/index.xml" rel="self" type="application/rss+xml"/><item><title>Explore Deployments</title><link>/kanvas/tutorials/kubernetes/kubernetes-deployments/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/kanvas/tutorials/kubernetes/kubernetes-deployments/</guid><description>&lt;p&gt;In this tutorial you build an NGINX Deployment with two replicas, deploy it, scale it to three, and roll it to a new image version, inspecting the result in Operator after each change. A Deployment is the controller most stateless applications run under: you declare how many Pods you want and what they look like, and Kubernetes keeps that many running and replaces them gradually when the template changes. Seeing the ReplicaSets and Pods appear and change shows you what the controller does on your behalf.&lt;/p&gt;</description></item><item><title>Deploy a PHP Guestbook with Redis</title><link>/kanvas/tutorials/kubernetes/deploy-php-redis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/kanvas/tutorials/kubernetes/deploy-php-redis/</guid><description>&lt;p&gt;In this tutorial you build the Kubernetes guestbook: a PHP frontend that writes entries to a Redis leader and reads them from Redis followers. Six manifests from the Kubernetes examples become one Kanvas design, which you deploy, inspect in Operator, scale, and remove. The application is small, but it carries the pattern behind most multi-tier systems: each tier runs as a Deployment, each tier is reached through a Service, and tiers find each other by Service name, never by Pod address.&lt;/p&gt;</description></item></channel></rss>