Skip to content
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

API-1509: Enable aes-gcm encryption provider #1469

Merged
merged 1 commit into from Feb 28, 2023

Conversation

dgrisonnet
Copy link
Member

@dgrisonnet dgrisonnet commented Feb 16, 2023

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2023
Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>
@dgrisonnet
Copy link
Member Author

@dgrisonnet dgrisonnet changed the title WIP: Enable aes-gcm encryption provider Enable aes-gcm encryption provider Feb 21, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 21, 2023
@dgrisonnet dgrisonnet changed the title Enable aes-gcm encryption provider API-1509: Enable aes-gcm encryption provider Feb 21, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 21, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 21, 2023

@dgrisonnet: This pull request references API-1509 which is a valid jira issue.

In response to this:

proof PR: openshift/cluster-kube-apiserver-operator#1446

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/test-infra repository.

dinhxuanvu

This comment was marked as duplicate.

Copy link
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2023
@@ -9,6 +9,7 @@ import (
var (
ModeToNewKeyFunc = map[state.Mode]func() []byte{
state.AESCBC: NewAES256Key,
state.AESGCM: NewAES256Key,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't realize it was exactly the same key. That's convenient.

@dgrisonnet
Copy link
Member Author

@deads2k can you please have another look at this PR now that the API has been merged?

@tkashem
Copy link
Contributor

tkashem commented Feb 28, 2023

/lgtm
/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 28, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgrisonnet, dinhxuanvu, tkashem

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 28, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 48b0500 and 2 for PR HEAD abaa55e in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 28, 2023

@dgrisonnet: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants