-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[registry-facade] Remove feature flag #3182
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
Conversation
7d1a74f
to
2266068
Compare
and enable registry-facade by default.
2266068
to
ff9d321
Compare
if ir.Config.Config.BlobServer == nil { | ||
ir.handleRootWithoutBlobserve(route) | ||
return | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the change in the ws-proxy-configmap.yaml
above it's still possible that the blobServer
config is missing (when blobserve
component is disabled). Doesn't that conflict with removing this case here?
I have also found a few lines with references to node-daemon. 😆
This one breaks Lines 114 to 116 in ff9d321
And here are two self-hosted files with references to node-daemon. Don't know if you want to address it in this PR as well or create an issue for this: gitpod/docs/self-hosted/install/nodes.md Lines 29 to 33 in ff9d321
gitpod/install/gcp-terraform/modules/gitpod/templates/values.node-layout.tpl Lines 5 to 9 in ff9d321
|
to the node anymore. Instead, registry-facade serves the IDE. The remaining sysctls were moved as init container to ws-daemon.
With registry-facade becoming the default, we can also make blobserve standard.
ff9d321
to
52054d0
Compare
Thank you for pointing those bits out. I've gone over the PR one more time and removed these bits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with the preview environment and self-hosted (k3s image). Both work fine.
This PR removes all variance surrounding registry-facade. Once this is merged, registry-facade is the sole way to start workspaces. To this end, we remove
registry_facade
feature flag and all variance it created in ws-managersysctls
are now an init container on ws-daemonHow to test
fixes #2655