Brief Introduction #
User #
With user role you don’t have that much privileges and option like manager or partner role, but you can create clusters and manage them, see the overview of projects, servers or cloud credentials for your organization, manage your account and more.
In this guideline you can see how to login, use the dashboard or create a cluster.
Visit Login, Dashboard, Projects or My Profile to see more.
Login to Taikun #
First-time login #
After you receive the token in your mail, it will redirected you to the new page to create a new password.
Warning
The password should meets its conditions: 1 uppercase, 1 lowercase, 1 number, 1 non-alphanumeric and at least 6 signs long (e.g. Test@123)!

If you did not manage to use the token in time (3 hours), click Resend Token button and use the new token in your e-mail.

Login #
Enter your E-mail and the created Password then click LOGIN button. The LOGIN button is disabled until you fill in both fields.

You are immediately redirected to the Dashboard.
Wrong Credentials #
If you enter the wrong password, you receive the error message Bad credentials.

Forgotten password #
If you don’t remember your password, use Forget your password? button.

A token is sent to your e-mail, clicking the link you will be redirected to the page where you can reset your password like when you want to login for the first time.
Dashboard #
You can access the Dashboard by clicking upper left Taikun logo or the Dashboard in the tabs:

On Dashboard you can find:
- Users
- Pie charts (Projects, Server Statuses, Servers, Cloud Credential, Nodes Overview, Pod overview, Project with Alerts and Kubernetes Health)
- Tables (Kubernetes, Project Resource Allocation and Recent Events)
Header #
On every page in the upper right corner you can see:


- logo of your organization

- link to this documentation, variable for every page

- global search – search for projects or servers, case insensitive, can be open with double shift at every page
- Taikun search – search through projects
- Kubernetes Search – have to be checked (as searching kubernetes takes longer time) and search through all active kubernetes

- real-time notifications
- General – notifications about changes made in projects (e.g. created project, enable monitoring, change of status), for details see Dashboard – Recent Events
- Alerts – new/persisting (red) or resolved (green) alerts, see Projects – Alerts

- your information and setting, see My Profile
- if your display name is changed, the name can be seen in the corner User Role
Users #
Shows how many Users are involved in your organization.

To find the information about your profile visit My Profile.
Charts #
Projects #
The graph shows number of Projects (right corner) for your organization and the pie chart shows their current status (pointing arrow at some part of the graph):
- Failed
- Succeeded
- Pending
- Updating

By clicking the specific part in graph, you see an overview of selected projects.
For more information visit Projects.
Server Statuses #
In the right corner is number of Servers and the pie chart shows their current status (pointing arrow at some part of the graph):
- Failed
- Succeeded
- Pending
- Updating

By clicking the specific part in graph you see an overview of selected servers.
Servers #
In the right corner is shown number of all Servers for your organization. The graph shows where the servers are hosted (AWS, Azure, OpenStack). When you point at a column, exact number of servers used is shown.

Cloud Credentials #
In the right corner is shown number of Cloud Credentials. The graph shows which cloud (AWS, Azure, OpenStack) and how many of each type are used. When you point to a column, the exact number of cloud credentials used is shown. In the right corner is number of all cloud credentials.

Nodes overview #
In the right corner is shown number of Nodes and the pie chart shows their current status (pointing arrow at some part of the graph):
- Healthy
- Unhealthy

By clicking the graph you see Kubernetes overview, where you can find Projects with number of Healthy and Unhealthy Nodes.
Pods overview #
In the right corner is shown number of Pods and the pie chart shows their current status (pointing arrow at some part of the graph):
- Healthy
- Unhealthy

By clicking the graph you see Kubernetes overview, where you can find Projects with number of Healthy and Unhealthy Pods.
Projects with Alerts #
In the right corner is shown number of all alerts and the pie chart shows how many alerts has each project (pointing arrow at some part of the graph):

By clicking the graph you see Kubernetes overview, where you can find Projects with number of alerts.
For more information see Projects – Alerts.
Kubernetes Health #
In the right corner is shown number of Non-Healthy items and the pie chart shows status for all projects with active kubernetes (pointing arrow at some part of the graph):
- Healthy
- Unhealthy
- Warning
- Unknown

By clicking the graph you see Kubernetes overview, where you can find Projects (with kubernetes) with its kubernetes health status.
For more information see Projects- Health.
Tables #
Kubernetes #
The Kubernetes chart consists of 3 main sections:
- Project
- Nodes
- Pods

