Docs: Create procedure for Deploying on OpenShift using Docker build strategy

[sheilamjones]

This PR aims to draft a procedure for the following use case

• Build and deploy Quarkus applications on OpenShift using the docker build strategy.

Reference: Based on the Red Hat build of Quarkus guide Deploying on OpenShift Container Platform

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[github-actions]

🎊 PR Preview 7ff0fcf has been successfully built and deployed to https://quarkus-pr-main-45918-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[sheilamjones]

Hi @iocanel,
Can I please get your review of this procedure. Again, this content is based on the existing downstream Deploying on Openshift guide.
Many thanks,
Sheila

[rolfedh]

I changed some items to bullet points to better reflect that they are a collection of independent options rather than a sequence of steps. Additionally, to make it clearer that these options are optional, I replaced the imperative verb form with the infinitive "To ..." form. Feel free to apply this approach to any other PRs that include similar lists of optional steps.

[rolfedh]

Hi Sheila,

Great work! With your agreement, I’ve taken the opportunity to provide a more thorough review. I hope you find it helpful. Feel free to apply or disregard any suggestions as you see fit.
Thanks!

[rolfedh]

Suggested change

	. To retrieve the log output for your application's pod, use the `oc logs -f` command with the `<pod_name>` value of the pod you are interested in.
	In this example, we use the `openshift-helloworld-1-gzzrx` pod name that corresponds with the latest pod prefixed with the name of your application:
	. To get the log output for your application's pod, use the `oc logs -f` command with its name. For example:

[rolfedh]

Suggested change

	[source,shell,subs=attributes+]
	.Example output
	[source,shell,subs=attributes+]

[rolfedh]

I'm unsure whether we want to label outputs, but if we do, we should aim to apply it consistently across all upstream-downstream documentation. Something to think about for the future.

[sheilamjones]

Good point and +1. I think it looks better to have the label, but for consistency reasons, I might leave this as it is for now and look to deciding whether or not to apply it in the future across the other guides.

[rolfedh]

I'd double-check with the SME correctness of the current statement. Is the route is listening on port 80 in addition to port 8080? If so, maybe:

Suggested change

	Be aware that the route is now listening on port 80 and no longer at port 8080.
	Be aware that the route is now listening on port 80.

[sheilamjones]

@iocanel, perhaps you could advise here?

[iocanel]

Maybe add a quick explanation on what the docker build strategy is.

I think that we need to let them know that its actually a docker build taking place inside openshift using the artifact that was build locally. In other words a more customizable version of the binary build that is the default option.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 97bc55a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.