Skip to content

Add configurable default theme support#4384

Open
guillaumebernard84 wants to merge 9 commits intokubernetes-sigs:mainfrom
guillaumebernard84:default-theme
Open

Add configurable default theme support#4384
guillaumebernard84 wants to merge 9 commits intokubernetes-sigs:mainfrom
guillaumebernard84:default-theme

Conversation

@guillaumebernard84
Copy link
Contributor

Summary

This PR adds runtime configuration for default themes via command-line arguments, addressing the feedback from #4307

Related Issue

Addresses feedback from #4307

Changes

Adds three new CLI flags:
--default-light-theme - Default theme when OS prefers light mode
--default-dark-theme - Default theme when OS prefers dark mode
--force-theme - Force specific theme (overrides user preference)

Also available as environment variables: HEADLAMP_CONFIG_DEFAULT_LIGHT_THEME, HEADLAMP_CONFIG_DEFAULT_DARK_THEME, HEADLAMP_CONFIG_FORCE_THEME

When a theme is forced, the theme selection menu is greyed out, and "Theme has been forced by your administrator" is displayed. I localized it to French as I'm a native French speaker.

Steps to Test

  • use a browser in private browsing mode or clean your prefered theme from localstorage: run delete localStorage.headlampThemePreference from your browser JS console
  • use the command line arguments to set a default or force a theme, for example --force-theme="Headlamp Classic"

I also added unit tests:

  • Backend tests: go test ./pkg/config -run TestParseThemeConfiguration
  • Frontend tests: npm test -- themes.test.ts

Signed-off-by: Guillaume BERNARD <guillaume.bernard@live.fr>
Signed-off-by: Guillaume BERNARD <guillaume.bernard@live.fr>
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 18, 2026
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 18, 2026
@guillaumebernard84
Copy link
Contributor Author

Hello @sniok, here is the new PR addressing your feedback from #4307

@joaquimrocha
Copy link
Contributor

Hi @guillaumebernard84 . I think this falls in the category of distributed settings that we'd like to have soon. See #3979 .
I see the logic for having a CLI arg for settings like the theme, but I think we should have this as a general "app-settings" arg, which we can pass a json file with different settings. This could include also plugin settings I mention in the issue pasted above.

@sniok , WDYT?

Copy link
Contributor

@skoeva skoeva left a comment

Choose a reason for hiding this comment

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

I see some errors in the CI, could you run these commands locally to try to fix those?

  • make frontend-test
  • make backend-lint-fix

Signed-off-by: Guillaume BERNARD <guillaume.bernard@live.fr>
@guillaumebernard84
Copy link
Contributor Author

Three fixes applied:

  • Go Linter: Refactored large table-driven test into 9 separate test functions to satisfy 60-line limit and split long lines.
  • Frontend Test: Settings.tsx UI changes altered MUI CSS classes. Ran npm test -- src/storybook.test.tsx -u to update snapshot.
  • TypeDoc Build: Exported applyBackendThemeConfig and ensureValidThemeName actions from themeSlice.ts so TypeDoc can resolve action types (was accessing via themeSlice.actions.* without explicit exports).

@guillaumebernard84
Copy link
Contributor Author

Hi @guillaumebernard84 . I think this falls in the category of distributed settings that we'd like to have soon. See #3979 . I see the logic for having a CLI arg for settings like the theme, but I think we should have this as a general "app-settings" arg, which we can pass a json file with different settings. This could include also plugin settings I mention in the issue pasted above.

@sniok , WDYT?

Yes, this could be an good solution too. I'll comment in #3979

@guillaumebernard84
Copy link
Contributor Author

/retest

@k8s-ci-robot
Copy link
Contributor

@guillaumebernard84: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

@guillaumebernard84
Copy link
Contributor Author

/honk

@k8s-ci-robot
Copy link
Contributor

@guillaumebernard84:
goose image

Details

In response to this:

/honk

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.

@guillaumebernard84
Copy link
Contributor Author

Hello @skoeva, can you please rerun the tests? Thanks

