Skip to content

Move default workspaceImage setting out of experimental #11408

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.

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

Closed
lucasvaltl opened this issue Jul 15, 2022 · 0 comments · Fixed by #11531
Closed

Move default workspaceImage setting out of experimental #11408

lucasvaltl opened this issue Jul 15, 2022 · 0 comments · Fixed by #11531

Comments

@lucasvaltl
Copy link
Contributor

Is your feature request related to a problem? Please describe

Currently, to set a global default workspace image, you need to add it to a config patch file in the following manner:

experimental:
  webapp:
    server:
      workspaceDefaults:
        # update with the docker image you want for workspaces. If the workspace default
        # base image is stored in a private repo, this registry should be the same as the
        # registry specified in config page in KOTS dashboard. This is the only supported authentication method atm.
        workspaceImage: registry.server.io/repository/workspace-image:latest

Describe the behaviour you'd like

  • Default workspace image can be set in the config - happy to chat about where and how exactly.
  • We have a guide in our docs that explains how & why to do this and clarifies the limitations

Describe alternatives you've considered

  • Expect every user to have a image set in the gitpod.yml - this is a hassle for some users, and something they would have to remember for every project / repo.

Related ticket

Additional context

@lucasvaltl lucasvaltl changed the title Move default workspaceImage: setting out of experimental Move default workspaceImage setting out of experimental Jul 15, 2022
Repository owner moved this from 📓Scheduled to ✨Done in 🚚 Security, Infrastructure, and Delivery Team (SID) Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant