Skip to content

docs: remove the deploy lifecycle page after the topic split #700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khuyentran1401 wants to merge 5 commits into
base: main
Choose a base branch
from
Open

docs: remove the deploy lifecycle page after the topic split #700

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3b2a279
Merge remote-tracking branch 'origin/docs/keycloak-auth' into docs/re…
khuyentran1401 Jun 18, 2026
40e28ed
docs: remove the deploy lifecycle page
khuyentran1401 Jun 18, 2026
a3ea57e
Merge branch 'main' into docs/remove-deploy-page
khuyentran1401 Jun 19, 2026
5697c0b
Merge remote-tracking branch 'origin/main' into docs/remove-deploy-page
khuyentran1401 Jun 19, 2026
b7b7488
docs: reword what your team gets so NKP reads as running on the cluster
khuyentran1401 Jun 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 0 additions & 46 deletions docs/docs/how-tos/deploy.mdx
View file
Open in desktop

This file was deleted.

5 changes: 3 additions & 2 deletions docs/docs/how-tos/providers/aws.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,10 @@ This guide walks through deploying NKP on AWS with `nic` (the Nebari Infrastruct

## What your team gets

When `nic deploy` finishes, your team will have all [standard NKP services](/docs/how-tos/deploy#what-every-deployment-includes) plus:
When `nic deploy` finishes, your team will have:

- **A managed Kubernetes cluster** ready for workloads (AWS EKS, multi-AZ by default).
- **Single sign-on, automatic TLS, and ingress**, all configured.
- **A managed Kubernetes cluster** (AWS EKS, multi-AZ by default) running it.
- **Optional shared storage** ([EFS](https://aws.amazon.com/efs/)) that pods on any node can mount when enabled in your config.

## Prerequisites
Expand Down
11 changes: 6 additions & 5 deletions docs/docs/how-tos/providers/hetzner.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,10 @@ Hetzner is the recommended starting point for most teams: it is the cheapest pro

## What your team gets

When `nic deploy` finishes, your team will have all [standard NKP services](/docs/how-tos/deploy#what-every-deployment-includes) plus:
When `nic deploy` finishes, your team will have:

- **A k3s Kubernetes cluster** ready for workloads (single-node or multi-node, your choice).
- **Single sign-on, automatic TLS, and ingress**, all configured.
- **A k3s Kubernetes cluster** (single-node or multi-node, your choice) running it.
- **Shared RWX storage** that pods on any node can mount ([Longhorn](https://longhorn.io/), installed automatically — Hetzner's native CSI is read-write-once only).

## Prerequisites
Expand Down Expand Up @@ -120,7 +121,7 @@ For the full schema (autoscaling, `persist_data`, Longhorn options), see the [NI

## Deploy

Run the deploy commands as described in [Deploy and verify](/docs/how-tos/deploy#deploy-and-verify) in the deploy lifecycle guide. Allow 10–15 minutes for the first deployment — k3s cluster creation followed by ArgoCD syncing foundational services.
Run the deploy commands as described in [Deploy a cluster](/docs/how-tos/deploy-cluster). Allow 10–15 minutes for the first deployment — k3s cluster creation followed by ArgoCD syncing foundational services.


See [Cloudflare DNS](/docs/how-tos/cloudflare-dns) for DNS setup (Cloudflare or manual A record).
Expand All @@ -133,7 +134,7 @@ See [Cloudflare DNS](/docs/how-tos/cloudflare-dns) for DNS setup (Cloudflare or
export KUBECONFIG=~/.cache/nic/hetzner-k3s/<project_name>/kubeconfig
```

Then follow the [Deploy and verify](/docs/how-tos/deploy#deploy-and-verify) steps in the deploy lifecycle guide to check the cluster and ArgoCD applications.
Then follow the [Verify](/docs/how-tos/deploy-cluster#verify) steps in the Deploy a cluster guide to check the cluster and ArgoCD applications.


## First sign-in
Expand All @@ -150,7 +151,7 @@ Changing `location` or `project_name` triggers destructive resource recreation.

## Destroy

Run the destroy commands as described in [Destroy](/docs/how-tos/deploy#destroy) in the deploy lifecycle guide.
Run the destroy commands as described in [Destroy a cluster](/docs/how-tos/destroy-cluster).

`nic destroy` removes the k3s cluster (all servers), the Hetzner load balancer, and automatically cleans up orphaned Longhorn/CSI block volumes and any load balancers left behind by in-cluster controllers.

Expand Down
1 change: 0 additions & 1 deletion docs/sidebars.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,6 @@ module.exports = {
link: { type: "doc", id: "how-tos/index" },
items: [
"how-tos/prepare-to-deploy",
"how-tos/deploy",
"how-tos/deploy-cluster",
"how-tos/cloudflare-dns",
"how-tos/update-cluster",
Expand Down
Loading