Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

📖 update hetzner-baremetal guide #1182

Merged
merged 1 commit into from
Apr 9, 2024
Merged

📖 update hetzner-baremetal guide #1182

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/reference/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,6 @@

In this object reference, we introduce all objects that are specific for this provider integration. The naming of objects, servers, machines, etc. can be confusing. Without claiming to be consistent throughout these docs, we would like to give an overview of how we name things here.

First, there are some important counterparts of our objects and CAPI objects. ```HetznerCluster``` has CAPI's ```Cluster``` object. CAPI's ```Machine``` object is the counterpart of both ```HCloudMachine``` and ```HetznerBareMetalMachine```. These two are objects of the provider integration that are reconciled by the ```HCloudMachineController``` and the ```HetznerBareMetalMachineController``` respectively. The ```HCloudMachineController``` checks whether there is a server in the HCloud API already and if not, buys/creates one that corresponds to a ```HCloudMachine``` object. The ```HetznerBareMetalMachineController``` does not buy new bare metal machines, but instead consumes a host of the inventory of ```HetznerBareMetalHosts```, which have a one-to-one relationship to Hetzner dedicated/root/bare metal servers that have been bought manually by the user.
First, there are some important counterparts of our objects and CAPI objects. `HetznerCluster` has CAPI's `Cluster` object. CAPI's `Machine` object is the counterpart of both `HCloudMachine` and `HetznerBareMetalMachine`. These two are objects of the provider integration that are reconciled by the `HCloudMachineController` and the `HetznerBareMetalMachineController` respectively. The `HCloudMachineController` checks whether there is a server in the HCloud API already and if not, buys/creates one that corresponds to a `HCloudMachine` object. The `HetznerBareMetalMachineController` does not buy new bare metal machines, but instead consumes a host of the inventory of `HetznerBareMetalHosts`, which have a one-to-one relationship to Hetzner dedicated/root/bare metal servers that have been bought manually by the user.

Therefore, there is an important difference between the ```HCloudMachine``` object and a server in the HCloud API. For bare metal, we have even three terms: the ```HetznerBareMetalMachine``` object, the ```HetznerBareMetalHost``` object, and the actual bare metal server that can be accessed through Hetzner's robot API.
Therefore, there is an important difference between the `HCloudMachine` object and a server in the HCloud API. For bare metal, we have even three terms: the `HetznerBareMetalMachine` object, the `HetznerBareMetalHost` object, and the actual bare metal server that can be accessed through Hetzner's robot API.
Loading
Loading