[ZBX-21339] K8S helm chart templates containing names with static ports Created: 2022 Jul 14 Updated: 2023 Jun 12 Resolved: 2023 Jun 12 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Installation (I), Proxy (P) |
| Affects Version/s: | 6.0.6, 6.2.0 |
| Fix Version/s: | None |
| Type: | Documentation task | Priority: | Major |
| Reporter: | Richard Ostrochovský | Assignee: | Denis Rasikhov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
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. |
| Comments |
| Comment by Denis Rasikhov [ 2023 Jun 09 ] |
|
Updated in:
|