farhoodlabs/devcontainer
8
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

Chart v0.4.8 fails deployment: port name "sequentialthinking" exceeds 15 character limit #48

New Issue
Closed
opened 2026-02-24 01:08:33 +00:00 by cpfarhood · 1 comment
cpfarhood commented 2026-02-24 01:08:33 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Problem

Devcontainer chart v0.4.8 fails to deploy due to Kubernetes port name validation error.

Error Details

Deployment.apps "devcontainer-devcontainer" is invalid: spec.template.spec.containers[4].ports[0].name: Invalid value: "sequentialthinking": must be no more than 15 characters

Root Cause

The port name "sequentialthinking" (18 characters) exceeds Kubernetes' maximum port name length of 15 characters.

Impact

  • Helm upgrade from v0.4.5 → v0.4.8 fails
  • HelmRelease becomes stuck in failed status
  • GitOps reconciliation cannot proceed

Environment

  • Kubernetes: K3s cluster
  • Helm: via Flux CD v2
  • Previous working version: v0.4.5

Expected Fix

Port name should be shortened to ≤15 characters, e.g.:

  • "seqthinking" (11 chars)
  • "sequential" (10 chars)
  • "seq-thinking" (12 chars)

Workaround

Rolling back to v0.4.7 or v0.4.5 until fixed.

## Problem Devcontainer chart v0.4.8 fails to deploy due to Kubernetes port name validation error. ## Error Details ``` Deployment.apps "devcontainer-devcontainer" is invalid: spec.template.spec.containers[4].ports[0].name: Invalid value: "sequentialthinking": must be no more than 15 characters ``` ## Root Cause The port name `"sequentialthinking"` (18 characters) exceeds Kubernetes' maximum port name length of 15 characters. ## Impact - Helm upgrade from v0.4.5 → v0.4.8 fails - HelmRelease becomes stuck in `failed` status - GitOps reconciliation cannot proceed ## Environment - Kubernetes: K3s cluster - Helm: via Flux CD v2 - Previous working version: v0.4.5 ## Expected Fix Port name should be shortened to ≤15 characters, e.g.: - `"seqthinking"` (11 chars) - `"sequential"` (10 chars) - `"seq-thinking"` (12 chars) ## Workaround Rolling back to v0.4.7 or v0.4.5 until fixed.
cpfarhood commented 2026-02-24 01:09:37 +00:00 (Migrated from github.com)
Copy Link
Copy Source

@claude please fix

@claude please fix
👀 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
antigravity
architecture
automation
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 examples
good first issue
Good for newcomers
 helm
help wanted
Extra attention is needed
 invalid
This doesn't seem right
 maintainability
monitoring
question
Further information is requested
 refactor
tooling
user-experience
validation
wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
fl_blake (Blake MIddleware) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) flux (Flux CD) admin (Gitea Admin) fl_hugh (Hugh Commit) renovate (Mend Renovate) fl_warren (Warren Bufferpool)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: farhoodlabs/devcontainer#48
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?