You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/main/asciidoc/deploying-to-openshift.adoc
+2-11Lines changed: 2 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The following table outlines the build strategies that {project-name} supports:
58
58
== Bootstrapping the project
59
59
60
60
First, you need a new project that contains the OpenShift extension.
61
-
Then, before you build and deploy our application, you must log into an OpenShift cluster.
61
+
Then, before you build and deploy your application, you must log into an OpenShift cluster.
62
62
63
63
=== Adding the OpenShift extension
64
64
@@ -67,15 +67,6 @@ To build and deploy your applications as a container image that runs inside your
67
67
This extension also generates {openshift} resources such as image streams, build configuration, deployment, and service definitions.
68
68
If your application includes the `quarkus-smallrye-health` extension, {openshift} can access the health endpoint and verify the startup, liveness, and readiness of your application.
69
69
70
-
[IMPORTANT]
71
-
====
72
-
From {project-name} 3.8, the `DeploymentConfig` object, deprecated in OpenShift, is also deprecated in {project-name}.
73
-
`Deployment` is the default and preferred deployment kind for the `quarkus-openshift` extension.
74
-
If you redeploy applications that you deployed before by using `DeploymentConfig`, by default, those applications use `Deployment` but do not remove the previous `DeploymentConfig`.
75
-
This leads to a deployment of both new and old applications, so, you must remove the old `DeploymentConfig` manually.
76
-
However, if you want to continue to use `DeploymentConfig`, it is still possible to do so by explicitly setting `quarkus.openshift.deployment-kind` to `DeploymentConfig`.
77
-
====
78
-
79
70
.Prerequisites
80
71
81
72
* You have a Quarkus Maven project.
@@ -104,7 +95,7 @@ However, if you want to continue to use `DeploymentConfig`, it is still possible
0 commit comments