Skip to content

Handle caBundleSecretRef in the shard controller#132

Merged
kcp-ci-bot merged 2 commits intokcp-dev:mainfrom
BergCyrill:hotfix/no-ref/fix-shard-cabundlesecretref
Dec 22, 2025
Merged

Handle caBundleSecretRef in the shard controller#132
kcp-ci-bot merged 2 commits intokcp-dev:mainfrom
BergCyrill:hotfix/no-ref/fix-shard-cabundlesecretref

Conversation

@BergCyrill
Copy link
Copy Markdown
Contributor

Summary

This PR adds the handling of the provided secret in the shards spec at .spec.caBundleSecretRef to the shards external logical cluster kubeconfig. This behavior is described in the CRD but is currently not implemented. This leads to issues if the externalHostname does not have the same certificate issuer as the serverCA (e.g. front-proxy with lets encrypt certificate and the rootShard & shard with self signed certificates).
The controller tests are extended to test for the correct path in the certificateAuthority property of the kubeconfig.

What Type of PR Is This?

/kind bug

Related Issue(s)

/

Release Notes

Fix usage of caBundleSecretRef in external logical cluster kubeconfig for shards resources similar to the rootShard behavior

…ClusterAdminKubeconfig

Signed-off-by: Cyrill Berg <cyrill.berg@bwi.de>
Signed-off-by: Cyrill Berg <cyrill.berg@bwi.de>
@kcp-ci-bot kcp-ci-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/bug Categorizes issue or PR as related to a bug. labels Dec 17, 2025
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

Hi @BergCyrill. 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/test-infra repository.

@kcp-ci-bot kcp-ci-bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 17, 2025
Copy link
Copy Markdown
Contributor

@mjudeikis mjudeikis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

I suspect this slipped. Thanks!!!!

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 22, 2025
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: cd274cc5158bf4b0a0398655af3a4041732ac29e

@kcp-ci-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mjudeikis

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

The pull request process is described 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 22, 2025
@kcp-ci-bot kcp-ci-bot merged commit 6378b20 into kcp-dev:main Dec 22, 2025
10 checks passed
@BergCyrill BergCyrill deleted the hotfix/no-ref/fix-shard-cabundlesecretref branch January 26, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants