In `oc adm release new` only two components are allowed to be specified:

• kubernetes
• machine-os

These are being extracted from operator labels and displayed on release controller release page. RHCOS version is set in machine-os and links to release browser, which works great for OCP.

However, for OKD we base our machine-os version on FCOS. After layering has been implemented we specify the base FCOS version in machine-os. OKD is also installing cri-o - and its version is not getting recorded. In some cases OKD machine-os also overrides kernel version (some versions may break e2e tests), so it would be useful to allow `oc` to set cri-o and kernel version labels and have them displayed on release controller