Skip to content

Migrate aggregated APIService TLS from hardcoded Secret to cert-manager#447

Open
alexandernorth wants to merge 3 commits into
mainfrom
feature/cert-manager-supported-certs
Open

Migrate aggregated APIService TLS from hardcoded Secret to cert-manager#447
alexandernorth wants to merge 3 commits into
mainfrom
feature/cert-manager-supported-certs

Conversation

@alexandernorth
Copy link
Copy Markdown
Contributor

Replaces #76.

Summary

Replace the hardcoded api-server-cert Secret with a cert-manager-issued cert chain following the SelfSigned bootstrapping pattern. Removes insecureSkipTLSVerify: true on the APIService. caBundle is now populated by cainjector from the CA Certificate.

Chain: selfsigned-cluster-issuer -> sdc-ca (CA) -> sdc-ca-issuer -> api-server-cert (mounted by the api-server Deployment, same Secret name as before).

Prerequisites

  • cert-manager installed (tested with v1.20.2) with cainjector Ready.
  • See artifacts/certmanager/install.md.

@alexandernorth alexandernorth requested a review from a team as a code owner May 19, 2026 15:33
@github-project-automation github-project-automation Bot moved this to Backlog in SDC project May 19, 2026
@alexandernorth alexandernorth moved this from Backlog to In review in SDC project May 19, 2026
@@ -1 +1,33 @@
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.16.2/cert-manager.yaml No newline at end of file
# cert-manager
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

do we still need this file? the install docs shows cert-manager clearly as a prereq.
The scripts there do also wait for cert-manager to become ready.

I do howver agree that we need to document the trust chain down there somewhere. Docs repo?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I will add it to the docs, but I don't see the harm in having it here too, or is the goal of this section something else?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I have added it to the docs with this PR sdcio/docs#141

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

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

2 participants