Projects
In the right corner you can switch between Projects with Kubernetes (to which you are assigned to).
Nodes
Lists Nodes by Name and shows status of Disk, Memory, PIDs and Ready (Status of the Node).
Status: working
Status: not wokring
Pods
For every Pod (characterized by Pod Name) is listed its Namespace, Node, Restart Count, Age and Status.
If the status is failed, you can check the pod in Kubernetes section – use the link in Nodes – Metadata Name or Pods – Pod Name.

For more information see Projects – Kubernetes.
Project Resource Allocation #
In this section you can see how the usage of CPUs, RAM and Disk Size are divided between the individual projects. The last column Total shows the sum of all projects for CPU, RAM or Disk Size. You can also sort CPU, RAM and Disk Size by Usage or Limit (if there is any).

The pie charts shows percentage of usage of each project:
Green – small usage
Yellow – normal usage
Orange – higher usage
Red – full usage
Recent Events #
Lists 10 events from the latest. Green ones are successful events, red ones are failed. The update button is in the right corner.

Warning
If there is a real-time change, you are notified Notifications ?
Notifications
General
Whenever user makes a change (create project, add backup, delete project etc.) you are notified via bell at the top of the page.
The colors indicate:
- green – successful action
- red – failed action

Alerts
Notifications for projects when alert starts or is resolved (e.g. Kubernetes health status), you are also notified via bell at the top of the page.
- green – resolved problem
- red – problem

The notification contains a brief message on a specific project and bellow the message is time of the change. After clicking Show Project, you will access the project in which the change was made.
Info
As the name suggests: Mark as Read and Dismiss all.
Projects #
On the Projects tab, you can preview all existing projects to which you are assigned.

Each project is described by following information:
ID, Project Name, Organization Name #
Changeless descriptions for each Project.
View #
Link to your Kubernetes or Virtual Machines part of your project.
Status #
Status shows the current status and actions of your servers in the project in real-time. Below are all possible statuses listed with their description.
- Ready
- all servers in the project are ready without any issues
- Deleting
- one or more servers in your current project are being deleted
- Failure
- one or more servers failed during the action for any reason (for instance during boot or creation)
- Pending
- one or more servers are in a pending state, which means that, for instance, they have not yet been created on the hosted platform
- Updating
- one or more servers in the project are being updated by Taikun during the creation process
- Upgrading
- one or more servers upgrade Kubernetes, cloud credentials or others
Health #
This column describes a condition of the project cluster. Keep in mind that a good-working project should be always Healthy.
- Healthy
- cluster id without any further problems
- None
- cluster is probably empty, there is nothing to check
- Unhealthy
- problems with connection to Kubernetes or Monitoring API
- Unknown
- cannot connect Kubernetes API
- Warning
- minor issues
Creation Date #
The exact time stamp when the project was created.
Kubernetes Version #
Shows current Kubernetes version for each project.
Cloud Type #
Shows which provider is hosting your project cluster
- AWS
- Azure
- OpenStack
K8’s #
Kubernates active
Kubernetes not active
Expiration Date #
See durability of a project. By default, the expiration date of project is set to infinity.
Warning
After the expiration date, your project is NOT affected, deleted or lock. It will stays the same.
Show hidden columns #
Click small arrow on the right side of the table to see more details.

Expand the table to see:
- Alerts count – number of firing alerts in a project
- Created By
- Last Modified
- Last Modified By
Sorting #
Projects can be sorted by Project Name, Status, Creation Date, K8s version, Cloud Type and Expiration Date. Also the search bar can be used to find some specific project.
Project Details – K8s #
By clicking the selected project or K8s View you are redirected to the Kubernetes Servers. Here you can see all K8s servers for the project with their description.

Project Info #
Under Servers title is a brief description of the project – such as Project Name (with locked/unlocked image), Project Status, Cloud Type, Kubernetes Version, Access Profile, Cloud Credentials, Kubernetes Profile, Alerting Profile, Policy Profile, Access IP Address (if you use this address to ssh connect, please do not use user ubuntu, it’s in use by Taikun for managing the cluster) and Kubernetes Health.

You can also see here ETC=Estimated Time to Complete. It is approx time (in minutes) until the cluster will be completed.

Servers #
Every Server is described by ID, Server Name, IP Address, Flavor, CPU/RAM/Disk Size, Role, Status, Kubernetes Health and Creation Time. If you expand the table, you can see the last modification made (Created By, Last Modified, Last Modified By).

