Skip to content

fix: Don't crash on Secret/ConfigMap names with more than 63 charaters #443

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.

Sign up for GitHub

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

Open
sbernauer wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: Don't crash on Secret/ConfigMap names with more than 63 charaters #443

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d07d9b6
test: Use long Secret name
sbernauer Aug 5, 2026
5cc4357
fix: Don't crash on Secret/ConfigMap names with more than 63 charaters
sbernauer Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,14 @@ All notable changes to this project will be documented in this file.

- Bump stackable-operator to 0.114.0 ([#439]).

### Fixed

- Support ConfigMaps and Secrets with names longer than 63 characters. Previously the restarter put
the object name into the name part of an annotation key, which Kubernetes limits to 63 characters,
causing it to reject the entire StatefulSet ([#443]).

[#439]: https://github.com/stackabletech/commons-operator/pull/439
[#443]: https://github.com/stackabletech/commons-operator/pull/443

## [26.7.0] - 2026-07-21

Expand Down
Loading
Loading