Skip to content

Access the platform

Everything on the platform is an API object, so you can operate it with the tools your team already uses. Anything the web console does, the Kubernetes API does.

Welcome mails

An order in the shop ends in two mails to the contact of the order, with a copy to info@grn.cloud:

Mail When What it holds
Your GRN.CLOUD cloud account is ready once, when your first order is provisioned on a cluster the console address and your login: your account is in the GRN.CLOUD identity realm, and the mail links to the password reset so you set your own password first
Your <app> is ready at <hostname> for every app you ordered, when it is reachable the address of the app and the link to its Application in the console, where its generated secrets are

Until the account mail arrives the console refuses the login; the app mail can only follow it. Managed apps explains what the Application is.

Web console

The console handles cluster, workload, virtual machine and storage management, plus the developer catalog and the AI/ML workbenches. Use it to inspect what exists and to try an operation once; anything you will repeat belongs in a manifest.

Command line

The platform is driven with oc, the OpenShift CLI. It is a superset of kubectl — every kubectl command works under oc, plus OpenShift-specific ones like oc new-project and oc adm. These docs use oc throughout.

brew install openshift-cli

curl -LO https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/openshift-client-linux.tar.gz
tar -xzf openshift-client-linux.tar.gz oc
sudo install -o root -g root -m 0755 oc /usr/local/bin/oc

Download openshift-client-windows.zip from the OpenShift client mirror and add oc.exe to your PATH.

Match the client to the cluster

The console's Command Line Tools page serves the oc build that matches your cluster version. Prefer it over a package manager if you hit a version mismatch.

Log in

oc login --token=<your-token> --server=<your-cluster-api-endpoint>
oc project myapp-dev

Get your token and API endpoint from the console under Copy login command.

Treat tokens as credentials

A login token grants everything your account can do. Do not commit one to Git, paste it into an issue, or share it in chat. Use a service account token with a narrow role for automation — see below.

Verify

oc whoami
oc get all -n myapp-dev

Tokens for automation

For CI, scripts and agents, create a service account and bind it the narrowest role that works:

oc create serviceaccount deployer -n myapp-dev
oc adm policy add-role-to-user edit -z deployer -n myapp-dev
oc create token deployer -n myapp-dev --duration=24h

Short-lived tokens are preferred. Rotate long-lived ones on a schedule.

Helm, GitOps and the API

  • Helm — standard charts, no platform-specific packaging
  • GitOps — Argo CD reconciles manifests, charts and Operators from your repository
  • Kubernetes API — the primary interface; the console and CLI are clients of it

See Reference for API, CLI and SDK details.

Next

Pick a guide and deploy something.