<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SealedSecret on Blog · Muhammad Fauzi Islami</title><link>https://fauzislami.github.io/tags/sealedsecret/</link><description>Recent content in SealedSecret on Blog · Muhammad Fauzi Islami</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://fauzislami.github.io/tags/sealedsecret/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing K8S Secret Object Using SealedSecret</title><link>https://fauzislami.github.io/blog/2021/09/26/secure-k8s-secret-object-using-sealedsecret/</link><pubDate>Sun, 26 Sep 2021 00:00:00 +0000</pubDate><guid>https://fauzislami.github.io/blog/2021/09/26/secure-k8s-secret-object-using-sealedsecret/</guid><description>&lt;p&gt;&lt;img src="https://fauzislami.github.io/images/sealed-secret/1.png" alt="Scratchpad" title="Scratchpad"&gt;&lt;/p&gt;
&lt;p&gt;Managing kubernetes manifest on Git or any other SCM is a common task nowadays. It makes life easier if we talk about continuous deployment. However, there is a manifest that should not be stored on SCM, it’s secret object. Secret object on Kubernetes was made to hide any sensitive data including user credentials and key. Unfortunately, secret object is not completely secure, it does not encrypt but only uses base64 encoding scheme to hide the data and it can be easily decoded. Therefore, Sealed Secret is one of the solution to make the secret more secure and can be securely stored on SCM.&lt;/p&gt;</description></item></channel></rss>