<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Kubernetes on RedDec</title><link>https://blog.reddec.net/tags/kubernetes/</link><description>Recent content in Kubernetes on RedDec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 May 2025 23:43:00 +0800</lastBuildDate><atom:link href="https://blog.reddec.net/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenEBS ZFS Permission</title><link>https://blog.reddec.net/posts/openebs-zfs-permission/</link><pubDate>Fri, 02 May 2025 23:43:00 +0800</pubDate><guid>https://blog.reddec.net/posts/openebs-zfs-permission/</guid><description>&lt;p&gt;&lt;a href="https://github.com/openebs/zfs-localpv"&gt;OpenEBS ZFS LocalPV&lt;/a&gt; delivers powerful and notably fast storage for Kubernetes environments. However, a common hurdle appears when attempting to use these volumes with containers operating under non-root privileges. Let&amp;rsquo;s dissect why this occurs specifically with native ZFS volumes and outline the effective solution.&lt;/p&gt;
&lt;h3 id="how-openebs-zfs-provisions-volumes"&gt;How OpenEBS ZFS provisions volumes&lt;/h3&gt;
&lt;p&gt;OpenEBS ZFS LocalPV offers &lt;a href="https://github.com/openebs/zfs-localpv/blob/develop/docs/quickstart.md#pool-name-requirement"&gt;several methods&lt;/a&gt; for volume creation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Native ZFS Volume (using &lt;code&gt;fstype: &amp;quot;zfs&amp;quot;&lt;/code&gt;):&lt;/strong&gt; This method carves out a ZFS filesystem directly within your ZFS pool. It stands out as the &lt;strong&gt;fastest and most straightforward approach&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Volume with other filesystems (e.g., &lt;code&gt;fstype: &amp;quot;ext4&amp;quot;&lt;/code&gt;):&lt;/strong&gt; This involves creating a ZFS subvolume (or zvol) which is then formatted using a different filesystem, such as ext4 or XFS.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This guide concentrates on the first scenario: native ZFS volumes.&lt;/p&gt;</description></item><item><title>Longhorn Backup and Restore</title><link>https://blog.reddec.net/posts/longhorn-backup-and-restore/</link><pubDate>Mon, 21 Oct 2024 12:53:49 +0800</pubDate><guid>https://blog.reddec.net/posts/longhorn-backup-and-restore/</guid><description>&lt;p&gt;Article breaks down using Longhorn (version 1.7) for backups, self-hosting, and recovery. It&amp;rsquo;s for seasoned DevOps and SysAdmin folks who like doing things themselves. You&amp;rsquo;ll find a step-by-step guide on setting up and restoring backups with Longhorn, Velero, and GitOps. The goal is to show you a tried-and-true setup for getting your backups and restores working smoothly.&lt;/p&gt;</description></item><item><title>Kubernetes Ingress Dashboard</title><link>https://blog.reddec.net/posts/kid/</link><pubDate>Mon, 13 Dec 2021 17:13:10 +0800</pubDate><guid>https://blog.reddec.net/posts/kid/</guid><description>&lt;p&gt;&lt;img loading="lazy" src="https://blog.reddec.net/img/ingress-dashboard.svg"&gt;&lt;/p&gt;
&lt;div&gt;
&lt;a a href="https://github.com/reddec/ingress-dashboard" target="_blank"&gt;
&amp;nbsp;&amp;nbsp;reddec/ingress-dashboard
&lt;/a&gt;
&lt;/div&gt;
&lt;p&gt;Automatic dashboard generation for Ingress objects.&lt;/p&gt;
&lt;p&gt;Features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No JS&lt;/li&gt;
&lt;li&gt;Supports OIDC (Keycloak, Google, Okta, &amp;hellip;) and Basic authorization&lt;/li&gt;
&lt;li&gt;Automatic discovery of Ingress objects, configurable by annotations&lt;/li&gt;
&lt;li&gt;Supports static configuration (in addition to Ingress objects)&lt;/li&gt;
&lt;li&gt;Multiarch docker images: for amd64 and for arm64&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>