Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-21339

K8S helm chart templates containing names with static ports

    XMLWordPrintable

Details

    • Documentation task
    • Status: Confirmed
    • Major
    • Resolution: Unresolved
    • 6.0.6, 6.2.0
    • None
    • Installation (I), Proxy (P)
    • None
    • Kubernetes

    Description

      Hello,

      we found out, that some names in helm chart templates contain static values with hardcoded port number. E.g.:

            containers:
              - name: zabbix-proxy
                image: "{{ .Values.zabbixProxy.image.repository }}:{{ .Values.zabbixProxy.image.tag }}"
                imagePullPolicy: {{ .Values.zabbixProxy.image.pullPolicy }}
                ports:
                  - containerPort: {{ .Values.zabbixProxy.service.port }}
                    protocol: TCP
                    name: 10051-tcp
        ports:
          - name: 10051-tcp
            port: {{ .Values.zabbixProxy.service.port }}
            protocol: TCP
            targetPort: {{ .Values.zabbixProxy.service.targetPort }}

      Impact:

      It has no impact on functionality, but live configurations in K8S are bit confusing then (from self-documentation perspective).

      Expected:

      Dynamic names depending on current port settings, or maybe better not including port numbers at all.

      Attachments

        Activity

          People

            zit Zabbix Integration Team
            rico Richard Ostrochovský
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: