Skip to content

Commit fa736a4

Browse files
svoribuziuk
andauthored
Update _posts/2025-09-09-running-open-vsx-on-premises.adoc
Co-authored-by: Ilya Buziuk <[email protected]>
1 parent 1ff90d3 commit fa736a4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2025-09-09-running-open-vsx-on-premises.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ But in enterprise environments, relying on the public link:https://open-vsx.org[
1616
air-gapped environments, compliance rules, or simply the need for a curated list of approved tools.
1717

1818
That’s where running **Open VSX On-Premises** comes in.
19-
In this post, we’ll explore how {prod} makes it easy to deploy and configure your own extension registry, using nothing more than an {prod} workspace.
19+
In this post, we’ll explore how {prod} makes it easy to deploy and configure your own extension registry, using nothing more than an {prod} Cloud Development Environment running on the OpenShift cluster.
2020

2121
WARNING: ⚠️ This flow is supported only on **OpenShift clusters where {prod} is deployed**. It will not work on plain Kubernetes.
2222

0 commit comments

Comments
 (0)