install instructions in readme

.drone.yml

@@ -43,3 +43,32 @@ steps:
       - push
       - pull_request
       - cron
+---
+kind: pipeline
+type: kubernetes
+name: release-bitwarden-crd-operator
+
+platform:
+  os: linux
+  arch: amd64
+
+steps:
+  - name: release-bitwarden-crd-operator
+    image: plugins/kaniko
+    settings:
+      dockerfile: Dockerfile
+      password:
+        from_secret: docker_password
+      username:
+        from_secret: docker_username
+      repo: lerentis/bitwarden-crd-operator
+      tags:
+        - latest
+        - ${DRONE_TAG##v}
+    when:
+      event:
+      - tag
+    resources:
+      limits:
+        cpu: 200
+        memory: 1024MiB

.github/workflows/release.yml

@@ -1,8 +1,9 @@
 name: Release Charts
 
 on:
-  release:
+  push:
-    types: [published]
+    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 }}"

README.md

@@ -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  
+- [ ] support more types
-[] offer option to use a existing secret in helm chart  
+- [ ] offer option to use a existing secret in helm chart
-[] host chart on gh pages  
+- [x] host chart on gh pages
-[] write release pipeline  
+- [x] write release pipeline
-[x] maybe extend spec to offer modification of keys as well
+- [x] maybe extend spec to offer modification of keys as well

charts/bitwarden-crd-operator/Chart.yaml

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

charts/bitwarden-crd-operator/templates/NOTES.txt

@@ -1 +1,2 @@
-Have fun :) 
+Bitwarden CRD Operator has been deployed. 
+Go ahead and create some secrets directly from bitwarden

charts/bitwarden-crd-operator/values.yaml

@@ -8,7 +8,7 @@ image:
   repository: lerentis/bitwarden-crd-operator
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "5806fb6c54c024ec918eac97601880096b5ff1d9"
+  # tag: "0.1.0"
 
 imagePullSecrets: []
 nameOverride: ""