From 8d4bb3881dbb702f08f830417a24b2b81d1a2678 Mon Sep 17 00:00:00 2001
From: Julien Dessaux
Date: Thu, 11 Mar 2021 23:15:31 +0100
Subject: Some more articles reformatting

---
 content/blog/kubernetes/get_key_and_certificae.md | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

(limited to 'content/blog/kubernetes/get_key_and_certificae.md')

diff --git a/content/blog/kubernetes/get_key_and_certificae.md b/content/blog/kubernetes/get_key_and_certificae.md
index c66cac8..247446b 100644
--- a/content/blog/kubernetes/get_key_and_certificae.md
+++ b/content/blog/kubernetes/get_key_and_certificae.md
@@ -1,9 +1,18 @@
 ---
 title: "Get tls certificate and key from a kubernetes secret"
 date: 2020-08-06
+description: How to extract a tls certificate and keys from a kubernetes secret
+tags:
+  - kubernetes
 ---
 
-My use case is to deploy a wildcard certificate that was previously handled by an acme.sh on my legacy lxd containers. Since moving to kubernetes parts of my services I have been using cert-manager to issue letsencrypt certificates. Since I am not done yet I looked into a way of getting a certificate out of kubernetes. Assuming we are working with a secret named `wild.adyxax.org-cert` and our namespace is named `legacy` :
+## The problem
+
+My use case is to deploy a wildcard certificate that was previously handled by an acme.sh on a legacy lxd containers. Since moving to kubernetes parts of my services I have been using cert-manager to issue letsencrypt certificates for the cluster's ingresses. Since I am not done migrating everything yet I need a way of getting a certificate out of kubernetes.
+
+## The solution
+
+Assuming we are working with a secret named `wild.adyxax.org-cert` and our namespace is named `legacy` :
 {{< highlight sh >}}
 kubectl -n legacy get secret wild.adyxax.org-cert -o json -o=jsonpath="{.data.tls\.crt}" | base64 -d > fullchain.cer
 kubectl -n legacy get secret wild.adyxax.org-cert -o json -o=jsonpath="{.data.tls\.key}" | base64 -d > adyxax.org.key
-- 
cgit v1.2.3