FAQ
GitLab
Do I have SSH access to my GitLab?
No, SSH access to the GitLab instance is not possible for technical reasons!
Is my GitLab instance dedicated?
Yes, each customer has a dedicated GitLab instance.
What does Shared vCPU mean?
Multiple containers with dedicated GitLab instances run on a single host system.
The vCPUs are shared between them via virtualization.
We ensure that there are always enough resources available and that no excessive load occurs.
Is the RAM shared?
No, each instance is exclusively allocated the specified amount of RAM.
Is administrative access restricted?
You have full administrative access to the GitLab instance via the web interface.
However, access to the operating system is not possible.
Can I use Git LFS?
This is disabled by default, but we can enable this feature upon request.
Do I need a GitLab EE license?
The GitLab EE packages do NOT include a license.
This can be purchased directly from NETWAYS. Of course, a license acquired elsewhere can also be applied.
GitLab Runner
Are the runners shared?
No, for all runners, the vCPU, RAM, and disk resources are exclusive.
What are Custom Runner Flavors?
Starting from the Advanced and Premium packages, it is possible to book additional resources for the runner(s) via our support team.
Is the runner cache automatically cleared?
The local runner cache is not automatically cleared. Otherwise, it could happen that required fragments are lost.
Which operating system do the runners use?
Fedora CoreOS
Can I use my own runners?
You can connect your own runners. There are no restrictions whatsoever for your own runners.
The runners only need to be able to establish a connection to the GitLab instance from your network.
Further Technical Information
Are there additional costs for data transfer?
Data transfer is included in the price.