This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/zeppelin-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 7b32bae44 Automatic Site Publish by Buildbot
7b32bae44 is described below
commit 7b32bae44b08341149248bf74a1b2ea497c040d9
Author: buildbot <[email protected]>
AuthorDate: Tue Nov 11 16:24:12 2025 +0000
Automatic Site Publish by Buildbot
---
output/atom.xml | 2 +-
output/rss.xml | 4 ++--
output/security.html | 9 +++++++++
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/output/atom.xml b/output/atom.xml
index 6c83b5055..d30595db8 100644
--- a/output/atom.xml
+++ b/output/atom.xml
@@ -4,7 +4,7 @@
<title>Apache Zeppelin</title>
<link href="http://zeppelin.apache.org/"; rel="self"/>
<link href="http://zeppelin.apache.org"/>
- <updated>2025-08-22T02:18:04+00:00</updated>
+ <updated>2025-11-11T16:24:03+00:00</updated>
<id>http://zeppelin.apache.org</id>
<author>
<name>The Apache Software Foundation</name>
diff --git a/output/rss.xml b/output/rss.xml
index e2ea7a30b..6e3f873c4 100644
--- a/output/rss.xml
+++ b/output/rss.xml
@@ -5,8 +5,8 @@
<description>Apache Zeppelin - The Apache Software
Foundation</description>
<link>http://zeppelin.apache.org</link>
<link>http://zeppelin.apache.org</link>
- <lastBuildDate>2025-08-22T02:18:04+00:00</lastBuildDate>
- <pubDate>2025-08-22T02:18:04+00:00</pubDate>
+ <lastBuildDate>2025-11-11T16:24:03+00:00</lastBuildDate>
+ <pubDate>2025-11-11T16:24:03+00:00</pubDate>
<ttl>1800</ttl>
diff --git a/output/security.html b/output/security.html
index 12e367418..4a5e57b87 100644
--- a/output/security.html
+++ b/output/security.html
@@ -201,6 +201,15 @@ Also, the Spark interpreter is auto configured to use
Spark on Kubernetes in cli
This isolation can provide an operational benefit on large deployments, but is
not intended as a security boundary:
access to your Zeppelin instances should be restricted regardless of how they
are deployed.</p>
+<h3>Deployment</h3>
+
+<p>If you want to allow access to a Zeppelin server across a network, you
should
+consider what files and other OS and network resources that the OS user used
to run
+the server has access to. Zeppelin users will be able to access these.
+Using a Docker container or equivalent might be one way to limit what is
accessible.
+Alternatively, you could look at setting the permissions for the OS user used
for
+running the Zeppelin server process.</p>
+
<h2>JavaScript code execution in the browser</h2>
<p>Zeppelin allows notes to produce rich output, including HTML and even
