Skip to content

Conversation

@henderiw
Copy link
Contributor

splitting the config server:

  • apiserver
  • controller

changed namespace to sdc-system by default.

need to find a solution for dry-run and get running config/configblame

@henderiw henderiw changed the title aplit config-server in apiserver and controller split config-server in apiserver and controller Nov 28, 2025
@hansthienpondt
Copy link
Contributor

Note: integration-tests needs to be adjusted in order to make the testing pipeline succeed (namespace change, deployment changes). Perhaps we can do that once the refactor PR has been merged.

deployment also might need to be adjusted as there are 2 deployments right now.

❯ kubectl get deployment -A
NAMESPACE            NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
cert-manager         cert-manager              1/1     1            1           23h
cert-manager         cert-manager-cainjector   1/1     1            1           23h
cert-manager         cert-manager-webhook      1/1     1            1           23h
kube-system          coredns                   2/2     2            2           23h
local-path-storage   local-path-provisioner    1/1     1            1           23h
sdc-system           api-server                1/1     1            1           23h
sdc-system           controller                1/1     1            1           23h

This need to be adjusted first before we apply the 'safe to test' label.

@hansthienpondt
Copy link
Contributor

Note: integration-tests needs to be adjusted in order to make the testing pipeline succeed (namespace change, deployment changes). Perhaps we can do that once the refactor PR has been merged.

deployment also might need to be adjusted as there are 2 deployments right now.

❯ kubectl get deployment -A
NAMESPACE            NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
cert-manager         cert-manager              1/1     1            1           23h
cert-manager         cert-manager-cainjector   1/1     1            1           23h
cert-manager         cert-manager-webhook      1/1     1            1           23h
kube-system          coredns                   2/2     2            2           23h
local-path-storage   local-path-provisioner    1/1     1            1           23h
sdc-system           api-server                1/1     1            1           23h
sdc-system           controller                1/1     1            1           23h

This need to be adjusted first before we apply the 'safe to test' label.

https://github.com/sdcio/integration-tests/tree/feature/split-configserver has been prepared for this.

@steiler
Copy link
Contributor

steiler commented Dec 23, 2025

@henderiw
Can we either make the metrics port configurable or define different ports for api-server and controller.

Running in debug mode this leads to issues for me.

metricsServerOptions := metricsserver.Options{
		BindAddress:   ":8443",

@steiler steiler added the safe to test Apply this label for PRs to kick off CI integration testing label Jan 16, 2026
@henderiw henderiw moved this to Backlog in SDC project Jan 19, 2026
@henderiw henderiw added this to the MS26-04 milestone Jan 19, 2026
@henderiw henderiw linked an issue Jan 19, 2026 that may be closed by this pull request
@henderiw henderiw moved this from Backlog to In progress in SDC project Jan 19, 2026
@henderiw henderiw moved this from In progress to In review in SDC project Jan 19, 2026
@steiler steiler self-requested a review January 19, 2026 15:08
@henderiw henderiw merged commit baff676 into main Jan 19, 2026
20 of 26 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in SDC project Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test Apply this label for PRs to kick off CI integration testing

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Split Config-Server into two pieces

4 participants