diff options
| author | Julien Dessaux | 2021-03-11 23:15:31 +0100 |
|---|---|---|
| committer | Julien Dessaux | 2021-03-11 23:15:31 +0100 |
| commit | 8d4bb3881dbb702f08f830417a24b2b81d1a2678 (patch) | |
| tree | 4063c82565aafa5b1291e4128f69f840398fedcc /content/blog/kubernetes/get_key_and_certificae.md | |
| parent | Removed empty file (diff) | |
| download | www-8d4bb3881dbb702f08f830417a24b2b81d1a2678.tar.gz www-8d4bb3881dbb702f08f830417a24b2b81d1a2678.tar.bz2 www-8d4bb3881dbb702f08f830417a24b2b81d1a2678.zip | |
Some more articles reformatting
Diffstat (limited to 'content/blog/kubernetes/get_key_and_certificae.md')
| -rw-r--r-- | content/blog/kubernetes/get_key_and_certificae.md | 11 |
1 files changed, 10 insertions, 1 deletions
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 |