-
Spike
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
Currently, the osImageURL field on MachineConfigs allows one to override the base OS image in favor of a custom OS image for a given MachineConfigPool. This conflicts with on-cluster builds and BuildController because BuildController currently uses the machine-config-osimageurl ConfigMap as its source of truth for the base OS image and extensions container.
It may be desirable to allow a cluster admin to instead consume the osImageURL for the base image. The extensions image in this case is TBD. We may need to omit that particular path for osImageURL overrides and potentially custom Dockerfiles as well.
Done When:
- It is determined if BuildController should consider the osImageURL.
- It is determined what effect that could have on the Dockerfile that BuildController generates (i.e., interactions with the extensions image).
- It is determined how that would impact the custom Dockerfile capability that BuildController has.