Update Transmission to latest templates

charts/transmission/Chart.yaml

@@ -2,10 +2,10 @@ apiVersion: 'v2'
 name: 'transmission'
 description: 'Chart for Transmission'
 type: 'application'
-version: 0.1.1
+version: 0.2.0
 appVersion: '4.0.5'
 icon: 'https://github.com/drinkataco/media-servarr/blob/main/charts/transmission/icon.png'
 dependencies:
   - name: 'media-servarr-base'
-    version: 0.1.1
+    version: 0.2.0
     repository: "file://../.."

charts/transmission/README.md

@@ -23,21 +23,25 @@ This README covers the basics of customising and installation
 Install this helm chart using the following command:
 
 ```bash
-helm repo add mediar-servarr https://media-servarr.p.shw.al/charts
+helm repo add mediar-servarr https://media-servarr.shw.al/charts
 
-helm install transmission media-servarr/transmission -f myvalues.yaml -f mysecrets.yaml
+helm install transmission media-servarr/transmission
 ```
 
+Pointing the host `media-servarr.local` to your kubernetes cluster will then allow you to access the application at the default location of `http://media-servarr.local/transmission/`
+
 ## Configuration
 
-Here is some example of some configuration you may want to override.
+Here is some example of some configuration you may want to override (and include in installation with `-f myvalues.yaml`
 
 ### Application Configuration
 
 By default, base configuration is defined using a ConfigMap - defined by default in `./values.yaml` in `application.config`. You can change values in the contents, such as the url base in your custom `values.yaml`
 
 ```yaml
 application:
+  port: 9091 # default UI port
+  urlBase: 'transmission' # default web base path
   config:
     filename: 'settings.json'
     contents: |
@@ -55,6 +59,7 @@ You can prevent a ConfigMap being create and the configuration being managed as
 
 ```yaml
 application:
+  ...
   config: null
 ```
 
@@ -65,7 +70,6 @@ Three volumes are available by default:
 - **config** - General config data - where settings exist
 - **downloads** - Downloads folder
 
-
 ```yaml
 deployment:
   ...
@@ -101,13 +105,6 @@ If ingress is enabled, you can customise the host, paths, and TLS settings:
 ```yaml
 ingress:
   enabled: true
-  hosts:
-    - host: 'mymedia.example.com'
-      paths:
-        - path: '/transmission/'
-          pathType: 'ImplementationSpecific'
-  tls:
-    # Your TLS settings...
 ```
 
 ### Advanced
@@ -123,7 +120,7 @@ Have a look at the parent charts default `values.yaml` for a comprehensive list
 To upgrade the deployment:
 
 ```bash
-helm upgrade transmission media-servarr/transmission -f myvalues.yaml -f mysecrets.yaml
+helm upgrade transmission media-servarr/transmission -f myvalues.yaml
 ```
 
 ## Uninstallation
@@ -137,4 +134,3 @@ helm delete transmission
 ## Support
 
 For support, issues, or feature requests, please file an issue on the chart's repository issue tracker.
-

charts/transmission/values.yaml

@@ -13,6 +13,11 @@ secrets:
 # Application Config
 #
 application:
+  # main application web ui port
+  port: 9091
+  # access url base
+  urlbase: 'transmission'
+  # ConfigMap for core application settings
   config:
     # Filename of configuration
     filename: 'settings.json'
@@ -122,7 +127,7 @@ deployment:
 
     ports:
       - name: 'http'
-        containerPort: 9091
+        containerPort: # use application.port
         protocol: 'TCP'
       - name: 'peer'
         containerPort: 51413
@@ -165,7 +170,7 @@ persistentVolumeClaims:
 service:
   type: 'LoadBalancer'
   ports:
-    - port: 9091
+    - port: # use application.port by default
       targetPort: 'http'
       protocol: 'TCP'
       name: 'http'
@@ -180,11 +185,3 @@ service:
 
 ingress:
   enabled: true
-  annotations: {}
-  hosts:
-    - host: 'media-servarr.local'
-      paths:
-        - path: '/transmission'
-          pathType: 'Prefix'
-          port: 9091
-  tls: []