Skip to content

Commit

Permalink
clarifying and adding documentation link
Browse files Browse the repository at this point in the history
  • Loading branch information
julienchastang committed Dec 5, 2024
1 parent 23416cc commit d0f20b0
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .org/openstack/readme.org
Original file line number Diff line number Diff line change
Expand Up @@ -791,7 +791,7 @@ and get a list of the nodes:
:CUSTOM_ID: h-1991828D
:END:

! *THINK before you type here because if you scale with an updated Ubuntu VM ID with respect to what is running on the cluster, you may wipe out your cluster* ! [[https://github.com/zonca/jupyterhub-deploy-kubernetes-jetstream/issues/54][See the GitHub issue about this topic]].
! *THINK before you type here because if you scale with an updated Ubuntu VM ID with respect to what is running on the cluster, you may wipe out your cluster* ! [[https://github.com/zonca/jupyterhub-deploy-kubernetes-jetstream/issues/54][See the GitHub issue about this topic]]. *Also*, the if adding many nodes, see section on [[#h-E988560D][Large Clusters with Many VMs]].

You can augment the computational capacity of your cluster by adding nodes. In theory, this is just a simple matter of [[#h-F44D1317][adding worker nodes]] in =jetstream_kubespray/inventory/$CLUSTER/cluster.tfvars= followed by running:

Expand Down
2 changes: 1 addition & 1 deletion openstack/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -766,7 +766,7 @@ kubectl get nodes --all-namespaces

### Adding Nodes to Cluster

! **THINK before you type here because if you scale with an updated Ubuntu VM ID with respect to what is running on the cluster, you may wipe out your cluster** ! [See the GitHub issue about this topic](https://github.com/zonca/jupyterhub-deploy-kubernetes-jetstream/issues/54).
! **THINK before you type here because if you scale with an updated Ubuntu VM ID with respect to what is running on the cluster, you may wipe out your cluster** ! [See the GitHub issue about this topic](https://github.com/zonca/jupyterhub-deploy-kubernetes-jetstream/issues/54). **Also**, the if adding many nodes, see section on [Large Clusters with Many VMs](#h-E988560D).

You can augment the computational capacity of your cluster by adding nodes. In theory, this is just a simple matter of [adding worker nodes](#h-F44D1317) in `jetstream_kubespray/inventory/$CLUSTER/cluster.tfvars` followed by running:

Expand Down

0 comments on commit d0f20b0

Please sign in to comment.