-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[installer] Registry facade should not use a port from node ports range #8580
Conversation
install/installer/pkg/components/cluster/podsecuritypolicies.go
Outdated
Show resolved
Hide resolved
Codecov Report
@@ Coverage Diff @@
## main #8580 +/- ##
=========================================
- Coverage 12.31% 7.37% -4.95%
=========================================
Files 20 32 +12
Lines 1161 2225 +1064
=========================================
+ Hits 143 164 +21
- Misses 1014 2058 +1044
+ Partials 4 3 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
a6ed7e3
to
76f45e0
Compare
install/installer/pkg/components/image-builder-mk3/networkpolicy.go
Outdated
Show resolved
Hide resolved
/hold cancel |
We can add one using the drop metric https://docs.cilium.io/en/stable/operations/metrics/#drop |
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.
/hold
Happy with that, just on the question raised. If that's fine, just remove the hold
Unfortunately, this breaks our preview environment @aledbf |
Ah, I think preview env is still using helm chart? So maybe that change needs to be done in there too now |
no, it's using installer |
In order to install multiple gitpod in a single kubernetes, we modified the hostport of registry-facade using the post-install script, but not in the PodSecurityPolicy, which prevented the registry-facade from starting |
Now is clear why we had a range in the policy Fix #8612 |
Description
Some CNI providers (as Cilium) do not allow overlap between
hostPorts
andnodePorts
Release Notes