-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[vnet] remote app provider #51279
[vnet] remote app provider #51279
Conversation
3d197ac
to
7f8b0b3
Compare
7f8b0b3
to
375602d
Compare
a3a4c20
to
53684bd
Compare
5486ab6
to
a80b639
Compare
a80b639
to
6086c59
Compare
mu sync.Mutex | ||
// appSignerCache caches the crypto.Signer for each certificate issued by | ||
// ReissueAppCert so that SignForApp can later use that signer. | ||
appSignerCache map[appKey]crypto.Signer |
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.
What is the lifecycle for entries in the map?
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.
added a comment, we never need to evict signers because when the cert expires, ReissueAppCert will overwrite the signer with a new one. We currently never clean up stale app proxies that haven't been used for a while, one day we should probably do that to free up memory, at that point we should clean up the signers too
f34a5a6
to
7ad0064
Compare
@nklaassen See the table below for backport results.
|
Backport #51279 to branch/v17
Backport #51279 to branch/v17
Backport #51279 to branch/v17
Backport #51279 to branch/v17
Part of RFD 195.
As a follow-up to #51216, this PR implements
vnet.remoteAppProvider
which exposes apps to the VNet Windows admin service over gRPC. I'm also adding a unit test that asserts that networking works when apps are provided via the remote app provider.