The Nautilus Cluster is a globally distrubuted Kubernetes cluster.
The general guide of getting access to the Nautilus Cluster can be found here. The guidance in this page is tailored to NU users:
After a successful authentication you will login on the portal.
On first login you become a guest. Any admin user can validate your guest account, promote you to user and add your account to their namespace. You need to be assigned to at least one namespace (usually a group project but can be your new namespace).
To get access to a namespace, please contact its owner (usually email). Once you are granted the user role in the cluster and are added to the namespace, you will get access to all namespace resources.
If you’re starting a new project and would like to have your own namespace, either for yourself or for your group, you can request to be promoted to the admin by contacting NRP admins through Matrix.
This will give you permission to create any number of namespaces and invite other users to your namespace(s). Please note, you’ll be the one responsible for all activity happening in your namespaces.
Once you are made either a user or admin of a namespace, you’ll need to accept the Acceptable Use Policy (AUP) on the portal page (as shown in the screenshot below) in order to get access to the cluster.
Please review Policies before starting any work on the Nautilus Cluster.
Now you have been given access to the Nautilus Cluster. To interact with the cluster, you need to configure a client with the kubectl
command-line tool. A client can be your desktop or laptop computer, a virtual machine, or a terminal environment.
Install the kubectl tool
Login to NRP Nautilus portal
Click the Get Config link on top right corner of the page to get your configuration file.
Save the file as config and put the file in your <home>/.kube folder. This folder may not exist on your machine, to create it execute from a terminal:
mkdir ~/.kube
Test kubectl can connect to the cluster using a command line tool:
kubectl get pods -n your_namespace
It’s possible there are no pods in your namespace yet. If you’ve got No resources found.
, this indicates your namespace is empty and you can start running in it.