Skip to content

Overriding baseDomain in wc-config generates faulty user kubeconfigs #1723

@anders-elastisys

Description

@anders-elastisys

Describe the bug:

When overriding baseDomain in wc-config.yaml, the kubeconfig generated for users does not work.

To Reproduce:

Steps to reproduce the behaviour:

  1. Override global.baseDomain in wc-config.yaml to something else than what is found in sc-config.yaml/common-config.yaml
  2. Run ./bin/ck8s kubeconfig user wc
  3. Try and use the user kubeconfig and see that it fails as the oidc-issuer-url is not pointing to dex in sc

Expected behaviour:

Would prefer that the generated user kubeconfig uses the baseDomain of dex in sc.

Version (add all relevant versions):

  • Compliant Kubernetes apps version v0.30.3 (but the config looks the same in newer versions of apps as well)

Additional context:

It is this configuration.

Metadata

Metadata

Assignees

Labels

kind/bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions