[updatecli] Bump epinio server version (#46)

* chore: Update key "image.epinio.tag" from file "/tmp/updatecli/epinio/h...

... elm-charts/chart/epinio/values.yaml"

Made with ❤️️  by updatecli

* chore: Update key "image.epinio.tag" from file "/tmp/updatecli/epinio/h...

... elm-charts/chart/epinio/values.yaml"

Made with ❤️️  by updatecli

* Update chart/epinio/Chart.yaml

* Update chart/epinio/values.yaml

Co-authored-by: GitHub Actions <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Loic Devulder <[email protected]>

chart/epinio/Chart.yaml

@@ -1,15 +1,15 @@
 apiVersion: v1
-name: epinio
-version: "0.2.1"
-appVersion: "v0.3.1"
+appVersion: v0.3.2
 description: The Epinio component (without dependencies)
 home: https://github.com/epinio/epinio
 icon: https://raw.githubusercontent.com/epinio/helm-charts/main/assets/epinio.png
 keywords:
 - epinio
 - paas
+maintainers:
+- email: [email protected]
+  name: SUSE
+name: epinio
 sources:
 - https://github.com/epinio/epinio
-maintainers:
-- name: SUSE
-  email: [email protected]
+version: 0.2.2

chart/epinio/values.yaml

@@ -4,15 +4,12 @@
 
 # The email address you are planning to use for getting notifications about your certificates.
 email: "[email protected]"
-
 # The URL of the container registry from where to pull container images
 # for the various created Pods. Don't confuse this registry with the "Epinio
 # registry" which is the one where Epinio stores the application images.
 registryURL: ""
-
 # The system domain that will be used to access the epinio API server
 systemDomain: ""
-
 image:
   epinio:
     repository: splatform/epinio-server
@@ -26,26 +23,19 @@ image:
   kubectl:
     repository: lachlanevenson/k8s-kubectl
     tag: v1.22.2
-
 server:
   # Domain which serves the Rancher UI (to access the API)
   accessControlAllowOrigin: ""
-
   # increase this value to increase all timeouts by the same factor
   timeoutMultiplier: 1
-
   # Change this to a random string. Used for session cookies by the API server.
   sessionKey: "12345"
-
   # The name of the cluster issuer to use.
   # Epinio creates three options: 'epinio-ca', 'letsencrypt-production', and 'selfsigned-issuer'.
   tlsIssuer: "epinio-ca"
-
   # Increase this value to instruct the API server to produce more debug output
   traceLevel: 0
-
 certManagerNamespace: ""
-
 # Connection details for the S3 storage
 s3:
   endpoint: s3.amazonaws.com
@@ -54,32 +44,27 @@ s3:
   accessKeyID: ""
   secretAccessKey: ""
   useSSL: true
-
 # Connection details for the container registry
 registry:
   url: ""
   localhostURL: ""
   username: ""
   password: ""
-
   # The registry namespace (aka org). Don't confuse this with Kubernetes
   # namespaces. This one is just the part between the registry url and the
   # image name (e.g. your username if you are using your account on Dockerhub).
   namespace: ""
-
   # The secret which Tekton's buildpack task uses to validate the registry's
   # certificate. If provided, it will be mounted inside the Tekton pod so that Tekton
   # can trust it when pushing the generated image.
   certificateSecret: ""
-
   # The namespace in which the above secret is stored
   # When set, the tekton-staging namespace will be annotated so that any secret
   # annotated with:
   #    "kubed.appscode.com/sync": "kubed-registry-tls-from=the_value_below"
   # will be copied there. The registry certificate should have such an annotation
   # if you are deploying one on the cluster.
   certificateSecretNamespace: ""
-
 api:
   # Default user username
   username: admin