Complete Configurations
Below you'll find all the available configurations for webup, with the relative default values.
# Default values for webup.
# This is a YAML-formatted file.
# @ignored -- Global configurations
global:
# -- Telemetry Configurations
telemetry:
# -- Enable Telemetry
enabled: true
imagePullSecrets:
- name: aws-ecr-regcred
nameOverride: ""
fullnameOverride: ""
webup:
# -- Install webup
enabled: true
# -- Number of webup replicas
replicaCount: 1
# @ignored -- Image settings
image:
# @ignored -- Remote image repository
repository: 100076361442.dkr.ecr.eu-south-1.amazonaws.com/webup
# -- Image tag
tag: "1.20.13"
# -- Webup application configurations
# @default -- See `values.yaml`
cfg:
# -- The application context
context: WebUP
# -- Developer Mode Password, enabled by pressing CTRL + Shift + F8
# It's highly recommended to set a custom password
# @default -- Random alphanumeric password
devModePassword:
# -- Internal Services configuration
# @default -- Map everything as INTERNAL_SERVICE
internalServices:
JA_00_05: INTERNAL_SERVICE
JA_00_20: INTERNAL_SERVICE
JA_00_27: INTERNAL_SERVICE
JA_00_32: INTERNAL_SERVICE
JA_00_44: INTERNAL_SERVICE
JA_00_55: INTERNAL_SERVICE
# @ignored -- JVM configurations
jvm:
Xmx: 4g
Xms: 4g
MetaspaceSize: 256m
MaxMetaspaceSize: 2g
rejectClientInitiatedRenegotiation: "true"
classloadingDelegate: "false"
GC: G1
# @ignored -- Payara configurations
payara:
stringDuplication: true
disableExplicitGC: true
autodeployEnabled: false
dynamicReload: false
poolResizeQuantity: 2
maxPoolSize: 128
steadyPoolSize: 10
minThreadPoolSize: 150
maxThreadPoolSize: 500
httpListener1Enabled: true
httpListener2Enabled: false
httpMaxConnections: 500
httpTimeoutSeconds: 60
httpFileCacheMaxAgeSeconds: 3600
httpFileCacheEnabled: true
acceptorThreads: 16
httpThreadPoolMinThreadPoolSize: 25
httpThreadPoolMaxThreadPoolSize: 50
loggingGFFileHandlerLogtoFile: true
loggingGFFileHandlerRotationLimitInBytes: "5000000"
loggingGFFileHandlerMaxHistoryFiles: 10
hazelcastEnabled: false
hazelcastDynamic: true
httpMaxFormPostSizeBytes: -1
httpXpoweredBy: false
httpSchemeMapping: X-Forwarded-Proto
dumpIfOutOfMemory: false
jfr: false
# -- volumes and persistence configs
# @default -- See `values.yaml`
persistence:
# leave blank to use cluster default storageClass
# two most used values are "local-path" for local-path-provisioner on k3s and "efs-sc" for EFS on EKS
storageClassName:
# storage size for webup PVC
# with k3s local storage and AWS EFS this value is not an actual limit, so it can be left as is
size: 1Gi
accessModes:
# access mode for the volume
# "ReadWriteOnce" works only on single node clusters
# "ReadWriteMany" works only on multi-node clusters - an appropriate storageClassName must be configured and used (i.e. efs-sc)
- ReadWriteOnce
# -- Define webup SMB shares
# to add a share, remove '[]' and follow the example
shares: []
# ALWAYS use different names for your shares!
# - name: share1
# device: 172.16.2.19/smeup
# user: user1
# password: pwd1
# domain: domain1
# alias: [custom.domain/smeup]
# additionalMountParams: []
# - name: share2
# device: 10.250.0.10/test
# user: user2
# password: pwd2
# domain: domain2
# alias: []
# -- Ingress configurations
# @default -- See `values.yaml`
ingress:
# -- Enable ingress
enabled: true
# -- (string) Ingress Class Name, leave empty to use the default Ingress for this cluster
className:
# -- Annotations for ingress
# @default -- Traefik compatible HTTPS annotations
annotations:
traefik.ingress.kubernetes.io/router.entrypoints: websecure
traefik.ingress.kubernetes.io/router.tls: "true"
# -- Redirect the root url (/) to the configured context.
# NOTE 1: make sure you don't have any other application listening on the root context, or issues will arise.
# NOTE 2: works best when an ssl.hostname is configured, so the root redirect is specific to that hostname only.
rootContextRedirect: false
# -- SSL configurations
# @default -- HTTPS redirect, no hostname routing
ssl:
# -- (string) The hostname DNS used for routing and for TLS
# Note: leave empty if you're using self-signed certificates
hostname:
# -- Redirect HTTP to HTTPS traffic
# Note: only works with Traefik ingress
redirectHttps: true
# @ignored -- Webup service configurations
service:
type: ClusterIP
port: 80
annotations:
# -- EXAMPLE AWS SPECIFIC ANNOTATIONS --
# -- IF YOU CHANGE THESE CONFIGURATIONS AFTER THE FIRST APPLY YOU WILL NEED TO DELETE THE LOADBALANCER SVC AND RECREATE IT --
# service.beta.kubernetes.io/aws-load-balancer-type: nlb
# service.beta.kubernetes.io/aws-load-balancer-ssl-cert: <Replace this with your certificate ARN>
# service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
# service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443,3500"
# service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
# @ignored -- Startup probe configurations
# due to Payara's slow startup, we allow up to 5 minutes of boot time before webup is ready
# 5 minutes is: failureThreshold * (periodSeconds + timeoutSeconds) + initialDelaySeconds
startupProbe:
enabled: true
# @ignored HTTP path. Leave empty to use /{{ .Values.webup.cfg.context }}/
path:
port: application
initialDelaySeconds: 0
periodSeconds: 10
timeoutSeconds: 10
successThreshold: 1
failureThreshold: 15
# @ignored -- Liveness probe configurations
livenessProbe:
enabled: true
# @ignored HTTP path. Leave empty to use /{{ .Values.webup.cfg.context }}/
path:
port: application
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 6
# @ignored -- Readiness probe configurations
readinessProbe:
enabled: false
# @ignored http path - leave empty to use /{{ .Values.webup.cfg.context }}/
path:
port: application
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 3
# @ignored Custom Deployment Annotations
customDeploymentAnnotations:
instrumentation.opentelemetry.io/inject-java: "true"
# @ignored -- Pod security context
podSecurityContext:
fsGroup: 1000
runAsUser: 1000
runAsGroup: 1000
# -- Compute resource limits and requests
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# 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:'.
# limits:
# cpu: 2000m
# memory: 8Gi
# requests:
# cpu: 1000m
# memory: 4Gi
h53:
# -- Install h53
enabled: false
# -- Number of h53 replicas
replicaCount: 1
# @ignored -- Image settings
image:
# -- Remote image repository
repository: 100076361442.dkr.ecr.eu-south-1.amazonaws.com/h53
# -- Image tag
tag: "1.1.0"
# -- h53 application configurations
# @default -- See `values.yaml`
cfg:
logLevel: INFO
payara:
Xms: 1g
Xmx: 2g
httpThreadPoolMinThreadPoolSize: 25
httpThreadPoolMaxThreadPoolSize: 50
# -- Define h53 SMB shares
# Note 1: you must use the same 'name' parameter as the ones used under 'webup.shares[]'
# Note 2: use 'overrideMountPath' if you want to specify a custom mountpath, otherwise '/mnt/$name' is used
shares: []
# - name: share1
# - name: share2
# overrideMountPath: /my-custom-path
# @ignored -- Pod security context
podSecurityContext:
fsGroup: 1000
runAsUser: 1000
runAsGroup: 1000
# @ignored -- h53 service configurations
service:
type: ClusterIP
port: 80
# @ignored -- Startup probe configurations
# due to Payara's slow startup, we allow up to 3 minutes of boot time before h53 is ready
# 3 minutes is: failureThreshold * (periodSeconds + timeoutSeconds) + initialDelaySeconds
startupProbe:
enabled: true
path: /h53/swagger.yml
port: application
initialDelaySeconds: 0
periodSeconds: 10
timeoutSeconds: 10
successThreshold: 1
failureThreshold: 9
# @ignored -- Liveness probe configurations
livenessProbe:
enabled: true
path: /h53/swagger.yml
port: application
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 6
# @ignored Readiness probe configurations
readinessProbe:
enabled: false
path: /h53/swagger.yml
port: application
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 3
# -- Compute resource limits and requests
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# 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:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
as400proxy:
# -- Install as400-proxy
enabled: true
# -- Number of as400-proxy replicas
replicaCount: 1
# @ignored -- Image settings
image:
# -- Remote image repository
repository: 100076361442.dkr.ecr.eu-south-1.amazonaws.com/as400-proxy
# -- Image tag
tag: "1.0.7"
# -- as400-proxy application configurations
# @default -- See `values.yaml`
cfg:
# -- (string) IBM i DNS
server: ""
# -- (string) Service user used for IBM i connection
user: ""
# -- (string) Service user's password
password: ""
# -- (string) Secret used to sign JWT auth tokens
secret: ""
# -- Auth token duration
# Note: MUST be between quotes (i.e. "1337", not 1337)
# Do NOT use a number bigger than 2147483647 (the max value for Java Integer) or as400-proxy boot will fail.
# As a best practice, it's best to leave this as is.
tokenDuration: "52560000"
# -- Use SSL connection towards IBM i
# Note: it is highly discouraged to set this to "false" in production environments
sslConnection: "true"
# -- Allow self signed ssl connection towards IBM i
sslSelfSignedAllowed: "false"
# -- SSL Certificates used to connect to IBM i
certs: []
#- name: my-custom-certificate
# b64: <BASE64-CERTIFICATE>
# @ignored -- Payara server configs
payara:
Xms: 1g
Xmx: 2g
httpThreadPoolMinThreadPoolSize: 25
httpThreadPoolMaxThreadPoolSize: 50
# -- as400-proxy logging configuration
# @default -- INFO log level
logback:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{70} - %msg %n</pattern>
</encoder>
</appender>
<appender name="EVENT_ROLLING_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${varRoot}/log/as400-proxy-event.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
<!-- rollover daily -->
<fileNamePattern>${varRoot}/log/as400-proxy-event-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
<!-- each file should be at most 50MB, keep 5 days worth of history, but at most 1GB -->
<maxFileSize>50MB</maxFileSize>
<maxHistory>5</maxHistory>
<totalSizeCap>1GB</totalSizeCap>
</rollingPolicy>
<encoder class="net.logstash.logback.encoder.LogstashEncoder">
</encoder>
</appender>
<root level="INFO">
<appender-ref ref="STDOUT" />
</root>
<logger name="com.smeup.as400.proxy.event.EventLog" level="INFO">
<appender-ref ref="EVENT_ROLLING_FILE" />
</logger>
</configuration>
# -- Ingress configurations
# @default -- See `values.yaml`
ingress:
# -- Enable ingress
enabled: false
# -- (string) Ingress Class Name, leave empty to use the default Ingress for this cluster
className:
# -- Annotations for ingress
# @default -- Traefik compatible HTTPS annotations
annotations:
traefik.ingress.kubernetes.io/router.entrypoints: websecure
traefik.ingress.kubernetes.io/router.tls: "true"
# -- Redirect the root url (/) to the configured context.
# NOTE 1: make sure you don't have any other application listening on the root context, or issues will arise.
# NOTE 2: works best when an ssl.hostname is configured, so the root redirect is specific to that hostname only.
rootContextRedirect: false
# -- SSL configurations
# @default -- HTTPS redirect, no hostname routing
ssl:
# -- (string) The hostname DNS used for routing and for TLS
# Note: leave empty if you're using self-signed certificates
hostname:
# -- Redirect HTTP to HTTPS traffic
# Note: only works with Traefik ingress
redirectHttps: true
# @ignored -- Pod security context
podSecurityContext:
fsGroup: 1000
runAsUser: 1000
runAsGroup: 1000
# @ignored -- as400-proxy service configurations
service:
type: ClusterIP
port: 80
# @ignored -- Startup probe configurations
# due to Payara's slow startup, we allow up to 3 minutes of boot time before as400-proxy is ready
# 3 minutes is: failureThreshold * (periodSeconds + timeoutSeconds) + initialDelaySeconds
startupProbe:
enabled: true
path: /as400-proxy/openapi.yaml
port: application
initialDelaySeconds: 0
periodSeconds: 10
timeoutSeconds: 10
successThreshold: 1
failureThreshold: 9
# @ignored -- Liveness probe configurations
livenessProbe:
enabled: true
path: /as400-proxy/openapi.yaml
port: application
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 6
# @ignored -- Readiness probe configurations
readinessProbe:
# turn off readiness probe by default since we run 1 replica only
enabled: false
path: /as400-proxy/openapi.yaml
port: application
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 3
# -- Compute resource limits and requests
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# 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:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi