-
Notifications
You must be signed in to change notification settings - Fork 317
Read-Only Mode #2922
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
Read-Only Mode #2922
Conversation
Hi @08volt. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/ok-to-test |
a43038f
to
af16c2b
Compare
/retest |
/retest |
1 similar comment
/retest |
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.
Please verify we add the read only mode only in the places we need it. Review all controllers and ask for review when done
/retest |
b03d134
to
b50ed0d
Compare
57452b4
to
4a2900a
Compare
/retest |
5f719e3
to
e823b0d
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 08volt, mmamczur The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Commenting on a closed PR, but we should convert this into metrics on the API calls instead of logs.
Also is there a read out of what this would look like? Will the controller keep erroring on its reads (because no writes have been made)?
Actually diving deeper, this doesn't feel like read only mode. This is more just logging when a sync is triggered |
This pull request introduces a new
--read-only
flag to run the ingress-gce controllers in a non-mutating, observational mode.Summary
When the
read-only
flag is enabled, the controllers will not execute any mutating API calls (e.g., create, update, delete) against the cloud provider.This change touches the following controllers:
Testing
Comprehensive tests have been added for each controller to ensure that no mutating operations are performed when read-only mode is active. Existing test suites have been parameterized to run in both standard and read-only modes, asserting that resources are not created or modified in the latter.