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

feat: port name validation RFC-6335 #2474

Merged

Conversation

leovct
Copy link
Contributor

@leovct leovct commented Jun 5, 2024

Description

Kubernetes adheres to RFC-6335, which specifies that port names must be between 1 and 15 characters. However, this constraint is currently not enforced by the Kurtosis engine, leading to deployment failures in Kubernetes environments when port names exceed 15 characters.

Here is an example that the Kurtosis validation step failed to catch:

image (1)

This PR resolves the issue by adding an additional validation step for port names. It also refactors the regex definitions in service.go and improves the test design for validating service and port names in service_test.go.

Is this change user facing?

YES

References (if applicable)

@leovct leovct marked this pull request as ready for review June 5, 2024 08:33
@tedim52 tedim52 added this pull request to the merge queue Jun 6, 2024
Merged via the queue into kurtosis-tech:main with commit ffbd30b Jun 6, 2024
50 checks passed
@leovct leovct deleted the feat/port-name-validation-rfc6335 branch June 7, 2024 07:39
github-merge-queue bot pushed a commit that referenced this pull request Jun 7, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.89.17](0.89.16...0.89.17)
(2024-06-07)


### Features

* add optional names to tasks
([#2477](#2477))
([5d7bb67](5d7bb67))
* port name validation RFC-6335
([#2474](#2474))
([ffbd30b](ffbd30b))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: kurtosisbot <[email protected]>
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