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

fix(statefulsets): port name not included in headless service (#3077) #3990

Merged
merged 1 commit into from
Apr 7, 2024

Conversation

cdk8s-automation
Copy link
Contributor

Backport

This will backport the following commits from k8s-28/main to k8s-26/main:

Questions ?

Please refer to the Backport tool documentation

If you have two different containers in a Stateful Set that both require port access Kubernetes (v.1.27) will fail with the following error:

```bash
The Service "SERVICE_NAME" is invalid:
* spec.ports[0].name: Required value
* spec.ports[1].name: Required value
```

This is because during creation of the headless service the name of the ports is not passed. This will also happen if you have a container with multiple ports.

(cherry picked from commit 46a7cb7)
Signed-off-by: Robert Koch <[email protected]>
@cdk8s-automation cdk8s-automation added the auto-approve Pull requests that should be auto approved label Apr 7, 2024
@mergify mergify bot merged commit 7b07bd0 into k8s-26/main Apr 7, 2024
16 checks passed
@cdk8s-automation
Copy link
Contributor Author

⚪ Backport skipped

The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.

Manual backport

To create the backport manually run:

backport --pr 3990

Questions ?

Please refer to the Backport tool documentation

@mergify mergify bot deleted the backport/k8s-26/main/pr-3077 branch April 7, 2024 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-approve Pull requests that should be auto approved
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants