Skip to content

Add Vault KMSv2 plugin and update socket path to kms.sock#2096

Draft
gangwgr wants to merge 1 commit intoopenshift:masterfrom
gangwgr:vault-kms-plugin
Draft

Add Vault KMSv2 plugin and update socket path to kms.sock#2096
gangwgr wants to merge 1 commit intoopenshift:masterfrom
gangwgr:vault-kms-plugin

Conversation

@gangwgr
Copy link
Copy Markdown
Contributor

@gangwgr gangwgr commented Jan 28, 2026

No description provided.

@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 Jan 28, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 28, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 28, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gangwgr
Once this PR has been reviewed and has the lgtm label, please assign p0lyn0mial for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@gangwgr
Add Vault KMSv2 plugin and update socket path to kms.sock
5b402df 
- Add Vault KMSv2 plugin for e2e encryption tests
  - main.go: KMS v2 gRPC server connecting to Vault Transit
  - Dockerfile: Multi-stage build for the plugin image
  - go.mod/go.sum: Go module dependencies
  - build-image.sh: Script to build the container image
  - deploy-vault-kms-plugin.sh: Script to deploy on OpenShift
  - README.md: Documentation and usage instructions

- Update socket path from socket.sock to kms.sock
  - vault-plugin files updated
  - k8s_mock_kms_plugin_daemonset.yaml updated
@openshift-bot
Copy link
Copy Markdown

openshift-bot commented Apr 30, 2026

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@gangwgr @openshift-bot