Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/redis] Ability to rename redis service port name #25228

Closed
arianf opened this issue Apr 18, 2024 · 3 comments · Fixed by #25579
Closed

[bitnami/redis] Ability to rename redis service port name #25228

arianf opened this issue Apr 18, 2024 · 3 comments · Fixed by #25579
Assignees
Labels
feature-request redis solved stale 15 days without activity triage Triage is needed

Comments

@arianf
Copy link

arianf commented Apr 18, 2024

Name and Version

bitnami/redis latest

What is the problem this feature will solve?

Our internal kube cluster has an odd requirement, it requires all service ports.name to match the ports.targetPort, I've filed something internally to hopefully get this constraint fixed (but due to the complexity of fixing it, it may take a lot of time, or never be resolved).

name: tcp-redis
targetPort: redis

ports:
- name: tcp-redis
port: {{ .Values.master.service.ports.redis }}
targetPort: redis
{{- if and (or (eq .Values.master.service.type "NodePort") (eq .Values.master.service.type "LoadBalancer")) .Values.master.service.nodePorts.redis}}
nodePort: {{ .Values.master.service.nodePorts.redis}}
{{- else if eq .Values.master.service.type "ClusterIP" }}
nodePort: null
{{- end }}
{{- if .Values.master.service.extraPorts }}
{{- include "common.tplvalues.render" (dict "value" .Values.master.service.extraPorts "context" $) | nindent 4 }}
{{- end }}

What is the feature you are proposing to solve the problem?

It would be awesome, if ports.name or ports.targetPort name could also be configurable

What alternatives have you considered?

I've tried using .Values.master.service.extraPorts to add a port with matching name

service:
  extraPorts:
    - name: redis
      port: 6379
      protocol: TCP
      targetPort: redis

but that results with a duplicate key since the default config and the extraPorts config are using the same ports

spec.ports[1]: Duplicate value: core.ServicePort{Name:"", Protocol:"TCP", AppProtocol:(*string)(nil), Port:6379, TargetPort:intstr.IntOrString{Type:0, IntVal:0, StrVal:""}, NodePort:0}
@github-actions github-actions bot added the triage Triage is needed label Apr 18, 2024
@javsalgar javsalgar changed the title Ability to rename redis service port name [bitnami/redis] Ability to rename redis service port name Apr 19, 2024
@javsalgar
Copy link
Contributor

Hi!

Thank you so much for reporting the issue. Would you like to submit a PR adding a value for the service name?

Copy link

github-actions bot commented May 5, 2024

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label May 5, 2024
cwgthornton added a commit to cwgthornton/charts that referenced this issue May 7, 2024
Addresses bitnami#25228

Signed-off-by: Chris Thornton <cwgthornton@gmail.com>
cwgthornton added a commit to cwgthornton/charts that referenced this issue May 7, 2024
Addresses bitnami#25228

Signed-off-by: Chris Thornton <cwgthornton@gmail.com>
cwgthornton added a commit to cwgthornton/charts that referenced this issue May 7, 2024
Addresses bitnami#25228

Signed-off-by: Chris Thornton <cwgthornton@gmail.com>
cwgthornton added a commit to cwgthornton/charts that referenced this issue May 8, 2024
Addresses bitnami#25228

Signed-off-by: Chris Thornton <cwgthornton@gmail.com>
dgomezleon pushed a commit that referenced this issue May 9, 2024
)

Addresses #25228

Signed-off-by: Chris Thornton <cwgthornton@gmail.com>
@github-actions github-actions bot added the solved label May 9, 2024
@arianf
Copy link
Author

arianf commented Jun 3, 2024

Thank you @cwgthornton for submitting a fix for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request redis solved stale 15 days without activity triage Triage is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants