Skip to content

Add NIC installation docs#649

Open
pavithraes wants to merge 3 commits into
nebari-dev:mainfrom
pavithraes:nic-install
Open

Add NIC installation docs#649
pavithraes wants to merge 3 commits into
nebari-dev:mainfrom
pavithraes:nic-install

Conversation

@pavithraes
Copy link
Copy Markdown
Member

@pavithraes pavithraes commented May 4, 2026

Reference Issues or PRs

Closes #646

What does this implement/fix?

Documentation Update

Acceptance criteria

  • /docs/get-started/install has the necessary installation instructions

Testing

  • Did you test the pull request locally?

Access-centered content checklist

Text styling

  • The content is written with plain language (where relevant).
  • If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
  • All links describe where they link to (for example, check the Nebari website).
  • This content adheres to the Nebari style guides.

Non-text content

  • All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
  • If there are emojis, there are not more than three in a row.
  • Don't use flashing GIFs or videos.
  • If the content were to be read as plain text, it still makes sense, and no information is missing.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 4, 2026

Deploy Preview for nebari-docs2 ready!

Name Link
🔨 Latest commit 666abc1
🔍 Latest deploy log https://app.netlify.com/projects/nebari-docs2/deploys/6a030c6e5e9ab70008657d17
😎 Deploy Preview https://deploy-preview-649--nebari-docs2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@pavithraes pavithraes marked this pull request as ready for review May 12, 2026 11:18
Ensure this location in on your user PATH with `echo $PATH`.
If not, you can add it to PATH with `export PATH=$PATH:/path/to/dir`.

:::info[MacOS verification error]
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I ran into this error, so added a workaround. Ideally, this should not be required, and the installation is streamlined. I can open a separate issue on the nic repo.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Agreed, the workaround makes sense to keep here for now. Could you drop the NIC issue link in this thread once it's open, so we know when to remove this callout?


# Install NIC

Nebari Infrastructure Core (NIC) provisions a production-grade platform (Kubernetes cluster).
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This intro is not strictly required, but I think it's useful to provide some context around why installing this particular library is the first step.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I had to pause on this sentence. The parenthetical made it hard to tell whether "production-grade platform" and "Kubernetes cluster" are the same thing or two different things. Could we spell out the layering, e.g. "Nebari Infrastructure Core (NIC) is a CLI that sets up a production-grade Kubernetes cluster and installs the platform essentials that run on top of it."?

Extract the tarball:

```sh
tar -xzf nic_v0.2.0_xyz.tar.gz
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The nic_v0.2.0_xyz.tar.gz example doesn't match what's on the releases page. The actual assets follow nebari-infrastructure-core_0.3.0_darwin_arm64.tar.gz. Could we use a real filename here so users can map it back?

# Install NIC

Nebari Infrastructure Core (NIC) provisions a production-grade platform (Kubernetes cluster).
It is the foundational layer of the Nebari ecosystem, that includes platform essentials like authentication (SSO), user management, observability, TLS certification, and more. You can set up software packs (like the data science pack with specific tools like JupyterLab) on top of this layer.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The NIC summary and README both describe the Data Science Pack as "JupyterHub and conda-store". JupyterHub is the user-facing tool (it serves JupyterLab to each user), so I think "JupyterHub" would be a touch more accurate as the example here. Small thing.

sudo mv nic /usr/local/bin/
```

Ensure this location in on your user PATH with `echo $PATH`.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Ensure this location in on your user PATH with `echo $PATH`.
Ensure this location is on your user PATH with `echo $PATH`.


# Install NIC

Nebari Infrastructure Core (NIC) provisions a production-grade platform (Kubernetes cluster).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I had to pause on this sentence. The parenthetical made it hard to tell whether "production-grade platform" and "Kubernetes cluster" are the same thing or two different things. Could we spell out the layering, e.g. "Nebari Infrastructure Core (NIC) is a CLI that sets up a production-grade Kubernetes cluster and installs the platform essentials that run on top of it."?

Extract the tarball:

```sh
tar -xzf nic_v0.2.0_xyz.tar.gz
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
tar -xzf nic_v0.2.0_xyz.tar.gz
tar -xzf nebari-infrastructure-core_0.3.0_darwin_arm64.tar.gz

Ensure this location in on your user PATH with `echo $PATH`.
If not, you can add it to PATH with `export PATH=$PATH:/path/to/dir`.

:::info[MacOS verification error]
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Agreed, the workaround makes sense to keep here for now. Could you drop the NIC issue link in this thread once it's open, so we know when to remove this callout?

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.

Get started: Installation

2 participants