Skip to content

chore: drop the unused database migrator init container value - #2423

Open
fjvbn2003 wants to merge 1 commit into
goharbor:mainfrom
fjvbn2003:drop-unused-migrator-value
Open

fjvbn2003 wants to merge 1 commit into
goharbor:mainfrom
fjvbn2003:drop-unused-migrator-value

Conversation

@fjvbn2003

Copy link
Copy Markdown

#1714 removed the data migrator init container from the internal database StatefulSet, but values.yaml still has database.internal.initContainer.migrator and the README still documents database.internal.initContainer.migrator.resources. No template reads the value any more, so setting it has no effect.

Checked on a cluster running chart 1.19.2: the harbor-database StatefulSet has a single init container, data-permissions-ensurer (driven by database.internal.initContainer.permissions.resources). On main, grep -rn migrator templates/ only matches the component: migrator labels of the pre-upgrade Job, which is unrelated.

This removes the value (with its commented example) and the README row.

This change was drafted with AI assistance and reviewed by me.

🤖 Generated with Claude Code

The data migrator init container was removed in goharbor#1714, but values.yaml
still has database.internal.initContainer.migrator and the README still
documents its resources. No template reads the value any more, so
setting it has no effect. Remove both.

Signed-off-by: YoungjuKim <[email protected]>

This branch has not been deployed

No deployments
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.

1 participant