-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
encryption config: no-op refactor to prepare for single loading #112703
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enj 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 |
func GetKMSPluginHealthzCheckers(filepath string, stopCh <-chan struct{}) ([]healthz.HealthChecker, error) { | ||
f, err := os.Open(filepath) | ||
_, kmsHealthChecks, err := LoadEncryptionConfig(filepath, stopCh) | ||
return kmsHealthChecks, err | ||
} | ||
|
||
func GetTransformerOverrides(filepath string, stopCh <-chan struct{}) (map[schema.GroupResource]value.Transformer, error) { | ||
transformers, _, err := LoadEncryptionConfig(filepath, stopCh) | ||
return transformers, err | ||
} |
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.
I will handle deleting these in #112685 (i.e. the single loading bit).
/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.
Just one small nit, but otherwise lgtm!
staging/src/k8s.io/apiserver/pkg/server/options/encryptionconfig/config.go
Outdated
Show resolved
Hide resolved
@@ -169,10 +163,7 @@ func TestEnvelopeCacheLimit(t *testing.T) { | |||
} | |||
|
|||
func BenchmarkEnvelopeCBCRead(b *testing.B) { |
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.
I don't see these used anywhere. Should we remove these in a follow-up PR?
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.
I think benchmarks in k/k are only every manually run (to prove if some change was good/bad for performance).
// remove after 1.13 | ||
func TestBackwardsCompatibility(t *testing.T) { |
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.
Remove after 1.13? 😄 I can help clean these up in a follow-up.
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.
I think this comment is wrong because we do not run storage migration automatically so we cannot assume that folks are not using the old non-cryptobyte format.
xref: #69249 (comment)
Signed-off-by: Monis Khan <mok@microsoft.com>
cfb395c
to
db85093
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.
/lgtm
Signed-off-by: Monis Khan mok@microsoft.com
/kind cleanup
/triage accepted
/assign @aramase
xref #111922 #112685 #112486