Skip to content

Pass imagePullSecrets from ImageSpec to Deployments#230

Open
madmecodes wants to merge 1 commit into
kcp-dev:mainfrom
madmecodes:feat/handle-imagepullsecrets
Open

Pass imagePullSecrets from ImageSpec to Deployments#230
madmecodes wants to merge 1 commit into
kcp-dev:mainfrom
madmecodes:feat/handle-imagepullsecrets

Conversation

@madmecodes
Copy link
Copy Markdown

@madmecodes madmecodes commented May 8, 2026

Summary

Propagate imagePullSecrets from ImageSpec to generated Deployments across all four deployment generators (CacheServer, Shard/RootShard, FrontProxy, VirtualWorkspace).

Previously, resources.GetImageSettings() returned imagePullSecrets but all generators discarded them by assigning to _. This fix captures and sets them on the Deployment's PodSpec.

Fixes #181

Propagate imagePullSecrets from component specs to generated Deployments

Changes

  • cacheserver/deployment.go: capture and set imagePullSecrets
  • utils/shard.go: capture and set imagePullSecrets (covers RootShard and Shard)
  • frontproxy/deployment.go: capture and set imagePullSecrets
  • virtualworkspace/deployment.go: capture and set imagePullSecrets
  • frontproxy/deployment_test.go: add test cases for imagePullSecrets propagation

@kcp-ci-bot kcp-ci-bot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label May 8, 2026
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. dco-signoff: no Indicates the PR's author has not signed the DCO. labels May 8, 2026
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

Hi @madmecodes. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kcp-ci-bot kcp-ci-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 8, 2026
Fixes kcp-dev#181

Signed-off-by: madmecodes <ayushguptadev1@gmail.com>
@madmecodes madmecodes force-pushed the feat/handle-imagepullsecrets branch from ffec4da to 1410da7 Compare May 8, 2026 11:37
@kcp-ci-bot kcp-ci-bot added dco-signoff: yes Indicates the PR's author has signed the DCO. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed dco-signoff: no Indicates the PR's author has not signed the DCO. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels May 8, 2026
@madmecodes
Copy link
Copy Markdown
Author

/kind feature

@kcp-ci-bot kcp-ci-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels May 9, 2026
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. kind/feature Categorizes issue or PR as related to a new feature. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature: Handle imagePullSecrets

2 participants