This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion-ballista.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 4eff45a5b Publish built docs triggered by
b8c44a2fc26b60923f9b6317bab50644b7f8df88
4eff45a5b is described below
commit 4eff45a5b07d76e22ec1b6eb57edd0bb4ee70033
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Aug 6 23:58:53 2026 +0000
Publish built docs triggered by b8c44a2fc26b60923f9b6317bab50644b7f8df88
---
_sources/user-guide/deployment/kubernetes.md.txt | 24 ++++++++++++++++++++++
searchindex.js | 2 +-
user-guide/deployment/kubernetes.html | 26 +++++++++++++++++++++++-
3 files changed, 50 insertions(+), 2 deletions(-)
diff --git a/_sources/user-guide/deployment/kubernetes.md.txt
b/_sources/user-guide/deployment/kubernetes.md.txt
index 9e936abba..721f7705c 100644
--- a/_sources/user-guide/deployment/kubernetes.md.txt
+++ b/_sources/user-guide/deployment/kubernetes.md.txt
@@ -107,6 +107,30 @@ persistentvolumeclaim/data-pv-claim created
Copy the following yaml to a `cluster.yaml` file and change `<your-image>`
with the name of your Ballista Docker image.
```yaml
+# Two Services front the same scheduler pod:
+# - `ballista-scheduler-registration` sets `publishNotReadyAddresses: true`
+# so executors can dial the scheduler for registration BEFORE its
+# /readyz gate flips green. Without this, the scheduler's /readyz
+# defaults to blocking on 1+ registered executor, which keeps its
+# Endpoints empty — executors can't reach it to register in the first
+# place. Chicken-and-egg; cluster never converges.
+# - `ballista-scheduler` is the client-facing Service (respects /readyz)
+# so clients don't submit queries to a scheduler with 0 executors mid
+# rolling upgrade.
+apiVersion: v1
+kind: Service
+metadata:
+ name: ballista-scheduler-registration
+ labels:
+ app: ballista-scheduler
+spec:
+ publishNotReadyAddresses: true
+ ports:
+ - port: 50050
+ name: scheduler
+ selector:
+ app: ballista-scheduler
+---
apiVersion: v1
kind: Service
metadata:
diff --git a/searchindex.js b/searchindex.js
index 315e2d87b..935959349 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"API changes":[[29,"api-changes"]],"AQE join
behavior (opt-in)":[[28,"aqe-join-behavior-opt-in"]],"Adaptive Query Execution
(AQE)":[[22,"adaptive-query-execution-aqe"]],"Adaptive Query Execution
(Experimental)":[[51,"adaptive-query-execution-experimental"]],"Adding a
persona":[[26,"adding-a-persona"]],"Aggregate
Functions":[[50,"aggregate-functions"]],"Apache DataFusion
Ballista":[[27,null]],"Apache DataFusion Ballista 0.10.0
Changelog":[[0,null]],"Apache Da [...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"API changes":[[29,"api-changes"]],"AQE join
behavior (opt-in)":[[28,"aqe-join-behavior-opt-in"]],"Adaptive Query Execution
(AQE)":[[22,"adaptive-query-execution-aqe"]],"Adaptive Query Execution
(Experimental)":[[51,"adaptive-query-execution-experimental"]],"Adding a
persona":[[26,"adding-a-persona"]],"Aggregate
Functions":[[50,"aggregate-functions"]],"Apache DataFusion
Ballista":[[27,null]],"Apache DataFusion Ballista 0.10.0
Changelog":[[0,null]],"Apache Da [...]
\ No newline at end of file
diff --git a/user-guide/deployment/kubernetes.html
b/user-guide/deployment/kubernetes.html
index 74790586b..3a1d14cbb 100644
--- a/user-guide/deployment/kubernetes.html
+++ b/user-guide/deployment/kubernetes.html
@@ -472,7 +472,31 @@ persistentvolumeclaim/data-pv-claim<span class="w">
</span>created
<section id="deploying-a-ballista-cluster">
<h2>Deploying a Ballista Cluster<a class="headerlink"
href="#deploying-a-ballista-cluster" title="Link to this heading">#</a></h2>
<p>Copy the following yaml to a <code class="docutils literal
notranslate"><span class="pre">cluster.yaml</span></code> file and change <code
class="docutils literal notranslate"><span
class="pre"><your-image></span></code> with the name of your Ballista
Docker image.</p>
-<div class="highlight-yaml notranslate"><div
class="highlight"><pre><span></span><span class="nt">apiVersion</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">v1</span>
+<div class="highlight-yaml notranslate"><div
class="highlight"><pre><span></span><span class="c1"># Two Services front the
same scheduler pod:</span>
+<span class="c1"># - `ballista-scheduler-registration` sets
`publishNotReadyAddresses: true`</span>
+<span class="c1"># so executors can dial the scheduler for registration
BEFORE its</span>
+<span class="c1"># /readyz gate flips green. Without this, the
scheduler's /readyz</span>
+<span class="c1"># defaults to blocking on 1+ registered executor, which
keeps its</span>
+<span class="c1"># Endpoints empty — executors can't reach it to
register in the first</span>
+<span class="c1"># place. Chicken-and-egg; cluster never converges.</span>
+<span class="c1"># - `ballista-scheduler` is the client-facing Service
(respects /readyz)</span>
+<span class="c1"># so clients don't submit queries to a scheduler with
0 executors mid</span>
+<span class="c1"># rolling upgrade.</span>
+<span class="nt">apiVersion</span><span class="p">:</span><span class="w">
</span><span class="l l-Scalar l-Scalar-Plain">v1</span>
+<span class="nt">kind</span><span class="p">:</span><span class="w">
</span><span class="l l-Scalar l-Scalar-Plain">Service</span>
+<span class="nt">metadata</span><span class="p">:</span>
+<span class="w"> </span><span class="nt">name</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">ballista-scheduler-registration</span>
+<span class="w"> </span><span class="nt">labels</span><span class="p">:</span>
+<span class="w"> </span><span class="nt">app</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">ballista-scheduler</span>
+<span class="nt">spec</span><span class="p">:</span>
+<span class="w"> </span><span class="nt">publishNotReadyAddresses</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">true</span>
+<span class="w"> </span><span class="nt">ports</span><span class="p">:</span>
+<span class="w"> </span><span class="p p-Indicator">-</span><span
class="w"> </span><span class="nt">port</span><span class="p">:</span><span
class="w"> </span><span class="l l-Scalar l-Scalar-Plain">50050</span>
+<span class="w"> </span><span class="nt">name</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">scheduler</span>
+<span class="w"> </span><span class="nt">selector</span><span
class="p">:</span>
+<span class="w"> </span><span class="nt">app</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">ballista-scheduler</span>
+<span class="nn">---</span>
+<span class="nt">apiVersion</span><span class="p">:</span><span class="w">
</span><span class="l l-Scalar l-Scalar-Plain">v1</span>
<span class="nt">kind</span><span class="p">:</span><span class="w">
</span><span class="l l-Scalar l-Scalar-Plain">Service</span>
<span class="nt">metadata</span><span class="p">:</span>
<span class="w"> </span><span class="nt">name</span><span
class="p">:</span><span class="w"> </span><span class="l l-Scalar
l-Scalar-Plain">ballista-scheduler</span>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