IsDynamicClusterEnabled bool `json:"isDynamicClusterEnabled"`
DefaultLightTheme string `json:"defaultLightTheme,omitempty"`
DefaultDarkTheme string `json:"defaultDarkTheme,omitempty"`
ForceTheme string `json:"forceTheme,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't this be a boolean? so that default light/dark theme can be forced

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know, it could.
It felt more natural for me to set --force-theme corporate-light instead of --default-light-theme corporate-light --force-theme
But that's a matter of taste. I can change that if you want.

Copy link
Contributor

Choose a reason for hiding this comment

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

it's not a matter of taste. for accessibility reasons there should be an option to force dark or light theme depending on the user preference

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok. What behaviour do you want?

  • What should happen to users with dark theme preferences when ran with --default-light-theme corporate-light --force-theme ?
  • Wouldn't it be easier to have two options --force-light-theme and --force-dark-theme as strings?

@illume
Copy link
Contributor

illume commented Feb 1, 2026

TIL /honk lol :)

@illume illume added this to the v0.40.0 milestone Feb 1, 2026
Copy link
Contributor

@illume illume left a comment

Choose a reason for hiding this comment

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

Thanks for this.

There's a GitHub check failing.

Can you please check the issue out locally?

npm run backend:lint
npm run backend:format
npm run backend:test

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds runtime configuration for default themes via command-line arguments and environment variables, addressing feedback from PR #4307. The implementation allows administrators to configure default themes based on OS preference and to force a specific theme, overriding user preferences.

Changes:

  • Adds three new CLI flags and corresponding environment variables for theme configuration (--default-light-theme, --default-dark-theme, --force-theme)
  • Implements backend configuration parsing and API endpoints to pass theme configuration to the frontend
  • Updates frontend theme selection logic to respect backend configuration with proper precedence order
  • Adds UI indication and disables theme selection when a theme is forced by an administrator
  • Includes comprehensive test coverage for both backend and frontend changes

Reviewed changes

Copilot reviewed 26 out of 26 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
backend/pkg/config/config.go Adds theme configuration flags and struct fields
backend/pkg/config/config_theme_test.go Comprehensive backend tests for theme configuration parsing
backend/pkg/headlampconfig/headlampConfig.go Extends HeadlampCFG with theme configuration fields
backend/cmd/server.go Maps theme config from Config to HeadlampCFG
backend/cmd/headlamp.go Updates clientConfig struct to include theme fields and getConfig endpoint
backend/cmd/stateless.go Updates parseKubeConfig to include theme configuration
frontend/src/redux/configSlice.ts Adds theme configuration to Redux state
frontend/src/lib/themes.ts Implements theme precedence logic with backend configuration support
frontend/src/lib/themes.test.ts Comprehensive frontend tests for theme selection logic
frontend/src/components/App/themeSlice.ts Adds applyBackendThemeConfig action and exports ensureValidThemeName
frontend/src/components/App/Layout.tsx Applies backend theme config when fetched from backend
frontend/src/plugin/index.ts Reapplies backend theme config after plugins load
frontend/src/components/App/Settings/Settings.tsx Disables theme selection UI and shows forced theme message
frontend/src/i18n/locales/*/translation.json Adds localization for forced theme message
frontend/src/components/App/Settings/snapshots/Settings.General.stories.storyshot Updates snapshot for UI styling changes

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

guillaumebernard84 and others added 3 commits February 1, 2026 21:15
Ok, this makes sense

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Guillaume BERNARD <guillaume.bernard@live.fr>
Ok, this copilot suggestion makes sense

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Guillaume BERNARD <guillaume.bernard@live.fr>
@guillaumebernard84
Copy link
Contributor Author

Hello @illume, I fixed the backend linter error, and accepted the two changes from the copilot review. It seems the third one from copilot encountered an error. Do you want to rerun it? I passed the frontend linter and tests after accepting the changes, it works.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 26 out of 26 changed files in this pull request and generated 4 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Contributor

@illume illume left a comment

Choose a reason for hiding this comment

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

🎉 thanks!

(I won't merge yet, but will wait for other people to review/test)

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guillaumebernard84, illume

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2026
@illume
Copy link
Contributor

illume commented Feb 3, 2026

@guillaumebernard84 Sorry, there's some git conflicts now. Would you mind having a look?

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2026
Signed-off-by: Guillaume BERNARD <guillaume.bernard@live.fr>
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2026
@guillaumebernard84
Copy link
Contributor Author

I fixed the git conflicts, I'll try to fix the build errors

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 3, 2026
@illume illume modified the milestones: v0.40.0, v0.41.0 Feb 4, 2026
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 13, 2026
@k8s-ci-robot
Copy link
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

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants