<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets on Layer5 Documentation</title><link>/tags/secrets/</link><description>Recent content in Secrets on Layer5 Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/secrets/index.xml" rel="self" type="application/rss+xml"/><item><title>Use ConfigMaps and Secrets</title><link>/kanvas/tutorials/kubernetes/kubernetes-configmaps-secrets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/kanvas/tutorials/kubernetes/kubernetes-configmaps-secrets/</guid><description>&lt;p&gt;In this tutorial you design a MySQL Pod that takes its database name from a ConfigMap and its root password from a Secret, deploy it to a cluster, and prove from inside the container that each value arrived. Separating configuration and credentials from the container image is how one image runs unchanged in every environment, and knowing exactly how Kubernetes delivers those values tells you why a changed setting sometimes reaches a running container and sometimes does not.&lt;/p&gt;</description></item><item><title>Deploy WordPress and MySQL with Persistent Volumes</title><link>/kanvas/tutorials/kubernetes/wordpress-mysql-persistentvolume/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/kanvas/tutorials/kubernetes/wordpress-mysql-persistentvolume/</guid><description>&lt;p&gt;In this tutorial you deploy WordPress backed by a MySQL database, and you give both tiers storage that outlives their Pods. You import the two Kubernetes example manifests into one design, add the Secret that holds the database password, and add the PersistentVolumes that the claims bind to. Stateless Pods can be replaced at any moment; a database cannot lose its files when that happens. This tutorial shows how Kubernetes separates the data from the Pod, and exactly which pieces a deploy creates and an undeploy removes.&lt;/p&gt;</description></item></channel></rss>