-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
DO380 - RHOCP4.14-en-3-20250418
-
None
-
False
-
-
False
-
-
-
en-US (English)
Please fill in the following information:
URL: | https://rol.redhat.com/rol/app/courses/do380-4.14/pages/ch03s04 |
Reporter RHNID: | ssanyal@redhat.com |
Section Title: | Guided Exercise: Node Configuration with the Machine Configuration Operator |
Issue description
Hello,
I am currently enrolled in the DO380 (v4.14) course and exploring the Machine Configuration (MachineConfig) section. While working through Chapter 3.4.4, the course guides us to create a custom MachineConfig (99-zcustom-chrony) that uses the data: URL format in the spec.config.storage.files.contents.source field.
In Chapter 3.3, the course specifically encourages learners to use the oc explain command to explore configuration options. When I ran:
oc explain mc.spec.config.storage.files.contents
It shows the following supported URL schemes: http, https, tftp, s3, and data.
I attempted to use an https: URL instead of data:, but encountered a parsing error. The MachineConfig renderer seemed to expect a data: prefix only, and none of the other schemes (even https worked despite being listed as supported. I tried various formats and combinations, but without success.
I also searched OpenShift documentation and external resources, but couldn't find a single working example that uses these alternative URL schemes (http, https, tftp, s3) in the MachineConfig's contents.source.
This seems contradictory, as the course suggests that multiple schemes are supported, and encourages exploring those options using oc explain.
Request:
Can you confirm whether http, https, tftp, and s3 URL schemes are actually supported in OpenShift 4.14 for use in contents.source?
If supported, could you please provide a valid working example for one of these URL types?
If there are additional conditions or configurations required for these schemes to work, please clarify that as well.
Reference:
Course: DO380 v4.14
Chapter: 3.4.4 (custom chronyd MachineConfig)
Additional Mention: Chapter 3.3 (suggests using oc explain)
Steps to reproduce:
Workaround:
Expected result: