-
Updated
Apr 30, 2020
hetzner-cloud
Here are 78 public repositories matching this topic...
Not sure if this is the right place for this bug report, because I think this is actually a missing feature in the API, but I can't find a repository for that.
With hcloud server list --output json, I can get a list of my servers in JSON format. This'll provide the server type's disk size as .server_type.disk:
martin@martin ~ % cat
-
Updated
May 13, 2020
-
Updated
May 12, 2020 - Go
-
Updated
May 19, 2020 - Go
-
Updated
Apr 30, 2020 - JavaScript
Hi,
I can successfully associate servers with networks.
resource "hcloud_network" "ens10" {
name = "ens10"
ip_range = "10.0.0.0/16"
}
resource "hcloud_network_subnet" "ens10" {
type = "server"
network_zone = "eu-central"
ip_range = "10.0.0.0/24"
network_id = hcloud_network.ens10.id
}
resource "hcloud_server" "node-0" {
name = "node-0"
server_type = "cpx
-
Updated
May 20, 2020
-
Updated
Apr 30, 2020 - Python
-
Updated
May 12, 2020 - Go
Is there documentation explaining architecture and how to write new drivers.
Would love to contribute however need to have more information instead of just guessing from the existing code.
-
Updated
May 17, 2019 - Go
-
Updated
Apr 23, 2018 - PHP
-
Updated
Mar 7, 2018 - Shell
-
Updated
Mar 30, 2019 - Dockerfile
-
Updated
Apr 19, 2020
-
Updated
May 26, 2018 - HCL
-
Updated
Jun 20, 2018 - Shell
-
Updated
Feb 20, 2019 - HCL
-
Updated
Apr 5, 2020
-
Updated
Apr 5, 2020
-
Updated
May 9, 2020
-
Updated
Mar 30, 2018 - PowerShell
-
Updated
Apr 20, 2020 - Go
Improve this page
Add a description, image, and links to the hetzner-cloud topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the hetzner-cloud topic, visit your repo's landing page and select "manage topics."
The OpenEBS addon requires iSCSI to be running on the worker nodes: https://docs.openebs.io/docs/next/prerequisites.html
I already created my cluster. How can I now make sure, that all my worked nodes have this service installed and running? And how do you make sure, that your packages on the worker nodes are up-to-date (basically regularly running
apt-get upgrade)?