Server status can be:
- Deleting
- Failure
- Pending
- Pending Delete
- Pending Upgrade
- Ready
- Updating
- Upgrading
Actions #
Upgrade #
Upgrade your version of Kubespray to the latest one. The button is disabled, if your Kubernetes are up to date. Also if you checked Auto Upgrade during creation.
Commit #
Sends the changes to the repository. Once the cluster is committed you will see ETC in project info.
Repair #
When the server/s are Failed or there is some other problem in the cluster, use repair button.

Warning
If the project is locked ? which you can see under Project Info, you can only preview some pages (e.g. Kube Info). You can’t make any changes.
Add Server #
To create a new server click button and fill all the fields. You, as user, can’t delete servers – think twice which and how many servers you want to create.

Server Name – only alphanumeric characters and dash are allowed, 1-30 characters
Warning
Letters must be lowercase!
Disk size – should be at least 30GB
Role – you are able to choose from several roles for your servers, which are set according to the Kubernetes settings
Number of Servers – set number for kubeworker or kubemaster, add odd number of masters (min. 3 for a highly available cluster)
Warning
The change MUST be committed.
Flavor – choose from the list of offered flavors (e.g. n0.large)
Info
Recommendation for sizing:
* bastion recommended 2 vCPU + 2GB of RAM
* masters recommended 4 vCPU + 8GB of RAM
Kubernetes Node Labels – label nodes where you want to sent or restrict pods; you can add more labels with add label button, for more info see Kubernetes docs.
Function buttons #
Under Add Server are buttons with specific features or more detailed information.

Kubeconfigs #
Add a new kubernetes configuration for your profile and project.

Kubeconfig Name – choose a name for your kubeconfig (3-230 characters)
Kubeconfig Role
- cluster-admin – perform any action on any resource, ClusterRoleBinding – gives full control over every resource in the cluster and in all namespaces (or in very resource in the role binding’s namespace – RoleBinding)
- admin – RoleBinding – allows read/write access to most resources in a namespace, does not allow write access to resource quota or to the namespace itself
- edit – allows read/write access to most objects in a namespace, does not allow viewing or modifying roles or role bindings, allows accessing Secrets and running Pods as any ServiceAccount in the namespace
- view – see most objects in a namespace, does not allow viewing roles or role bindings, does not allow viewing Secrets
Info
For more info, see kubernetes documentation.
Personal Kubeconfig – kubeconfig can be used only by you
You can see all project’s configurations in the table with its ID, Name, User Name, User Role, Project, Accessible for all, Konfig Role Name, Created By and Actions.

Actions
This .yaml file can be download and use to organize information about clusters, users, namespaces, and authentication mechanisms.
Delete your kube config if it is no longer needed.
K8s Info #
If Kubernetes is active, Kube Info button will take you to the Kubernetes configuration. For more see Projects – Kubernetes.
Events #
You are redirected to Events, where you can see all Kubernetes changes made in the project. To preview details for more information to each action usebutton. A green strip indicates a successful action, a red strip indicates a failed action. Use Clear events for deleting all the events.
You can sort Events by:
- Search field
- Filling Start and End Date
- Tick Only failed to filter failed actions

Logs #
Preview Kubernetes cluster logs to Grafana. Logs button is disabled if Monitoring is disabled.

Write your query and use Start date and End Date for sorting. You can also expand every message – red is added action, no color is other.

Alerts #
First thing when you access Alerts are Firing Alerts. This section is refreshed every 5 minutes, but you can also use the refresh button to see the most updated data.

To see all alerts, use upper right Show All Alerts button. As seen above, firing alerts are marked with red color. For each alert you can see details and use a link that will redirected you to Metrics with the query already written.
Alerts are accessible only if Monitoring is enabled and the project is not empty.

The index number at Alerts shows the number of firing alerts. When the firing alerts are resolved, the number disappears.
Firing alerts also work from the real-time notifications bell in the header. Red ones are indicate alert, green ones means that the alert is resolved.

The notification contains a brief message on a specific project and bellow the message is time of the change. After clicking Show Project, you can access the project in which the alert is.
As the name suggests: Mark as Read and Dismiss all.
Metrics #
Write a query, search Prometheus Metrics and preview the value needed. Modify Step or Date.
Switch between Console and Graph for better results.

Project Dashboard #
Dashboard is accessible only if cluster is created and monitoring is enabled.

Here you can see graphs with Memory and CPU usage for the project. You can also see added Query from Manager or Partner.
Project Details – VMs #
By clicking VMs button in Servers page or VMs View in Project page you are redirected to the VMs Servers. Here you can see all virtual machines for the project with their description.

Project Info #
Under Servers title is a brief description of the project – such as Project Name (with locked/unlocked image), Project Status, Cloud Type or Cloud Credentials.

