https://github.com/hopopops/vault-operator
An operator to support configuring ACL and KSA bindings to Vault policies and Vault authentication engine roles from within Kubernetes
https://github.com/hopopops/vault-operator
hashicorp-vault k8s-operator
Last synced: 4 months ago
JSON representation
An operator to support configuring ACL and KSA bindings to Vault policies and Vault authentication engine roles from within Kubernetes
- Host: GitHub
- URL: https://github.com/hopopops/vault-operator
- Owner: HopopOps
- Created: 2025-08-20T22:50:33.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2025-09-02T15:25:06.000Z (4 months ago)
- Last Synced: 2025-09-02T15:34:27.500Z (4 months ago)
- Topics: hashicorp-vault, k8s-operator
- Language: Go
- Homepage:
- Size: 68.4 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# vault-operator
A basic vault operator enabling the user to create custom vault resources such as policies and roles for kubernetes
authentication engine.
## Description
This is a basic Hashicorp Vault operator enabling the user to create custom vault resources such as policies and roles
for kubernetes authentication engine. It was written in order to be a part of GitOps pipelines making use of tools
like `external-secrets-operator` where one as to write and maintain a lot of vault policies and auth engine role.
Being able to store those parts of a configuration next to an app bundle using them is a nice QoL improvement.
This project is an exercise to demonstrate how simple it can be to augment kubernetes API thanks to the operator
pattern. The creator needed a simpler alternative to
[redhat-cop/vault-config-operator](https://github.com/redhat-cop/vault-config-operator), a project about
configuring vault from CRD. `vault-config-operator` already implement a large portion of Hashicorp Vault's API,
looks well maintained and will most likely fit your needs.
## Getting Started
### Prerequisites
- go version v1.24.0+
- docker version 17.03+.
- kubectl version v1.11.3+.
- Access to a Kubernetes v1.11.3+ cluster.
### To Deploy on the cluster
**Build and push your image to the location specified by `IMG`:**
```sh
make docker-build docker-push IMG=quay.io/hopopops/vault-operator:tag
```
**NOTE:** This image ought to be published in the personal registry you specified.
And it is required to have access to pull the image from the working environment.
Make sure you have the proper permission to the registry if the above commands don’t work.
**Install the CRDs into the cluster:**
```sh
make install
```
**Deploy the Manager to the cluster with the image specified by `IMG`:**
```sh
make deploy IMG=quay.io/hopopops/vault-operator:tag
```
> **NOTE**: If you encounter RBAC errors, you may need to grant yourself cluster-admin
privileges or be logged in as admin.
**Create instances of your solution**
You can apply the samples (examples) from the config/sample:
```sh
kubectl apply -k config/samples/
```
>**NOTE**: Ensure that the samples has default values to test it out.
### To Uninstall
**Delete the instances (CRs) from the cluster:**
```sh
kubectl delete -k config/samples/
```
**Delete the APIs(CRDs) from the cluster:**
```sh
make uninstall
```
**UnDeploy the controller from the cluster:**
```sh
make undeploy
```
## Project Distribution
Following the options to release and provide this solution to the users.
### By providing a bundle with all YAML files
1. Build the installer for the image built and published in the registry:
```sh
make build-installer IMG=quay.io/hopopops/vault-operator:tag
```
**NOTE:** The makefile target mentioned above generates an 'install.yaml'
file in the dist directory. This file contains all the resources built
with Kustomize, which are necessary to install this project without its
dependencies.
2. Using the installer
User can create a Kustomization to edit the parameters then just run 'kubectl apply -k ' to install the project, i.e.:
```yaml
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- https://raw.githubusercontent.com/hopopops/vault-operator/main/dist/install.yaml
patches:
- patch: |
- op: add
path: /spec/template/spec/containers/0/args/-
value: --vault-addr=https://vault.hopopops.com
target:
kind: Deployment
name: vault-operator-controller-manager
```
### By providing a Helm Chart
1. Build the chart using the optional helm plugin
```sh
kubebuilder edit --plugins=helm/v1-alpha
```
2. See that a chart was generated under 'dist/chart', and users
can obtain this solution from there.
**NOTE:** If you change the project, you need to update the Helm Chart
using the same command above to sync the latest changes. Furthermore,
if you create webhooks, you need to use the above command with
the '--force' flag and manually ensure that any custom configuration
previously added to 'dist/chart/values.yaml' or 'dist/chart/manager/manager.yaml'
is manually re-applied afterwards.
## Contributing
// TODO(user): Add detailed information on how you would like others to contribute to this project
**NOTE:** Run `make help` for more information on all potential `make` targets
More information can be found via the [Kubebuilder Documentation](https://book.kubebuilder.io/introduction.html)
## License
Copyright 2025 HopopOps, Inc..
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.