cdk8s-abstractions

Use when asking about ZFS volumes, TailscaleIngress, Tailscale ingress, Funnel public access, container props, Redis construct, or other reusable CDK8s abstractions.

15 stars

Best use case

cdk8s-abstractions is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when asking about ZFS volumes, TailscaleIngress, Tailscale ingress, Funnel public access, container props, Redis construct, or other reusable CDK8s abstractions.

Teams using cdk8s-abstractions should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/cdk8s-abstractions/SKILL.md --create-dirs "https://raw.githubusercontent.com/shepherdjerred/monorepo/main/packages/dotfiles/dot_agents/skills/cdk8s-abstractions/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/cdk8s-abstractions/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How cdk8s-abstractions Compares

Feature / Agentcdk8s-abstractionsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when asking about ZFS volumes, TailscaleIngress, Tailscale ingress, Funnel public access, container props, Redis construct, or other reusable CDK8s abstractions.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# CDK8s Abstractions

## Overview

This project provides reusable CDK8s constructs for common patterns: storage volumes with backup
labeling, Tailscale networking, container property composition, and database services.

## Storage Constructs

### ZfsNvmeVolume

Creates a PVC on NVMe storage with automatic Velero backup labeling.

```typescript
import { ZfsNvmeVolume } from "../misc/zfs-nvme-volume.ts";
import { Size } from "cdk8s";

const configVolume = new ZfsNvmeVolume(chart, "myapp-config-pvc", {
  storage: Size.gibibytes(8),
});

// Use in deployment
volumeMounts: [
  {
    path: "/config",
    volume: Volume.fromPersistentVolumeClaim(
      chart,
      "myapp-config-volume",
      configVolume.claim,  // Access the PVC
    ),
  },
],
```

### ZfsSataVolume

Creates a PVC on SATA SSD storage for large data (uses K8s storage class `zfs-hdd` for legacy reasons).

```typescript
import { ZfsSataVolume } from "../misc/zfs-sata-volume.ts";
import { Size } from "cdk8s";

const mediaVolume = new ZfsSataVolume(chart, "media-hdd-pvc", {
  storage: Size.tebibytes(4),
});
```

### Automatic Backup Labeling

Both constructs auto-label PVCs for Velero:

| Volume Size | Backup Status                |
| ----------- | ---------------------------- |
| < 200 GB    | `velero.io/backup: enabled`  |
| >= 200 GB   | `velero.io/backup: disabled` |

```typescript
// Implementation detail
const shouldBackup = props.storage.toKibibytes() < Size.gibibytes(200).toKibibytes();
metadata: {
  labels: {
    "velero.io/backup": shouldBackup ? "enabled" : "disabled",
    "velero.io/exclude-from-backup": shouldBackup ? "false" : "true",
  },
},
```

## Networking Constructs

### TailscaleIngress

Creates an Ingress with the Tailscale ingress class. Services are exposed via the Tailscale Kubernetes operator for secure private network access.

```typescript
import { TailscaleIngress } from "../misc/tailscale.ts";
import { Service } from "cdk8s-plus-31";

const service = new Service(chart, "myapp-service", {
  selector: deployment,
  ports: [{ port: 8080 }],
});

// Basic usage (private Tailscale access)
new TailscaleIngress(chart, "myapp-ingress", {
  service,
  host: "myapp", // Accessible at myapp.tailnet-1a49.ts.net
});

// Public internet access via Funnel
new TailscaleIngress(chart, "myapp-ingress", {
  service,
  host: "myapp",
  funnel: true, // Accessible from public internet
});
```

**DNS pattern:** All services follow `{host}.tailnet-1a49.ts.net` (e.g., `sonarr.tailnet-1a49.ts.net`, `argocd.tailnet-1a49.ts.net`).

#### Implementation Details

```typescript
// From src/cdk8s/src/misc/tailscale.ts
export class TailscaleIngress extends Construct {
  constructor(
    scope: Construct,
    id: string,
    props: Partial<IngressProps> & {
      host: string;
      funnel?: boolean;
      service: Service | ServiceObject;
    },
  ) {
    super(scope, id);

    let base: IngressProps = {
      defaultBackend: IngressBackend.fromService(props.service as Service),
      tls: [{ hosts: [props.host] }],
    };

    if (props.funnel) {
      base = {
        ...base,
        metadata: {
          annotations: {
            "tailscale.com/funnel": "true",
          },
        },
      };
    }

    const ingress = new Ingress(scope, `${id}-ingress`, merge({}, base, props));

    // Set ingress class to Tailscale
    ApiObject.of(ingress).addJsonPatch(
      JsonPatch.add("/spec/ingressClassName", "tailscale"),
    );
  }
}
```

TLS is automatically handled by Tailscale — no `secretName` needed in the tls config.

### createIngress Function

Alternative function-based API for ArgoCD applications or when you need more control:

```typescript
import { createIngress } from "../misc/tailscale.ts";

createIngress(
  chart,
  "myapp-ingress", // Ingress name
  "myapp", // Namespace
  "myapp-service", // Service name (string, not object)
  8080, // Port
  ["myapp"], // Hosts
  false, // Funnel enabled
);
```

**Signature:**

```typescript
export function createIngress(
  chart: Chart,
  name: string,
  namespace: string,
  service: string,
  port: number,
  hosts: string[],
  funnel: boolean,
): KubeIngress;
```

### Tailscale Ingress Patterns

**ArgoCD application ingress:**

```typescript
createIngress(
  chart,
  "argocd-ingress",
  "argocd",
  "argocd-server",
  443,
  ["argocd"],
  true,
);
```

**Multiple ingresses for same deployment:**

```typescript
new TailscaleIngress(chart, "myapp-web-ingress", {
  service: webService,
  host: "myapp",
});
new TailscaleIngress(chart, "myapp-metrics-ingress", {
  service: metricsService,
  host: "myapp-metrics",
});
```

**External service reference:**

```typescript
new TailscaleIngress(chart, "external-ingress", {
  service: { name: "external-service", port: 443 } as unknown as Service,
  host: "external",
});
```

### When to Use Funnel

**Use Funnel for:** External webhook receivers, public-facing web apps, GitHub Actions integrations, OAuth callbacks.

**Do NOT use Funnel for:** Internal tools (Sonarr, Radarr), admin dashboards (ArgoCD, Grafana), database connections, sensitive services.

### Tailscale Operator Configuration

```typescript
// From src/cdk8s/src/resources/argo-applications/tailscale.ts
const tailscaleValues: HelmValuesForChart<"tailscale-operator"> = {
  oauth: { clientId: "...", clientSecret: "..." },
  operatorConfig: { hostname: "homelab-operator" },
};
```

### Debugging Tailscale Ingress

```bash
kubectl get ingress -A
kubectl describe ingress myapp-ingress -n media
kubectl logs -n tailscale deployment/tailscale-operator
tailscale status
nslookup myapp.tailnet-1a49.ts.net
```

## Container Property Composition

### withCommonProps

Applies base properties to all containers:

```typescript
import { withCommonProps } from "../misc/common.ts";

deployment.addContainer(
  withCommonProps({
    image: "myimage:latest",
    portNumber: 8080,
    // ... other props
  }),
);
```

**What it adds:**

- `TZ: America/Los_Angeles` environment variable
- Empty resources object (ready for limits)

### withCommonLinuxServerProps

Extends `withCommonProps` for linuxserver.io images:

```typescript
import { withCommonLinuxServerProps, LINUXSERVER_GID } from "../misc/linux-server.ts";

const deployment = new Deployment(chart, "myapp", {
  replicas: 1,
  strategy: DeploymentStrategy.recreate(),
  securityContext: {
    fsGroup: LINUXSERVER_GID,  // Important!
  },
});

deployment.addContainer(
  withCommonLinuxServerProps({
    image: `ghcr.io/linuxserver/myapp:${versions["linuxserver/myapp"]}`,
    portNumber: 8080,
    volumeMounts: [...],
  }),
);
```

**What it adds:**

- `PUID: 1000` and `PGID: 1000` environment variables
- `TZ: America/Los_Angeles`
- Security context allowing root (for permission fixing)

## Database Constructs

### Redis

Deploys Redis via ArgoCD with Bitnami Helm chart:

```typescript
import { Redis } from "../resources/common/redis.ts";

const redis = new Redis(chart, "myapp-redis", {
  namespace: "media",  // Use the appropriate service namespace
});

// Use in deployment
envVariables: {
  REDIS_HOST: EnvValue.fromValue(redis.serviceName),  // "myapp-redis-master"
  REDIS_PORT: EnvValue.fromValue("6379"),
},
```

**Features:**

- Standalone architecture (no replication)
- No authentication (internal use)
- No persistence (in-memory only)
- Auto-creates ArgoCD Application

### PostalMariaDB

Specialized MariaDB for Postal mail server:

```typescript
import { PostalMariaDB } from "../resources/postgres/postal-mariadb.ts";

const mariadb = new PostalMariaDB(chart, "postal-mariadb", {
  namespace: "postal",
  storageClass: "zfs-ssd",
  storageSize: "32Gi",
});

// Access properties
mariadb.serviceName; // "postal-mariadb"
mariadb.databaseName; // "postal"
mariadb.username; // "postal"
mariadb.secretItem; // OnePasswordItem for credentials
```

## Utility Patterns

### JsonPatch for Unsupported Fields

Add fields CDK8s doesn't expose:

```typescript
import { ApiObject, JsonPatch } from "cdk8s";

// Add GPU resource limits
ApiObject.of(deployment).addJsonPatch(
  JsonPatch.add("/spec/template/spec/containers/0/resources", {
    limits: {
      "gpu.intel.com/i915": 1,
    },
  }),
);

// Enable host networking
ApiObject.of(deployment).addJsonPatch(
  JsonPatch.add("/spec/template/spec/hostNetwork", true),
);
```

### OnePasswordItem for Secrets

```typescript
import { OnePasswordItem } from "../generated/imports/onepassword.com.ts";

const secrets = new OnePasswordItem(chart, "myapp-secrets", {
  spec: {
    itemPath: "vaults/xxx/items/yyy",
  },
});

// Reference in container
envVariables: {
  API_KEY: EnvValue.fromSecretValue({
    secret: Secret.fromSecretName(chart, "api-key-ref", secrets.name),
    key: "password",
  }),
},
```

### ConfigMap from Directory

```typescript
import { ConfigMap, Volume } from "cdk8s-plus-31";

const config = new ConfigMap(chart, "myapp-config");
config.addDirectory(`${import.meta.dir}/../../../config/myapp`);

const configVolume = Volume.fromConfigMap(chart, "myapp-config-volume", config);

// Mount individual files
volumeMounts: files.map((file) => ({
  path: `/config/${file}`,
  subPath: file,
  volume: configVolume,
})),
```

## Constants

```typescript
// Storage classes
export const NVME_STORAGE_CLASS = "zfs-ssd";
export const SATA_STORAGE_CLASS = "zfs-hdd";

// User/Group IDs
export const ROOT_UID = 0;
export const ROOT_GID = 0;
export const LINUXSERVER_UID = 1000;
export const LINUXSERVER_GID = 1000;
```

## Key Files

- `src/cdk8s/src/misc/zfs-nvme-volume.ts` - SSD volume construct
- `src/cdk8s/src/misc/zfs-sata-volume.ts` - HDD volume construct
- `src/cdk8s/src/misc/tailscale.ts` - Tailscale ingress construct
- `src/cdk8s/src/misc/common.ts` - Base container props
- `src/cdk8s/src/misc/linux-server.ts` - LinuxServer.io props
- `src/cdk8s/src/misc/storage-classes.ts` - Storage class constants
- `src/cdk8s/src/resources/common/redis.ts` - Redis construct
- `src/cdk8s/src/resources/postgres/postal-mariadb.ts` - MariaDB construct

Related Skills

toolkit-recall

15
from shepherdjerred/monorepo

Search past decisions, prior research, conversation history, monorepo docs, and fetched web pages. Use toolkit recall search to find context from previous work, and toolkit fetch to save web pages for future search.

zod-patterns

15
from shepherdjerred/monorepo

Zod schema validation, type-safe development, and strict TypeScript patterns. When user works with Zod, validates data, creates schemas, handles form validation, mentions z.object/z.string patterns, needs runtime validation, type-safe code, or strict TypeScript configuration.

zellij-helper

15
from shepherdjerred/monorepo

Zellij terminal multiplexer for session management, layouts, and pane operations When user mentions Zellij, terminal multiplexer, zellij commands, sessions, panes, layouts, or tabs

worktree-workflow

15
from shepherdjerred/monorepo

Git worktree workflow for isolated feature development and PR creation When user starts new work, needs to switch contexts, or wants parallel development

vite-react-helper

15
from shepherdjerred/monorepo

Vite + React for fast modern web development - build config, HMR, hooks, state management, and performance patterns When user works with Vite, React, creates components, manages state, uses hooks, or configures Vite builds

version-management

15
from shepherdjerred/monorepo

Use when asking about version management, Renovate annotations, versions.ts patterns, or pinning image/chart versions.

typst-authoring

15
from shepherdjerred/monorepo

This skill should be used when the user asks to "write Typst", "create a Typst document", "format in Typst", "convert to Typst", "Typst syntax", "Typst template", "Typst math", "Typst table", or works with .typ files. Provides comprehensive Typst markup, scripting, math, layout, and styling reference for authoring documents. Also use proactively when generating .typ output files (e.g., in deep-research reports).

typescript-helper

15
from shepherdjerred/monorepo

TypeScript development guidance for type systems and tooling When user works with .ts or .tsx files, mentions TypeScript, or encounters type errors

torvalds-deployment

15
from shepherdjerred/monorepo

Use when asking about adding services, createXxxDeployment patterns, or homelab deployment conventions. Services use per-namespace charts.

terraform-helper

15
from shepherdjerred/monorepo

Terraform and OpenTofu infrastructure as code - HCL, providers, modules, state management, and CLI operations When user works with .tf files, mentions Terraform, OpenTofu, tofu, HCL, infrastructure as code, or tf commands

terminal-concepts

15
from shepherdjerred/monorepo

Comprehensive guide for building CLI and TUI applications - terminal internals, design principles, and battle-tested patterns When building CLI/TUI apps, implementing argument parsing, handling terminal input/output, escape codes, buffering, signals, or asking about terminal development concepts

talos-helper

15
from shepherdjerred/monorepo

Talos Linux cluster administration using talosctl When user mentions Talos, talosctl, or Talos cluster operations