aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJulien Dessaux2020-11-29 15:05:44 +0100
committerJulien Dessaux2020-11-29 15:05:44 +0100
commit2ac0e0dcd2a3c8218fbc95bee06f2fda6f0beadb (patch)
tree584d83e4d32563cadce2edbc5a72ee7e605d75e8
parentUpdated www.adyxax.org articles (diff)
downloadwww-2ac0e0dcd2a3c8218fbc95bee06f2fda6f0beadb.tar.gz
www-2ac0e0dcd2a3c8218fbc95bee06f2fda6f0beadb.tar.bz2
www-2ac0e0dcd2a3c8218fbc95bee06f2fda6f0beadb.zip
Added content
-rw-r--r--content/en/blog/kubernetes/get_key_and_certificae.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/content/en/blog/kubernetes/get_key_and_certificae.md b/content/en/blog/kubernetes/get_key_and_certificae.md
new file mode 100644
index 0000000..c66cac8
--- /dev/null
+++ b/content/en/blog/kubernetes/get_key_and_certificae.md
@@ -0,0 +1,10 @@
+---
+title: "Get tls certificate and key from a kubernetes secret"
+date: 2020-08-06
+---
+
+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` :
+{{< 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
+{{< /highlight >}}