This is an automated email from the ASF dual-hosted git repository.

zakelly pushed a commit to branch release-1.19
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.19 by this push:
     new 0cb0ba3808f [hotfix] Fix the broken link of standalone deployment
0cb0ba3808f is described below

commit 0cb0ba3808faaddfbc7ed6d34f1d608af8d6a35f
Author: Zakelly <zakelly....@gmail.com>
AuthorDate: Mon Jul 8 11:46:25 2024 +0800

    [hotfix] Fix the broken link of standalone deployment
---
 docs/content.zh/docs/deployment/overview.md | 2 +-
 docs/content/docs/deployment/overview.md    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content.zh/docs/deployment/overview.md 
b/docs/content.zh/docs/deployment/overview.md
index 58d0ac93902..9be46a0b601 100644
--- a/docs/content.zh/docs/deployment/overview.md
+++ b/docs/content.zh/docs/deployment/overview.md
@@ -80,7 +80,7 @@ When deploying Flink, there are often multiple options 
available for each buildi
             </td>
             <td>
                 <ul id="jmimpls">
-                    <li><a href="{{< ref 
"docs/deployment/resource-providers/standalone/" >}}">Standalone</a> (this is 
the barebone mode that requires just JVMs to be launched. Deployment with <a 
href="{{< ref "docs/deployment/resource-providers/standalone/docker" 
>}}">Docker, Docker Swarm / Compose</a>, <a href="{{< ref 
"docs/deployment/resource-providers/standalone/kubernetes" >}}">non-native 
Kubernetes</a> and other models is possible through manual setup in this mode)
+                    <li><a href="{{< ref 
"docs/deployment/resource-providers/standalone/overview" >}}">Standalone</a> 
(this is the barebone mode that requires just JVMs to be launched. Deployment 
with <a href="{{< ref "docs/deployment/resource-providers/standalone/docker" 
>}}">Docker, Docker Swarm / Compose</a>, <a href="{{< ref 
"docs/deployment/resource-providers/standalone/kubernetes" >}}">non-native 
Kubernetes</a> and other models is possible through manual setup in this mode)
                     </li>
                     <li><a href="{{< ref 
"docs/deployment/resource-providers/native_kubernetes" >}}">Kubernetes</a></li>
                     <li><a href="{{< ref 
"docs/deployment/resource-providers/yarn" >}}">YARN</a></li>
diff --git a/docs/content/docs/deployment/overview.md 
b/docs/content/docs/deployment/overview.md
index 939f7c12828..f87264d0b00 100644
--- a/docs/content/docs/deployment/overview.md
+++ b/docs/content/docs/deployment/overview.md
@@ -80,7 +80,7 @@ When deploying Flink, there are often multiple options 
available for each buildi
             </td>
             <td>
                 <ul id="jmimpls">
-                    <li><a href="{{< ref 
"docs/deployment/resource-providers/standalone/" >}}">Standalone</a> (this is 
the barebone mode that requires just JVMs to be launched. Deployment with <a 
href="{{< ref "docs/deployment/resource-providers/standalone/docker" 
>}}">Docker, Docker Swarm / Compose</a>, <a href="{{< ref 
"docs/deployment/resource-providers/standalone/kubernetes" >}}">non-native 
Kubernetes</a> and other models is possible through manual setup in this mode)
+                    <li><a href="{{< ref 
"docs/deployment/resource-providers/standalone/overview" >}}">Standalone</a> 
(this is the barebone mode that requires just JVMs to be launched. Deployment 
with <a href="{{< ref "docs/deployment/resource-providers/standalone/docker" 
>}}">Docker, Docker Swarm / Compose</a>, <a href="{{< ref 
"docs/deployment/resource-providers/standalone/kubernetes" >}}">non-native 
Kubernetes</a> and other models is possible through manual setup in this mode)
                     </li>
                     <li><a href="{{< ref 
"docs/deployment/resource-providers/native_kubernetes" >}}">Kubernetes</a></li>
                     <li><a href="{{< ref 
"docs/deployment/resource-providers/yarn" >}}">YARN</a></li>

Reply via email to