Skip to content

Procedures/managed openvsx registry - #3170

Open
svor wants to merge 14 commits into
mainfrom
procedures/managed-openvsx-registry
Open

Procedures/managed openvsx registry#3170
svor wants to merge 14 commits into
mainfrom
procedures/managed-openvsx-registry

Conversation

@svor

@svor svor commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

What does this pull request change?

Provides documentation how to enable OpenVSX as a operand

What issues does this pull request fix or reference?

https://redhat.atlassian.net/browse/CRW-11147

Specify the version of the product this pull request applies to

7.121.0

Pull Request checklist

The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.

  • Any procedure:
    • Successfully tested.
  • Any page or link rename:
    • The page contains a redirection for the previous URL.
    • Propagate the URL change in:
  • Builds on Eclipse Che hosted by Red Hat.
  • the Validate language on files added or modified step reports no vale warnings.

svor and others added 4 commits July 10, 2026 16:40
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
@svor
svor requested review from a team, deerskindoll, gtrivedi88 and mkuznyetsov as code owners July 23, 2026 15:35
@svor
svor requested a review from ibuziuk July 23, 2026 15:35
@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown

🎊 Navigate the preview: https://6a689fa68e05fb299b0d3dff--eclipse-che-docs-pr.netlify.app 🎊

@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown

Click here to review and test in web IDE: Contribute

Add procedure for deleting extensions from the managed Open VSX
registry using the admin API. Fix verification pod labels to use
app.kubernetes.io/component instead of app=openvsx. Add NOTE about
the registry starting empty.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
{prod-short} supports three registry configurations:
{prod-short} supports four registry configurations:

Embedded Open VSX registry:: Runs in the `plugin-registry` pod and supports air-gapped, offline, and proxy-restricted environments. Contains a default subset of extensions that you can customize.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we have an ordered list here 1 - 4 ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done
Screenshot 2026-07-28 at 14 58 12


Embedded Open VSX registry:: Runs in the `plugin-registry` pod and supports air-gapped, offline, and proxy-restricted environments. Contains a default subset of extensions that you can customize.

Public Open VSX registry:: The community-hosted registry at `open-vsx.org`, accessed over the internet. Provides the full catalog of openly published extensions.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, we might want to highlight option 5: https://managed.open-vsx.org/pricing/
manged openvsx

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Screenshot 2026-07-28 at 14 58 12

:page-aliases:

[id="enabling-the-managed-open-vsx-registry"]
= Enabling the managed Open VSX registry

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's clarify that this is tech-preview

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2026-07-28 at 15 27 31

@gtrivedi88 gtrivedi88 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JTBD mapping

This content maps to Extend > Customize workspace tooling (extend_tooling), specifically Job 34: Control which editors developers can use. It belongs under assembly_deploying-private-registry (Deploy a private extension registry) alongside the existing self-hosted Open VSX procedures.

Merge sequencing recommendation

Option A (preferred): Merge PR #3143 (Extend JTBD restructuring) first, then rebase this PR to place the new file directly in the Extend module (modules/extend/). This avoids the file being added to administration-guide/ and then immediately moved.

Option B (acceptable): Merge this PR first if the feature needs docs before #3143 is ready. The person rebasing #3143 will need to:

  1. Move enabling-the-managed-open-vsx-registry.adoc from administration-guide/pages/ to extend/pages/
  2. Add the xref: to extend/nav.adoc (and remove it from administration-guide/nav.adoc)
  3. Resolve 2-3 small merge conflicts in managing-ide-extensions.adoc and extensions-for-microsoft-visual-studio-code-open-source.adoc

This is roughly 15 minutes of rebase work, so not a blocker.

Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated
Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated

@gtrivedi88 gtrivedi88 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-posting misplaced inline comments at the correct lines. Apologies for the earlier confusion.

Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated
Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated
Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated
Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated
Comment thread modules/administration-guide/pages/enabling-the-managed-open-vsx-registry.adoc Outdated
svor and others added 9 commits July 28, 2026 12:52
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc

Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
[role="_abstract"]
[IMPORTANT]
====
The managed Open VSX registry is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The managed Open VSX registry is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
The managed Open VSX registry is a Technology Preview feature only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants