Conversation
|
|
||
| ### Data Source | ||
|
|
||
| The top-level keys are populated based on the annotations and labels of the |
There was a problem hiding this comment.
Is there any specific reason for including both labels and annotations? Could we use only either of them, to avoid extra logic to prevent duplicated entries?
There was a problem hiding this comment.
You will probably have labels for being able to include things like topology information, but on the other hand you also have data that does not fit the restricted format of labels und thus have to go into an annotation (e.g. IPv6 addresses).
| included in the field `server-name`. Specifying an annotation or label with | ||
| that key overwrites it with the given value. | ||
|
|
||
| For data that is common among all servers the operator can define static |
There was a problem hiding this comment.
Could we simplify this statement, with an example, maybe I couldn't understand it.
There was a problem hiding this comment.
An example would be the region or zone, which is the same of all servers inside a cluster.
|
|
||
| ### Metaldata API | ||
|
|
||
| To retrieve data from a local metadata server, clients rely on DNS to resolve to |
There was a problem hiding this comment.
It should also support hard-coded reserved IP to avoid dependency on functional DNS imo.
There was a problem hiding this comment.
Magic IPs are rather something for virtualized environments in which you can have SDN mangle the request. But in our bare-metal hardware setup we have to work with a real network which makes DNS the natural choice. In the end, you can also specify the IP address, it's up to the client how to discover the address of the server.
|
|
||
| ### Metal-API Changes | ||
|
|
||
| As outlined earlier we will have to add support for a user-data secret to the |
There was a problem hiding this comment.
We might want to quickly think, if there are any potential overlaps with the ongoing efforts related to ServerMetadata.
Ref: https://github.com/ironcore-dev/metal-operator/pull/762/changes
There was a problem hiding this comment.
There are some touch-points but these two efforts are mostly separate. Metaldata consumes that information but supplying user-data is a separate concern which should be a property of the claim.
|
|
||
| ### Non-Goals | ||
|
|
||
| `¯\_(ツ)_/¯` |
3 participants
No description provided.