Giving my 2 cents here; I would make two changes to the Helm chart:

A provide support for ingress as requested.

With the following values in the values.yaml file, you can have complete control over it's configuration:

## Ingress configuration.
  # ref: https://kubernetes.io/docs/concepts/services-networking/ingress/
  ingress:
    # -- Enable an ingress resource
    enabled: false
    # -- Additional ingress annotations
    annotations: {}
    # -- Additional ingress labels
    labels: {}
    # -- Defines which ingress controller will implement the resource
    ingressClassName: ""

    # -- List of ingress hosts
    ## Hostnames must be provided if Ingress is enabled.
    ## Secrets must be manually created in the namespace
    hosts: []
      # - argoworkflows.example.com

    # -- List of ingress paths
    paths:
      - /

    # -- Ingress path type. One of `Exact`, `Prefix` or `ImplementationSpecific`
    pathType: Prefix
    # -- Additional ingress paths
    extraPaths: []
      # - path: /*
      #   backend:
      #     serviceName: ssl-redirect
      #     servicePort: use-annotation
      ## for Kubernetes >=1.19 (when "networking.k8s.io/v1" is used)
      # - path: /*
      #   pathType: Prefix
      #   backend:
      #     service
      #       name: ssl-redirect
      #       port:
      #         name: use-annotation

    # -- Ingress TLS configuration
    tls: []
      # - secretName: parseable-example-tls
      #   hosts:
      #     - parseable.example.com

Using Argo Workflows for ref.

B ensure SSO can be enabled as well

For this to work, we need to be able to add env vars from a configmap and secret, this can be done by adding the following block to the statefulset:

envFrom:
- configMapRef:
    name: parseable-config
- secretRef:
    name: parseable-secret

You could re-use the parseable secret for the storage (e.g. S3) configuration here and make the configmap optional (e.g. only add the block when it is non-empty).

If you want, I can make a PR with those changes to make the suggestion more concrete?

Sunbelt Computer Software

PL/B Language Development and Support

Uh oh!

Uh oh!

feat: ingress helm chart #1444

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions