-
Notifications
You must be signed in to change notification settings - Fork 96
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
Watch for Secrets #807
Merged
Merged
Watch for Secrets #807
+1,935
−1,777
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pleshakov
commented
Jun 30, 2023
sjberman
reviewed
Jul 3, 2023
kate-osborn
requested changes
Jul 5, 2023
This was referenced Jul 6, 2023
not resolving conflicts yet, so that those changes don't clutter the changes based on the feedback so far |
kate-osborn
reviewed
Jul 6, 2023
sjberman
reviewed
Jul 7, 2023
sjberman
approved these changes
Jul 7, 2023
kate-osborn
approved these changes
Jul 7, 2023
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.
🚀
pleshakov
force-pushed
the
feature/watch-for-secrets
branch
from
July 7, 2023 16:40
1f91dc4
to
6830fd7
Compare
Problem: NKG doesn't watch for updates of TLS Secrets referenced by Gateway resource. Solution: - Move secrets processing into ChangeProcessor. - Introduce helper secretResolver component to resolve Secrets (includes validation) and capture resolved Secrets. - When building Gateway Listener, resolve Secrets using secretResolver. - When building Graph, add referenced Secrets by Gateway to the Graph, including the ones that don't exists. - When Upserting or Deleting a Secret to ChangeProccessor, use Graph to determine if the Secret is referenced by the Graph and thus changes the store. - When building Configuration, add all TLS Secrets to it referenced by _valid_ TLS Listeners. - Update NGINX file.Manager so that it can deal with multiple files of two types: regular and secret. - Remove SecretStore and SecretDiskMemoryManager components. Solves nginxinc#553 Solves nginxinc#441 Testing: - Update affected and add new unit tests - Manual testing - Conformance testing. Relevant tests pass: TestConformance/GatewayInvalidTLSConfiguration
pleshakov
force-pushed
the
feature/watch-for-secrets
branch
from
July 7, 2023 16:53
6830fd7
to
0262e1d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Problem:
NKG doesn't watch for updates of TLS Secrets referenced by Gateway resource.
Solution:
Testing:
Closes #553
Closes #441
Checklist
Before creating a PR, run through this checklist and mark each as complete.