Skip to content

Commit

Permalink
QDOCS-1083: minor edits, fix attributes
Browse files Browse the repository at this point in the history
Signed-off-by: shjones <[email protected]>
  • Loading branch information
sheilamjones committed Feb 6, 2025
1 parent 748789b commit 66970a6
Showing 1 changed file with 7 additions and 13 deletions.
20 changes: 7 additions & 13 deletions docs/src/main/asciidoc/deploying-to-openshift-native-howto.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -13,20 +13,19 @@ include::_attributes.adoc[]
:topics: devops,kubernetes,openshift,cloud,deployment
:extensions: io.quarkus:quarkus-openshift

You can deploy your native {project-name} applications to {openShift} compiled to native executables by using the Docker build strategy.
You can deploy your native {project-name} applications to {openshift} compiled to native executables by using the Docker build strategy.

You must create a native executable for your application that targets the Linux AMD64 operating system.
If your host operating system is different from this, create a native Linux executable using a container runtime, for example, Docker or Podman.
If your host operating system is different from this, create a native Linux executable by using a container runtime, for example, Docker or Podman.

Your project includes pregenerated Dockerfiles with instructions.
Your Quarkus project includes pregenerated Dockerfiles with instructions.
To use a custom Dockerfile, add the file in the `src/main/docker` directory or anywhere inside the module, and set the path to your Dockerfile by using the `quarkus.openshift.native-dockerfile` property.

== Prerequisites

* You have a Linux AMD64 system or an Open Container Initiative (OCI) compatible container runtime, such as Podman or Docker.
* You have a Quarkus project that includes the `quarkus-openshift` extension.
* You are working in the correct OpenShift project namespace, as outlined in Switching to the required {openshift} project.
// xref:proc_verifying-the-openshift-project-namespace_quarkus-openshift[Switching to the required {RHOSSHORT} project].
* You have a Quarkus Maven project that includes the `quarkus-openshift` extension.
* You are working in the correct OpenShift project namespace.

== Procedure

Expand All @@ -49,7 +48,7 @@ quarkus.native.container-build=true
----
quarkus.kubernetes-client.trust-certs=true
----
.. Expose the service to create an {RHOSSHORT} route:
.. Expose the service to create an {openshift} route:
+
[source,properties]
----
Expand Down Expand Up @@ -81,7 +80,6 @@ quarkus.native.container-runtime=podman
quarkus.native.container-runtime=docker
----


. Finally, build a native executable, package, and deploy your application to {openshift}:
+
[source,shell,subs="attributes+,+quotes"]
Expand All @@ -92,7 +90,7 @@ quarkus.native.container-runtime=docker
== Verification

. Verify that an image stream and a service resource is created and the application is deployed by using the OpenShift web console.
Alternatively, you can run the following {openShift} command-line interface (CLI) commands:
Alternatively, you can run the following {openshift} command-line interface (CLI) commands:
+
[source,shell,subs="attributes+,+quotes"]
----
Expand All @@ -112,7 +110,3 @@ oc get svc <3>
oc logs -f __<pod_name>__
----

[[additional-resources]]
== Additional resources
//* link:https://docs.openshift.com/container-platform/{RHOSVersion}/openshift_images/image-streams-manage.html[Managing image streams]

0 comments on commit 66970a6

Please sign in to comment.