Skip to content

adminer: ingress.servicePort is ignored when rendering Ingress backend #131

Description

@attilaolah

Summary

In the adminer chart, setting ingress.servicePort to a named service port does not affect the rendered Ingress backend. The chart still renders the backend service port as http.

Chart Version

adminer chart 1.1.0

Reproduction

Render the chart with an additional service port and configure the Ingress to use it:

service:
  extraPorts:
    - name: oauth-proxy
      port: 8443
      targetPort: 8443
      appProtocol: https

ingress:
  enabled: true
  hostname: example.com
  path: /adminer/(.*)
  pathType: ImplementationSpecific
  servicePort: oauth-proxy

Run:

helm template adminer startechnica/adminer --version 1.1.0 --values values.yaml

Expected Result

The rendered Ingress backend should use the configured port:

backend:
  service:
    name: adminer
    port:
      name: oauth-proxy

Actual Result

The rendered Ingress backend uses http instead:

backend:
  service:
    name: adminer
    port:
      name: http

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions