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
operator: introduce gateway api cell #28785
operator: introduce gateway api cell #28785
Conversation
/test |
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.
LGTM ✔️
f3cd727
to
88dc526
Compare
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.
Great, thanks!
I've left a suggestion for a follow up PR inline.
/test |
This commit moves the Gateway API controller registration from the legacyOnLeader cell to its own cell. In addition, the config properties `enable-gateway-api-secrets-sync` & `gateway-api-secrets-namespace` are moved from the global operator config to a dedicate gatewayApiConfig struct. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
88dc526
to
a5827f4
Compare
rebased to main as gateway api conformance test check was failing -> #28654 added an additional gRPC test (file was missing) |
/test |
This commit moves the Gateway API controller registration from the legacyOnLeader cell to its own cell.
In addition, the config properties
enable-gateway-api-secrets-sync
&gateway-api-secrets-namespace
are moved from the global operator config to a dedicate gatewayApiConfig struct.