-
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
Replace cluster periodics with watchers #9609
Conversation
f5d5c7f
to
0ad9b7b
Compare
0ad9b7b
to
32e9a28
Compare
6b69282
to
2dbdd96
Compare
} | ||
newHost = make(map[string]types.CertAuthority, len(host)) | ||
for _, ca := range host { | ||
newHost[ca.GetName()] = ca |
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.
nit: ca.GetID()
may also be a good option for keys. I think in that case you only need one map too. not big deal. and hopefully when generics come, it will make these conversions easier
2dbdd96
to
fdc2603
Compare
@rosstimothy @fspmarshall I know that locks have different states they can be in with respect to availability. Does this take that into consideration? |
The |
fdc2603
to
3de91da
Compare
e8470de
to
b77c080
Compare
Remove periodically sending locks and certificate authorities to leaf clusters. Instead we can rely on the watcher system to only deliver resources to leaf clusters when changes occur. Fixes #8817
…otateTrustedClusters test.
…thorityWatcher test.
… Filter is opt-in by default
b77c080
to
0d381dc
Compare
Remove periodically sending locks and certificate authorities to leaf clusters. Instead
we can rely on the watcher system to only deliver resources to leaf clusters when changes occur.
Fixes #8817