Skip to content

Docs: Add hetzner provider how-to for deploying NKP#679

Open
andrewfulton9 wants to merge 12 commits into
nebari-dev:mainfrom
andrewfulton9:docs/nkp-hetzner-provider
Open

Docs: Add hetzner provider how-to for deploying NKP#679
andrewfulton9 wants to merge 12 commits into
nebari-dev:mainfrom
andrewfulton9:docs/nkp-hetzner-provider

Conversation

@andrewfulton9

@andrewfulton9 andrewfulton9 commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator

Reference Issues or PRs

#652

What does this implement/fix?

Adds an end to end how-to for deploying NKP on Hetzner with the nic CLI.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds a feature)
  • Breaking change (fix or feature that would cause existing features not to work as expected)
  • Documentation Update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Other (please describe):

Testing

  • Did you test the pull request locally?
  • Did you add new tests?

tested with nic deploy and destroy.

@netlify

netlify Bot commented Jun 3, 2026

Copy link
Copy Markdown

Deploy Preview for nebari-docs2 failed.

Name Link
🔨 Latest commit 2256f12
🔍 Latest deploy log https://app.netlify.com/projects/nebari-docs2/deploys/6a2b2a47f45a760008ca7bd7

@marcelovilla marcelovilla left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @andrewfulton9!

This is looking good on a first pass but there's one thing I'd like to flag:

There's a good amount of overlap between this how-to guide and the AWS one on things that are general rather than provider specific (e.g. installing nic, first sign-in, GitOps repo, etc...). @khuyentran1401 opened an issue about this and I think we should address preferably before merging, or promptly after it to avoid drift and to keep things tidy. I'm not implying you should be the one to do that work and I'd like to have @khuyentran1401's input on how to best achieve this.

@andrewfulton9

Copy link
Copy Markdown
Collaborator Author

There's a good amount of overlap between this how-to guide and the AWS one on things that are general rather than provider specific (e.g. installing nic, first sign-in, GitOps repo, etc...). @khuyentran1401 opened an issue about this and I think we should address preferably before merging, or promptly after it to avoid drift and to keep things tidy. I'm not implying you should be the one to do that work and I'd like to have @khuyentran1401's input on how to best achieve this.

linking #680 for tracking of this

Comment thread docs/docs/how-tos/providers/hetzner.mdx Outdated
@khuyentran1401

Copy link
Copy Markdown
Collaborator

I left one suggestion on the title. The docs looks good from the scan. I'll let the engineers look at the technical aspects of the docs.

@andrewfulton9

Copy link
Copy Markdown
Collaborator Author

I updated the hetzner page to link to the deploy page introduced into #686, until that PR is merged and this branch is updated, the CI for this PR will fail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo 📬

Development

Successfully merging this pull request may close these issues.

3 participants