Skip to content

carapace-sh/carapace-bin / skills/kubeadm

kubeadm

Unverified

Use when working with the kubeadm CLI — bootstrapping Kubernetes clusters, init/join/reset/upgrade workflows, the phase system, certificate management, bootstrap tokens, kubeconfig generation, and the v1beta4 configuration API. Triggers on: "kubeadm", "kubeadm init", "kubeadm join", "kubeadm reset", "kubeadm upgrade", "kubeadm config", "kubeadm token", "kubeadm certs", "kubeadm kubeconfig", "kubeadm version", "kubeadm alpha", "bootstrap token", "InitConfiguration", "ClusterConfiguration", "JoinConfiguration", "ResetConfiguration", "NodeRegistrationOptions", "control-plane-endpoint", "discovery-token", "certificate-key", "feature-gates", "skip-phases", "static pod manifest", "TLS bootstrap", "kubeadm-config".

FileKindSize
SKILL.mdskill md5.1 KB
references/certs.mdmarkdown7.5 KB
references/concepts.mdmarkdown8.3 KB
references/config.mdmarkdown10.3 KB
references/flags.mdmarkdown6.7 KB
references/init.mdmarkdown7.8 KB
references/join.mdmarkdown7.1 KB
references/misc.mdmarkdown3.2 KB
references/phases.mdmarkdown9.4 KB
references/reset.mdmarkdown4.4 KB
references/token.mdmarkdown5.2 KB
references/upgrade.mdmarkdown7.7 KB

references/misc.md

View on GitHub
# kubeadm kubeconfig, version, alpha

The remaining kubeadm commands: `kubeconfig` for generating kubeconfig files for additional users, `version` for printing the kubeadm version, and `alpha` for experimental features.

> **Source of truth**: <https://kubernetes.io/docs/reference/setup-tools/kubeadm/>.

## kubeadm kubeconfig

Kubeconfig file utilities.

### Subcommands

| Subcommand | Purpose |
|------------|---------|
| `kubeadm kubeconfig user` | Output a kubeconfig file for an additional user |

### `kubeconfig user`

Generates a kubeconfig file for an additional user. The kubeconfig is printed to stdout — redirect to a file to save it.

```bash
kubeadm kubeconfig user --client-name dev-user > dev-user.conf
```

#### Flags

| Flag | Default | Description |
|------|---------|-------------|
| `--client-name` | (required) | Name of the user (used as the CN if client certs are created). |
| `--config` | — | Path to a kubeadm configuration file. |
| `--org` | — | Organizations of the client certificate (used as the O). Can be repeated. |
| `--token` | — | Use token authentication instead of client certificates. |
| `--validity-period` | `8760h0m0s` (1 year) | Validity period of the client certificate (offset from now). |

#### Examples

Generate a kubeconfig with a client certificate:

```bash
kubeadm kubeconfig user --client-name dev-user --org dev-team
```

Generate a kubeconfig with token authentication instead of a cert:

```bash
kubeadm kubeconfig user --client-name ci-bot --token abcdef.0123456789abcdef
```

Set a custom validity period:

```bash
kubeadm kubeconfig user --client-name temp-user --validity-period 720h
```

#### How It Works

The command connects to the cluster using the admin kubeconfig (`/etc/kubernetes/admin.conf`), generates a client certificate signed by the cluster CA, and embeds it in a new kubeconfig. The `--token` option skips cert generation and uses a bootstrap token instead.

## kubeadm version

Prints the version of kubeadm.

```bash
$ kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"30", GitVersion:"v1.30.0", ...}
```

### Flags

| Flag | Description |
|------|-------------|
| `-o, --output` | Output format: `yaml`, `json`, or `short` |

```bash
$ kubeadm version -o short
v1.30.0

$ kubeadm version -o yaml
gitVersion: v1.30.0
gitCommit: abc123...
gitTreeState: clean
buildDate: "2024-04-18T..."
goVersion: go1.22.2
compiler: gc
platform: linux/amd64
```

## kubeadm alpha

Preview features for gathering community feedback. This is a placeholder for experimental sub-commands.

Currently, there are **no experimental commands** under `kubeadm alpha`. Features that were previously here have either graduated to stable or been removed. The `alpha` command exists to provide a staging ground for future experimental features.

## References

- [kubeadm kubeconfig](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-kubeconfig/)
- [kubeadm version](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-version/)
- [kubeadm alpha](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-alpha/)

## Related

- [concepts.md](concepts.md) — kubeconfig files generated during init
- [certs.md](certs.md) — the CA that signs client certs for `kubeconfig user`
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall