diff --git a/deployment/helmchart/values.yaml b/deployment/helmchart/values.yaml index d5d25bd..6323aa8 100644 --- a/deployment/helmchart/values.yaml +++ b/deployment/helmchart/values.yaml @@ -21,10 +21,10 @@ global: ## @param kubeVersion Force target Kubernetes version (using Helm capabilities if not set) ## kubeVersion: "" -## @param nameOverride String to partially override discourse.fullname template (will maintain the release name) +## @param nameOverride String to partially override adminFrontend.fullname template (will maintain the release name) ## nameOverride: "" -## @param fullnameOverride String to fully override discourse.fullname template +## @param fullnameOverride String to fully override adminFrontend.fullname template ## fullnameOverride: "" ## @param commonLabels Labels to be added to all deployed resources @@ -77,7 +77,7 @@ service: ## @section Discourse parameters ## Bitnami Discourse image version -## ref: https://hub.docker.com/r/bitnami/discourse/tags/ +## ref: https://hub.docker.com/r/bitnami/adminFrontend/tags/ ## @param image.registry Discourse image registry ## @param image.repository Discourse image repository ## @param image.tag Discourse image tag @@ -86,9 +86,9 @@ service: ## @param image.debug Specify if debug logs should be enabled ## image: - registry: docker.io - repository: bitnami/discourse - tag: 2.7.8-debian-10-r22 + registry: open.greenhost.net:4567 + repository: openappstack/admin-frontend/admin-frontend + tag: 0.1.0 ## Specify a imagePullPolicy ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent' ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images @@ -108,38 +108,42 @@ image: ## @param imagePullSecrets Specify docker-registry secret names as an array ## imagePullSecrets: [] -## Discourse configuration parameters -## ref: https://github.com/bitnami/bitnami-docker-discourse#configuration +## Admin frontend configuration parameters +## ref: https://open.greenhost.net/openappstack/admin-frontend ## -discourse: - ## @param discourse.host Discourse host to create application URLs (include the port if =/= 80) +adminFrontend: + ## @param adminFrontend.reactAppApiUrl URL to the admin-backend API + reactAppApiUrl: "http://oas-api.initdevelopment.com/api/v1" + ## @param adminFrontend.extendEslint Whether to read .eslint.json rules + extendEslint: false + ## @param adminFrontend.host Discourse host to create application URLs (include the port if =/= 80) ## host: "" - ## @param discourse.siteName Discourse site name + ## @param adminFrontend.siteName Discourse site name ## siteName: 'My Site!' - ## @param discourse.username Admin user of the application + ## @param adminFrontend.username Admin user of the application ## username: user - ## @param discourse.password password. WARNING: Minimum length of 10 characters + ## @param adminFrontend.password password. WARNING: Minimum length of 10 characters ## Defaults to a random 10-character alphanumeric string if not set ## password: "" - ## @param discourse.existingSecret Name of an existing secret containing the password (ignores previous password) + ## @param adminFrontend.existingSecret Name of an existing secret containing the password (ignores previous password) ## The secret should contain the following key: - ## discourse-password + ## adminFrontend-password ## existingSecret: "" - ## @param discourse.email Admin user email of the application + ## @param adminFrontend.email Admin user email of the application ## email: user@example.com - ## @param discourse.command Custom command to override image cmd + ## @param adminFrontend.command Custom command to override image cmd ## command: [] - ## @param discourse.args Custom args for the custom command + ## @param adminFrontend.args Custom args for the custom command ## args: [] - ## @param discourse.containerSecurityContext Container security context specification + ## @param adminFrontend.containerSecurityContext Container security context specification ## Example: ## capabilities: ## drop: @@ -155,8 +159,8 @@ discourse: ## choice for the user. This also increases chances charts run on environments with little ## resources, such as Minikube. If you do want to specify resources, uncomment the following ## lines, adjust them as necessary, and remove the curly braces after 'resources:'. - ## @param discourse.resources.limits The resources limits for the container - ## @param discourse.resources.requests The requested resources for the container + ## @param adminFrontend.resources.limits The resources limits for the container + ## @param adminFrontend.resources.requests The requested resources for the container ## resources: ## Example: @@ -173,12 +177,12 @@ discourse: ## WARNING: Discourse installation process may take up some time and ## setting inappropriate values here may lead to pods failure. ## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes - ## @param discourse.livenessProbe.enabled Enable/disable livenessProbe - ## @param discourse.livenessProbe.initialDelaySeconds Delay before liveness probe is initiated - ## @param discourse.livenessProbe.periodSeconds How often to perform the probe - ## @param discourse.livenessProbe.timeoutSeconds When the probe times out - ## @param discourse.livenessProbe.failureThreshold Minimum consecutive failures for the probe - ## @param discourse.livenessProbe.successThreshold Minimum consecutive successes for the probe + ## @param adminFrontend.livenessProbe.enabled Enable/disable livenessProbe + ## @param adminFrontend.livenessProbe.initialDelaySeconds Delay before liveness probe is initiated + ## @param adminFrontend.livenessProbe.periodSeconds How often to perform the probe + ## @param adminFrontend.livenessProbe.timeoutSeconds When the probe times out + ## @param adminFrontend.livenessProbe.failureThreshold Minimum consecutive failures for the probe + ## @param adminFrontend.livenessProbe.successThreshold Minimum consecutive successes for the probe ## livenessProbe: enabled: true @@ -191,12 +195,12 @@ discourse: ## WARNING: Discourse installation process may take up some time and ## setting inappropriate values here may lead to pods failure. ## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes - ## @param discourse.readinessProbe.enabled Enable/disable readinessProbe - ## @param discourse.readinessProbe.initialDelaySeconds Delay before readiness probe is initiated - ## @param discourse.readinessProbe.periodSeconds How often to perform the probe - ## @param discourse.readinessProbe.timeoutSeconds When the probe times out - ## @param discourse.readinessProbe.failureThreshold Minimum consecutive failures for the probe - ## @param discourse.readinessProbe.successThreshold Minimum consecutive successes for the probe + ## @param adminFrontend.readinessProbe.enabled Enable/disable readinessProbe + ## @param adminFrontend.readinessProbe.initialDelaySeconds Delay before readiness probe is initiated + ## @param adminFrontend.readinessProbe.periodSeconds How often to perform the probe + ## @param adminFrontend.readinessProbe.timeoutSeconds When the probe times out + ## @param adminFrontend.readinessProbe.failureThreshold Minimum consecutive failures for the probe + ## @param adminFrontend.readinessProbe.successThreshold Minimum consecutive successes for the probe ## readinessProbe: enabled: true @@ -205,21 +209,21 @@ discourse: timeoutSeconds: 5 failureThreshold: 6 successThreshold: 1 - ## @param discourse.customLivenessProbe Custom liveness probe to execute (when the main one is disabled) + ## @param adminFrontend.customLivenessProbe Custom liveness probe to execute (when the main one is disabled) ## customLivenessProbe: {} - ## @param discourse.customReadinessProbe Custom readiness probe to execute (when the main one is disabled) + ## @param adminFrontend.customReadinessProbe Custom readiness probe to execute (when the main one is disabled) ## customReadinessProbe: {} ## Discourse SMTP settings - ## @param discourse.smtp.enabled Enable/disable SMTP - ## @param discourse.smtp.host SMTP host name - ## @param discourse.smtp.port SMTP port number - ## @param discourse.smtp.user SMTP account user name - ## @param discourse.smtp.password SMTP account password - ## @param discourse.smtp.protocol SMTP protocol (Allowed values: tls, ssl) - ## @param discourse.smtp.auth SMTP authentication method - ## @param discourse.smtp.existingSecret Name of an existing Kubernetes secret. The secret must have the following key configured: `smtp-password` + ## @param adminFrontend.smtp.enabled Enable/disable SMTP + ## @param adminFrontend.smtp.host SMTP host name + ## @param adminFrontend.smtp.port SMTP port number + ## @param adminFrontend.smtp.user SMTP account user name + ## @param adminFrontend.smtp.password SMTP account password + ## @param adminFrontend.smtp.protocol SMTP protocol (Allowed values: tls, ssl) + ## @param adminFrontend.smtp.auth SMTP authentication method + ## @param adminFrontend.smtp.existingSecret Name of an existing Kubernetes secret. The secret must have the following key configured: `smtp-password` ## smtp: enabled: false @@ -230,21 +234,21 @@ discourse: protocol: "" auth: "" existingSecret: "" - ## @param discourse.extraEnvVars An array to add extra env vars + ## @param adminFrontend.extraEnvVars An array to add extra env vars ## For example: ## extraEnvVars: - ## discourse: + ## adminFrontend: ## - name: DISCOURSE_ELASTICSEARCH_URL ## value: test ## extraEnvVars: [] - ## @param discourse.extraEnvVarsCM Array to add extra configmaps + ## @param adminFrontend.extraEnvVarsCM Array to add extra configmaps ## extraEnvVarsCM: [] - ## @param discourse.extraEnvVarsSecret Array to add extra environment variables from a secret + ## @param adminFrontend.extraEnvVarsSecret Array to add extra environment variables from a secret ## extraEnvVarsSecret: "" - ## @param discourse.extraVolumeMounts Additional volume mounts (used along with `extraVolumes`) + ## @param adminFrontend.extraVolumeMounts Additional volume mounts (used along with `extraVolumes`) ## Example: Mount CA file ## extraVolumeMounts ## - name: ca-cert @@ -252,7 +256,7 @@ discourse: ## mountPath: /path/to/ca_cert ## extraVolumeMounts: [] - ## @param discourse.skipInstall Do not run the Discourse installation wizard + ## @param adminFrontend.skipInstall Do not run the Discourse installation wizard ## Use only in case you are importing an existing database. ## skipInstall: false @@ -320,8 +324,8 @@ hostAliases: [] persistence: ## @param persistence.enabled Whether to enable persistence based on Persistent Volume Claims ## - enabled: true - ## @param persistence.storageClass discourse & sidekiq data Persistent Volume Storage Class + enabled: false + ## @param persistence.storageClass adminFrontend & sidekiq data Persistent Volume Storage Class ## If defined, storageClassName: ## If set to "-", storageClassName: "", which disables dynamic provisioning ## If undefined (the default) or set to null, no storageClassName spec is @@ -417,10 +421,10 @@ sidekiq: containerSecurityContext: {} ## @param sidekiq.command Custom command to override image cmd (evaluated as a template) ## - command: ['/opt/bitnami/scripts/discourse/entrypoint.sh'] + command: ['/opt/bitnami/scripts/adminFrontend/entrypoint.sh'] ## @param sidekiq.args Custom args for the custom command (evaluated as a template) ## - args: ['/opt/bitnami/scripts/discourse-sidekiq/run.sh'] + args: ['/opt/bitnami/scripts/adminFrontend-sidekiq/run.sh'] ## @param sidekiq.resources Sidekiq container resource requests and limits ## ref: http://kubernetes.io/docs/user-guide/compute-resources/ ## We usually recommend not to specify default resources and to leave this as a conscious @@ -533,7 +537,7 @@ ingress: certManager: false ## @param ingress.hostname Default host for the ingress resource ## - hostname: discourse.local + hostname: adminFrontend.local ## @param ingress.apiVersion Force Ingress API version (automatically detected if not set) ## apiVersion: "" @@ -558,15 +562,15 @@ ingress: ## @param ingress.extraHosts The list of additional hostnames to be covered with this ingress record. ## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array ## extraHosts: - ## - name: discourse.local + ## - name: adminFrontend.local ## path: / extraHosts: [] ## @param ingress.extraTls The tls configuration for additional hostnames to be covered with this ingress record. ## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls ## extraTls: ## - hosts: - ## - discourse.local - ## secretName: discourse.local-tls + ## - adminFrontend.local + ## secretName: adminFrontend.local-tls extraTls: [] ## @param ingress.secrets If you're providing your own certificates, please use this to add the certificates as secrets ## key and certificate should start with -----BEGIN CERTIFICATE----- or @@ -578,125 +582,7 @@ ingress: ## It is also possible to create and manage the certificates outside of this helm chart ## Please see README.md for more information ## Example: - ## - name: discourse.local-tls + ## - name: adminFrontend.local-tls ## key: ## certificate: secrets: [] - -## @section Database parameters - -## PostgreSQL chart configuration -## https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml -## -postgresql: - ## @param postgresql.enabled Deploy PostgreSQL container(s) - ## - enabled: true - ## @param postgresql.postgresqlUsername PostgreSQL user to create (used by Discourse). Has superuser privileges if username is `postgres`. - ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#setting-the-root-password-on-first-run - ## - postgresqlUsername: bn_discourse - ## @param postgresql.postgresqlPassword PostgreSQL password - ## Defaults to a random 10-character alphanumeric string if not set - ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#setting-the-root-password-on-first-run - ## - postgresqlPassword: "" - ## @param postgresql.postgresqlPostgresPassword PostgreSQL admin password (used when `postgresqlUsername` is not `postgres`) - ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#creating-a-database-user-on-first-run (see note!) - ## - postgresqlPostgresPassword: 'bitnami' - ## @param postgresql.existingSecret Name of existing secret object - ## The secret should contain the following keys: - ## postgresql-postgres-password (for root user) - ## postgresql-password (for the unprivileged user) - ## - existingSecret: "" - ## @param postgresql.postgresqlDatabase Name of the database to create - ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#creating-a-database-on-first-run - ## - postgresqlDatabase: bitnami_application - ## @param postgresql.persistence.enabled Enable database persistence using PVC - ## - persistence: - enabled: true -## External database configuration -## -externalDatabase: - ## @param externalDatabase.host Host of the external database - ## - host: "" - ## @param externalDatabase.port Database port number (when using an external db) - ## - port: 5432 - ## @param externalDatabase.user Non-root PostgreSQL username (when using an external db) - ## - user: bn_discourse - ## @param externalDatabase.password Password for the above username (when using an external db) - ## - password: "" - ## @param externalDatabase.create PostgreSQL create user/database - ## If true it will add POSTGRESQL_CLIENT_* env vars to the deployment which will create the PostgreSQL user & database using the provided admin credentials - ## - create: true - ## @param externalDatabase.postgresqlPostgresUser PostgreSQL admin user, used during the installation stage (when using an external db) - ## - postgresqlPostgresUser: "" - ## @param externalDatabase.postgresqlPostgresPassword PostgreSQL admin password used in the installation stage (when using an external db) - ## - postgresqlPostgresPassword: "" - ## @param externalDatabase.existingSecret Name of existing secret object - ## The secret should contain the following keys: - ## postgresql-postgres-password (for root user) - ## postgresql-password (for the unprivileged user) - ## - existingSecret: "" - ## @param externalDatabase.database Name of the existing database (when using an external db) - ## - database: bitnami_application - -## @section Redis™ parameters - -## Redis™ chart configuration -## https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml -## -redis: - ## @param redis.enabled Whether to deploy a redis server to satisfy the applications requirements. To use an external redis instance set this to false and configure the externalRedis parameters - ## - enabled: true - ## Use password authentication - ## @param redis.auth.enabled Use password authentication - ## @param redis.auth.password Redis™ password (both master and replica) - ## @param redis.auth.existingSecret Name of an existing Kubernetes secret object containing the password - ## @param redis.auth.existingSecretPasswordKey Name of the key pointing to the password in your Kubernetes secret - ## - auth: - enabled: false - ## Defaults to a random 10-character alphanumeric string if not set and auth.enabled is true. - ## It should always be set using the password value or in the existingSecret to avoid issues - ## with Discourse. - ## The password value is ignored if existingSecret is set - password: "" - existingSecret: "" - existingSecretPasswordKey: 'redis-password' - ## @param redis.architecture Cluster settings - ## - architecture: standalone - ## Redis™ Master parameters - ## @param redis.master.persistence.enabled Enable database persistence using PVC - ## - master: - persistence: - enabled: true -## External Redis™ -## @param externalRedis.host Host of the external database -## @param externalRedis.port Database port number -## @param externalRedis.password Password for the external Redis. Ignored if existingSecret is set -## @param externalRedis.existingSecret Name of an existing Kubernetes secret object containing the password -## @param externalRedis.existingSecretPasswordKey Name of the key pointing to the password in your Kubernetes secret -## -externalRedis: - host: "" - port: 6379 - password: "" - existingSecret: "" - existingSecretPasswordKey: 'redis-password'