coreos
metadata: pick up OKD details from filesystem
OKD just started to use FCOS for its nodes OS.
It would be helpful to agree with OKD developers so that they start exposing some machine-friendly details on the FS. Pinger would then pick them up and report back. This is useful for filtering when aggregating data.
Some useful bits would:
- is this an OKD node? (via Ignition)
- which OKD aleph-version was this node born on? (via Ignition)
- additional details relevant for OKD stats
And by saying via Ignition, are we reading from the log by journalctl --identifier=ignition --all or /run/ignition.json?
Oh sorry, that was indeed a bit too terse.
It means that OKD installer should be writing those files to disk via Ignition on first-boot. The rationale is to loose the coupling/ordering between pinger and the rest of OKD bootstrap.