Skip to content

docs: Add cluster login step to Open VSX deployment procedures #3123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vinokurig merged 2 commits into from
Jun 11, 2026
+4 −1
Merged

docs: Add cluster login step to Open VSX deployment procedures #3123

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e70900d
docs: Add cluster login step to Open VSX deployment procedures
vinokurig Jun 11, 2026
8615871
Update modules/administration-guide/pages/proc_deploy-open-vsx-from-w…
vinokurig Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,9 @@ The link:https://github.com/eclipse-openvsx/openvsx/blob/master/.devfile.yaml[.d
The environment, including all necessary commands, is defined in the `.devfile.yaml` file.
====

. Login to the cluster as a cluster administrator from the workspace terminal:
.. Navigate to *Terminal* -> *New Terminal*
.. Execute: `$ oc login --token=<USER_TOKEN> --server=<CLUSTER_API_URL>`
. Create a new project for Open VSX.
+
Run the `2.1. Create Namespace for OpenVSX` task in the workspace:
Expand Down
2 changes: 1 addition & 1 deletion ...istration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@ The embedded plugin registry is deprecated. Setting up an internal, on-premises

.Prerequisites

* You are logged in to your {prod-short} instance as an administrator.
* You have started a workspace using the link:{plugin-registry-repo-url}[plugin registry repository].
* You are logged in to the cluster as a cluster administrator from the workspace terminal: `$ oc login --token=<USER_TOKEN> --server=<CLUSTER_API_URL>`
* You have created a link:https://access.redhat.com/terms-based-registry/[Red Hat Registry Service Account] and have the username and token available.
* For IBM Power (`ppc64le`) and IBM Z (`s390x`) architectures, you must build the custom plugin registry locally on the corresponding hardware.
* (Optional) You can rebuild the container based on the latest tag or SHA to get the latest security fixes after a {prod-short} update.
Expand Down
Loading