The PaaS Console - Your Bridge to the Kubernetes Cluster
Console Web interface: https://console.paas.sikt.no/
Our Kubernetes cluster solution is designed to simplify and enhance your development and deployment processes. To facilitate this, we've created a web interface we call the "Console". The Console is responsible for connecting your GitLab project to our Kubernetes cluster.
Key Features of the Console
Connecting to the Kubernetes Cluster
GitLab Environments decide where code is deployed and is typically set for each job defined in your project .gitlab-ci.yml
file.
The Console allows you to connect your project in GitLab to our Kubernetes cluster. The Platon PaaS Console will:
- Create two namespaces for your project in Kubernetes:
- Production namespace
<full-group-path>-<project-name>
with GitLab environment scopeproduction
. - Development namespace
<full-group-path>-<project-name>-dev
with GitLab environment scope*
, meaning it will be where everything else gets deployed (review, staging, etc).
- Production namespace
- Add Kubernetes configurations in your GitLab project for the environment scopes, which allows GitLab to communicate with Kubernetes.
- Add the GitLab CI/CD variable
DOCKER_AUTH_CONFIG
to your project. This allows GitLab CI/CD to upload Docker images toregistry.uninett.no
.
Read how to set up your project with the console in the Getting started section.
Accessing kubectl Context
The Console provides you with the kubectl context needed to connect to the cluster. This gives you the capability to observe what's happening within your application and the cluster as a whole, offering valuable insight into your application's operation and performance.
You can read how how to use kubectl for troubleshooting your application in the kubectl section.
CronJobs Schedule Overview
For those who utilize CronJobs for scheduling tasks, the Console offers an overview of the CronJobs schedule. This feature allows you to monitor and manage your scheduled tasks effectively within the Kubernetes environment.