Skip to main content

Frequently asked questions

Find here the answers to the most common questions about using Hikube. Each service also has its own FAQ.

1. How do I access Hikube?​

Sign in to the console: https://console.hikube.cloud, with the credentials provided by Hidora. If you do not have an account yet, contact sales@hidora.io.

See: Quick start

2. What is the difference between an organization and a project?​

The organization represents your company; it is created by Hidora. Projects are the isolated spaces you create within the organization to group your resources, each with its own quotas. In older versions of the documentation, a project was called a tenant.

See: Key concepts

3. How do I retrieve the kubeconfig of my Kubernetes cluster?​

Open Infrastructure → Kubernetes, click your cluster, then Kubeconfig. The console downloads the kubeconfig-<cluster-name>.yaml file.

This file grants administrator access to the cluster: downloading it is reserved for project administrators. For other members, the Kubeconfig button is disabled with the note "Reserved for project administrators."

export KUBECONFIG=~/.kube/kubeconfig-<cluster-name>.yaml
kubectl get nodes

See: Kubernetes - Quick start

4. Do I still need a kubeconfig to manage my Hikube resources?​

No. VMs, disks, buckets, networks, Kubernetes clusters and databases are created and managed from the console, and automated with the public API. The project kubeconfig is no longer available; the legacy Terraform method that relied on it is retired.

The kubeconfig of a Kubernetes cluster (question 3), on the other hand, remains the normal way to access that cluster.

5. Where do I find my database credentials?​

On the detail page of the database cluster in the console (DB & Messaging → service → cluster). The users, their passwords and the connection host are shown there.

See: PostgreSQL, MariaDB, MongoDB, Redis, RabbitMQ

6. How do I expose a database to the Internet?​

Enable the External access option when creating the cluster or in Edit. A public IP is then assigned and shown in the External zone of the detail page. For a MongoDB replica set, the zone lists the address of each member.

To connect from a VM or a Kubernetes cluster of the same project, external access is not needed: use the host in the Internal zone, which is always shown.

warning

Only expose a database if necessary, and use strong passwords.

7. How do I choose the size of my resources?​

The creation wizards offer predefined sizes:

  • VMs and Kubernetes nodes: instance types from the s1, u1 and m1 series (from 1 to 64 vCPU). See Kubernetes concepts and Virtual machine concepts.
  • Managed databases and RabbitMQ (PostgreSQL, MariaDB, MongoDB, Redis, RabbitMQ): the VM sizes, from the u1, s1 and m1 series, from s1.small (1 vCPU, 2 GB) to m1.8xlarge (32 vCPU, 256 GB). A size has the same resources as the VM of the same name: u1.medium is 1 vCPU and 4 GB. See the Concepts page of each service.
  • Kubernetes control plane: s1.small (1 vCPU, 2 GB) or s1.medium (2 vCPU, 4 GB), applied to each of its four components. See Kubernetes concepts.

At creation, no size is preselected: choose one. A resource created with a former size (small, medium…) keeps it and can still be edited.

Each wizard shows the impact on the project quota and the estimated cost before creation.

8. How do I increase a project's quotas?​

Project or organization administrators change the quotas in the project settings. A quota cannot be lowered below current consumption. If your organization's capacity is insufficient, contact support.

See: Key concepts - Quotas

9. How do I scale my resources?​

  • Kubernetes cluster: change the minimum and maximum bounds of the node groups in Edit. Nodes adjust automatically to the load between these bounds. See Manage node groups.
  • Databases: depending on the service, the preset and the storage can be changed in Edit. The disk size cannot be reduced and the version cannot be downgraded; changing the version or the preset restarts the instances. See the "scaling" guide of each service.

10. How does database high availability work?​

With several replicas, each managed service automatically fails over to a healthy replica if the primary instance fails. The number of replicas is chosen at creation.

See: PostgreSQL - Concepts, Redis - Concepts

11. Are database backups available in the console?​

Yes. PostgreSQL and MariaDB databases, as well as virtual machines and disks, are backed up and restored from the console, in the Infrastructure > Backups menu and the Backups tab of each resource. See Backups.

12. How do I contact support?​

From the console, open the profile menu and click Contact support: the technical context of the page is attached to your request. You can also write to support@hidora.io.