-
Notifications
You must be signed in to change notification settings - Fork 335
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
feat(*): enable Gateway with runtime flag #3736
Conversation
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #3736 +/- ##
==========================================
+ Coverage 50.89% 50.93% +0.04%
==========================================
Files 924 923 -1
Lines 56960 56990 +30
==========================================
+ Hits 28987 29026 +39
+ Misses 25689 25679 -10
- Partials 2284 2285 +1
Continue to review full report at Codecov.
|
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
// to a Kubernetes zone, we would need to be able to transform Gateway | ||
// resources from Universal -> Kubernetes and have to deal with namespace | ||
// semantics and a lot of other unpleasantness. | ||
// RegisterTypeIfAbsent is used because it's not deterministic in testing that RegisterGatewayTypes is called only once. |
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.
Do we know why it's not deterministic? Could/should it be?
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.
For example BuildRuntime()
is a problem. It registers the plugin for every test case, but Type Registry is unfortunately global, so it tries to register multiple times.
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.
Looks good otherwise, I just fear the non determinism is due to some kind of broken initialization when we run the tests.
…e-flag Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
Summary
Enabled Gateway with runtime configuration instead of a flag during compilation.
This lets us ship gateway as an experimental opt-in feature.
Full changelog
kumactl get
,kumactl delete
andkumactl apply
by default, even if it's not enabled in CP. Typing extra--experimental-gateway
for all those commands would be annoying if anyone would like to use Gateway now.--experimental-gateway
tokumactl install gateway
. Only in this case we install Gateway resources and RBAC.Issues resolved
Fix #3722
Documentation
Testing
Backwards compatibility
- [ ] UpdateUPGRADE.md
with any steps users will need to take when upgrading.- [ ] Addbackport-to-stable
label if the code follows our backporting policy