When there is some operation going on, you can also see here ETC=Estimated Time to Complete. It is approx time (in minutes) until the cluster will be completed.

Servers #
Every Server is described by ID, Name, Flavor, IP Address, Public IP Address, Status, Profile, Image and Created. If you expand the table, you can see the last modification made (Created By, Last Modified, Last Modified By).

Server status can be:
- Deleting
- Failure
- Pending
- Pending Delete
- Pending Upgrade
- Ready
- Updating
- Upgrading
Actions #
Commit #
Sends the changes to the repository.
Once the cluster is committed you will see ETC in project info.
Repair #
When the server’s are Failed, use repair button.

Add VM #
To create a new server click button and fill all the fields. You, as user, can’t delete servers – think twice which and how many servers you want to create.
Warning
For creating the VM: Image has to be bound and Stanalone Profile has to be created. Please contact your manager if these fields are empty.

Server Name – only alphanumeric characters and dash are allowed, 1-30 characters
Warning
Letters must be lowercase!
Flavor – choose from the list of offered flavors (e.g. n0.large)
Image – choose from the list of offered images (e.g. ubuntu-20.04)
Volume Size – minimal size is automatically filled in when you select image, you can only increase the volume size number
Volume Type – optional, choose from drop down selection
Profile – choose Standalone profile
Count – how many VMs you want to create
Public IP – check if you want to enable public IP
Cloud-init – optional, if set it will override the ssh key from standalone profile
Tags – enter Key and Value
Disk – enter Name, choose Size and select Volume Type
Info
If the project is locked ? which you can see under Project Info, you can’t use Commit, Repair or Add VM.
Kubernetes #
To access Kubernetes go to Projects – Servers – K8s Info or use the K8s buttonin Projects.

In Kubernetes tab can be found:
- Nodes
- Message, Reason, Status and Type
- Deamon Set
- Namespace, Name, Status and Age
- Persistent Volume Claim
- Namespace, Name, Phase, Size, Storage Class Name and Age
- Deployment
- Namespace, Name, Status and Age
- Config Map
- Namespace, Name and Age
- Secret
- Namespace, Name and Age
- Sts
- Namespace, Name, Status and Age
- Service
- Namespace, Name, Type, External IP and Age
- Pods
- Namespace, Name, Node Name, Age, Status, Restart Count, Kill Pod, Terminal and Logs
- Ingress
- Namespace, Name, Hosts and Age
- Ingress
- Namespace, Name, Hosts and Age
- CRD (Custom Resource Definition)
- Name, Group, List Kind, Spec name kind, Labels and Age
- PDB (Pod Disruption Budgets)
- Namespace, Name and Created At
Warning
Please do NOT deploy any apps in monitoring Service, because Taikun uses the monitoring namespace heavily! And if you disable the monitoring, all pvc in monitoring will be deleted.

You can use sort buttons or search button in each section for easier searching.
Info
Except Pods tab are all tabs for preview only.
Actions #
Show description – for all tabs except Nodes
Pods #
Kill Pod #
Pod can be killed with Kill Podbutton.
Terminal #
Open Terminal to control your container/s.

Logs #
Logs record events happening in cluster. You can check the logs for more details. To search the logs visit Projects – Project Details – Logs.

My Profile #
You can access your profile and its settings by clicking in the right upper corner of the page.
My Information #
Here you can see your User Name, Organization Name, Subscription End Date, E-mail and Role.

Settings #

In Settings section you can:
- Change your password
- Change your e-mail
- Enable e-mail notifications from Taikun
- Delete Account
Change E-mail #
You just need to type your new e-mail, which you want to use in the future.

Your e-mail address is changed but not confirmed, which is indicated with red cross next to your e-mail in My Information.

Clicking the Confirm E-Mail button will send the confirmation token to the e-mail address provided by you. Use the link in the mail to confirm your mail. If the link redirects you to homepage of Taikun, please login first and click the link in the e-mail again.
Token expires after 1 hour and then you need to send it with Confirm E-mail button again.

Info
You can’t change e-mail address until your current one is confirmed.
Change Password #
To change your password, you have to insert your current password (old) and new (different) one.
Password should contain at least 1 uppercase, 1 lowercase, 1 number, 1 non alphanumeric and minimum length is 6 signs (e.g. Test@123).
Warning
If you receive an error during changing the password, please check it meets the conditions.

Warning
After confirming the password (by clicking the update button), you are logged off and need to log in with the new password.
Delete Account #
If you no longer wish to use Taikun, permanently delete your account. You will lose all access to Taikun.