Fix PREVENT_METADATA_ACCESS is not effact#8336
Conversation
Codecov Report
@@ Coverage Diff @@
## main #8336 +/- ##
===========================================
- Coverage 33.00% 11.17% -21.84%
===========================================
Files 33 18 -15
Lines 4735 993 -3742
===========================================
- Hits 1563 111 -1452
+ Misses 3054 880 -2174
+ Partials 118 2 -116
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
4f7821e to
a1548ae
Compare
|
@iQQBot I'm trying to test, but workspaces don't get shutdown |
|
I cannot find |
a1548ae to
175624d
Compare
9103ea8 to
f471b66
Compare
f471b66 to
81c22a7
Compare
|
Hey @iQQBot , this definitely works as advertised, I cannot start workspaces in |
|
GITPOD_PREVENT_METADATA_ACCESS env variable control this behavior, if this env variable is set true, supervisor will try to access gcp endpoint, if it can access,supervisor will close itself This PR change all workspace's default env variable, set GITPOD_PREVENT_METADATA_ACCESS to true And this is is base on "fix" before, you can see commit history |
akosyakov
left a comment
There was a problem hiding this comment.
lgtm, works as advertised now

Description
rename THEIA_PREVENT_METADATA_ACCESS to GITPOD_PREVENT_METADATA_ACCESS
and fix is not effect in coredev
also fix workspace
nodeAffinityin core-dev maybe it can improve stable for core-devRelated Issue(s)
Relate https://github.com/gitpod-io/ops/pull/1246/files
How to test
metadata access is possiblelog in GCPRelease Notes
Documentation