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

Give the Service default port (5984) a name so that it is not ambiguous if service.extraPorts is used. #156

Merged
merged 1 commit into from
Jun 4, 2024

Conversation

samwho
Copy link
Contributor

@samwho samwho commented Jun 4, 2024

What this PR does / why we need it:

Sorry about this @willholley, but I noticed when trying to update to 4.5.4 and use my new extraPorts values that if you try to have multiple ports on a Service in Kubernetes, all ports need a name (kubernetes/kubernetes#36803). If there's just one port, this name property is optional. Sadly this renders service.extraPorts useless in 4.5.4, so for 4.5.5 I've given the default port a name.

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.

  • Chart Version bumped
  • e2e tests pass
  • Variables are documented in the README.md (no new variables)
  • NEWS.md updated

@samwho
Copy link
Contributor Author

samwho commented Jun 4, 2024

Thank you so much for reviewing these PRs so quickly, we really appreciate it 🙏

@willholley willholley merged commit b6d55fc into apache:main Jun 4, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants