USHIFT-5477: Split MicroShift Image Mode docs into user and contributor parts

[ggiguash]

The following procedures were moved to the user-only part:

• Build MicroShift Bootc Image
• Run MicroShift Bootc Virtual Machine
• Using Bootc Image Builder (BIB)
• Appendix A: Embedding Container Images in Bootc Builds

The following procedures remain in the contributor-only part:

• Run MicroShift Bootc Image using podman
• Appendix A: Multi-Architecture Image Build
• Appendix B: The rpm-ostree to Image Mode Upgrade Procedure

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-5477 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

The following procedures remain in the contributor-only part:

• Run MicroShift Bootc Image using podman
• The rpm-ostree to Image Mode Upgrade Procedure

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[ggiguash]

/assign @DanielFroehlich

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-5477 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

The following procedures were moved to the user-only part:

• Build MicroShift Bootc Image
• Run MicroShift Bootc Virtual Machine
• Using Bootc Image Builder (BIB)
• Appendix A: Embedding Container Images in Bootc Builds
• Appendix B: The rpm-ostree to Image Mode Upgrade Procedure

The following procedures remain in the contributor-only part:

• Run MicroShift Bootc Image using podman
• Appendix A: The rpm-ostree to Image Mode Upgrade Procedure

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-5477 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

The following procedures were moved to the user-only part:

• Build MicroShift Bootc Image
• Run MicroShift Bootc Virtual Machine
• Using Bootc Image Builder (BIB)
• Appendix A: Embedding Container Images in Bootc Builds

The following procedures remain in the contributor-only part:

• Run MicroShift Bootc Image using podman
• Appendix A: Multi-Architecture Image Build
• Appendix B: The rpm-ostree to Image Mode Upgrade Procedure

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[DanielFroehlich]

Good stuff! I do have some suggestions.

[DanielFroehlich]

The primary reason of building an ISO is that I can simply put it onto an USB stick and boot my edge device from it.
For that to success, the kickstart needs also be embedded into the ISO, not injected using the hypervisor.
It would be nice if bib would be able to do this directly , but it looks like it cant, should we create an RFE?
The procedure to embedd the kickstart into the ISO is non-trivial, if this doc is correct:
https://access.redhat.com/solutions/60959

So about we change this to:

Suggested change

	### Create Virtual Machine
	### Option A: Embed the kickstart file into the ISO
	To be able to boot e.g. a physical edge device from the ISO, the kickstart file needs to be embedded into the ISO image. Follow the instructions provided [here](https://access.redhat.com/solutions/60959) to do so.
	Then you can put the ISO image onto an USB using a disk imager tool of your choice (see e.g. [here](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/interactively_installing_rhel_from_installation_media/assembly_creating-a-bootable-installation-medium_rhel-installer)) and boot the edge device from it.
	### Option B: Create Virtual Machine from the ISO
	When testing using a virtual machine, the kickstart file can be injected at vm creation time using the following steps.

[ggiguash]

I will simplify this to always include kickstart in ISO. That's easy with BIB.

[ggiguash]

Embedding will complicate things a bit because it's not a command line option and we'll have to create a configuration file.
I changed the order of chapters:

• Kickstart file creation is coming before ISO image creation now
• Kickstart file creation contains this reference to how embed kickstart into ISO

Would it be acceptable for this doc?

[openshift-ci]

@ggiguash: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[pmtk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ggiguash,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment