Merge pull request #14 from epinio/add_epinio_small

Add the Epinio "small" chart

Author: Dimitris Karakasilis

.github/workflows/lint-test.yml

@@ -25,14 +25,3 @@ jobs:
           fi
       - name: Run chart-testing (lint)
         run: ct lint --config ct.yaml
-
-      - name: Set up k3d cluster
-        uses: nolar/setup-k3d-k3s@v1
-        with:
-          version: v1.22
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-        if: steps.list-changed.outputs.changed == 'true'
-
-      - name: Run chart-testing (install)
-        run: ct install --config ct.yaml
-

chart/epinio-installer/Chart.yaml

@@ -0,0 +1,16 @@
+apiVersion: v1
+name: epinio-installer
+version: "0.1.20"
+appVersion: "v0.2.1"
+description: Deploys Epinio and dependencies automatically
+home: https://github.com/epinio/epinio
+icon: https://raw.githubusercontent.com/epinio/epinio-helm-chart/main/assets/epinio.png
+keywords:
+- epinio
+- paas
+sources:
+- https://github.com/epinio/epinio-helm-chart
+maintainers:
+- name: epinio
+  email: team@epinio.io
+  url: https://epinio.io/

chart/epinio-installer/README.md

@@ -0,0 +1,12 @@
+# Epinio Helm Chart
+
+From app to URL in one command.
+
+## Introduction
+
+This helm chart can be used to deploy Epinio on a cluster. It is an alternative
+to `epinio install` command.
+
+## Usage
+
+The doc is centralized in a uniq place, checkout the [doc website](https://docs.epinio.io/installation/install_epinio_with_helm.html).

chart/epinio/questions.yml chart/epinio-installer/questions.ymlchart/epinio/questions.yml renamed to chart/epinio-installer/questions.yml

@@ -0,0 +1,15 @@
+
+{{- if .Values.domain }}
+You can get the IP address of your Ingress controller by passing this command:
+`kubectl describe svc traefik --namespace traefik | grep Ingress | awk '{print $3}'`
+
+Make sure your domain points to the IP address of your Ingress controller (1.2.3.4).
+{{ end }}
+To interract with your Epinio installation, you have to download the latest epinio binary https://github.com/epinio/epinio/releases.
+
+Update the api location and credentials with:
+`epinio config update`
+
+Then, you have to run `epinio namespace create workspace`
+
+For more information about Epinio, feel free to checkout https://epinio.io/ and https://docs.epinio.io/.

chart/epinio-installer/templates/NOTES.txt

@@ -0,0 +1,52 @@
+## Default values for Epinio Helm Chart.
+## This is a YAML-formatted file.
+## Declare variables to be passed into your templates.
+
+# Domain which serves the Rancher UI (to access the API)
+# accessControlAllowOrigin: ""
+
+# The email address you are planning to use for getting notifications about your certificates. (default "epinio@suse.com")
+email: "epinio@suse.com"
+
+# The name of the cluster issuer to use. Epinio creates three options: 'epinio-ca', 'letsencrypt-production', and 'selfsigned-issuer'. (default "epinio-ca")
+tlsIssuer: "epinio-ca"
+
+# The domain you are planning to use for Epinio. Should be pointing to the traefik public IP (mandatory option).
+domain: "localhost.omg.howdoi.website"
+
+# The user name for authenticating all API requests.
+# user: ""
+
+# The password for authenticating all API requests.
+# password: ""
+
+# Assert to epinio that cert-manager is already installed.
+# skipCertManager: false
+
+# Assert to epinio that Linkerd is already installed.
+# skipLinkerd: false
+
+# Assert to epinio that there is a Traefik active, even if epinio cannot find it.
+# skipTraefik: false
+
+# If you are using your own S3 compatible object storage for blobs, set the following options:
+# s3Endpoint: ""
+# s3AccessKeyId: ""
+# s3SecretAccessKey: ""
+# s3Bucket: ""
+
+# Optional
+# s3Location: ""
+# s3UseSSL: ""
+
+# If you are using your own external registry, set the following options:
+# --external-registry-url: ""
+# --external-registry-username: ""
+# --external-registry-password: ""
+
+# Optional
+# Provide namespace (or organization) of the external registry to which you have push access. It can be left empty.
+# --external-registry-namespace: ""
+
+# Use TLS when application images will be pulled by kubernetes. Only applies to the internal registry. (default "false")
+# --force-kube-internal-registry-tls: ""

chart/epinio/templates/post-install.yaml …io-installer/templates/post-install.yamlchart/epinio/templates/post-install.yaml renamed to chart/epinio-installer/templates/post-install.yaml chart/epinio/templates/post-install.yaml renamed to chart/epinio-installer/templates/post-install.yaml

@@ -1,16 +1,15 @@
 apiVersion: v1
 name: epinio
-version: 0.1.20
-appVersion: v0.2.1
-description: From app to URL in one command
+version: "0.1.0"
+appVersion: "v0.2.1"
+description: The Epinio component (without dependencies)
 home: https://github.com/epinio/epinio
 icon: https://raw.githubusercontent.com/epinio/epinio-helm-chart/main/assets/epinio.png
 keywords:
 - epinio
 - paas
 sources:
-- https://github.com/epinio/epinio-helm-chart
+- https://github.com/epinio/epinio
 maintainers:
-- name: epinio
+- name: SUSE
   email: team@epinio.io
-  url: https://epinio.io/