2 Commits

Author SHA1 Message Date
7d4f01caf6 install instructions in readme
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2022-10-03 19:28:14 +02:00
fc4e561f29 release on push to main branch
All checks were successful
continuous-integration/drone/push Build is passing
2022-10-03 19:17:16 +02:00
3 changed files with 15 additions and 10 deletions

View File

@ -1,8 +1,9 @@
name: Release Charts
on:
release:
types: [published]
push:
branches:
- main
jobs:
release:
@ -27,5 +28,7 @@ jobs:
- name: Run chart-releaser
uses: helm/chart-releaser-action@v1.4.1
with:
charts_dir: charts
env:
CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

View File

@ -31,8 +31,10 @@ env:
After that it is a basic helm deployment:
```bash
helm repo add bitwarden-operator https://lerentis.github.io/bitwarden-crd-operator
helm repo update
kubectl create namespace bw-operator
helm upgrade --install --namespace bw-operator -f chart/bitwarden-crd-operator/values.yaml bw-operator chart/bitwarden-crd-operator
helm upgrade --install --namespace bw-operator -f values.yaml bw-operator bitwarden-operator/bitwarden-crd-operator
```
And you are set to create your first secret using this operator. For that you need to add a CRD Object like this to your cluster:
@ -75,8 +77,8 @@ type: Opaque
## Short Term Roadmap
[] support more types
[] offer option to use a existing secret in helm chart
[x] host chart on gh pages
[x] write release pipeline
[x] maybe extend spec to offer modification of keys as well
- [ ] support more types
- [ ] offer option to use a existing secret in helm chart
- [x] host chart on gh pages
- [x] write release pipeline
- [x] maybe extend spec to offer modification of keys as well

View File

@ -4,6 +4,6 @@ description: Deploy the Bitwarden CRD Operator
type: application
version: 0.1.1
version: "v0.1.2"
appVersion: "0.1.1"
appVersion: "0.1.2"