Skip to content

Enable automatic OIDC integration for created kubernetes cluster #604

Closed

Description

@c42-konstantin

Description

When users create a kubernetes cluster they often want to have a seamless single sign-on (SSO) using the same OIDC provider used by platform (CozyStack) itself. Something like it's done in hyperscalers.
Currently kubernetes clusters require additional configuration to use platform keycloak (or other IDP) provider for authentication.

Proposed solution

Add an (optional) parameter to the 'kind: Kubernetes' spec, that allows user to specify authentication configuration of the kubernetes cluster that is going to be created. So that if cozystack has been configured with OIDC enabled a user can select this parameter as 'platform-oidc' (or something like this), if not - user can specify any another IDP that is compatible with kubernets or don't specify anything.

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature
    on Jan 23, 2025
  2. kvaps commented on Feb 6, 2025

    @kvaps
    Member

    Totally makes sense, we'll consider the implementation.

  3. kvaps commented on Feb 6, 2025

    @kvaps
    Member
  4. changed the title [-]Feature request: enable automatic OIDC integration for creaetd kubernetes cluster[/-] [+]Enable automatic OIDC integration for created kubernetes cluster[/+] on Apr 3, 2025
  5. dosubot commented on Oct 19, 2025

    @dosubot

    Hi, c42-konstantin. I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You proposed adding an optional parameter for automatic OIDC integration during Kubernetes cluster creation to enable seamless SSO.
    • The maintainer, kvaps, responded positively and is considering the implementation.
    • Implementation would require adding extra --oidc-* options to the KamajiControlPlane resource.
    • Relevant code references were shared to guide the potential development.
    • The issue remains unresolved with no recent updates.

    Next Steps:

    • Please let me know if this feature is still relevant to the latest version of the cozystack repository by commenting on this issue.
    • If I do not hear back within 7 days, the issue will be automatically closed.

    Thank you for your understanding and contribution!

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 19, 2025
  7. kvaps commented on Oct 20, 2025

    @kvaps
    Member

    This is still on a row

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 20, 2025
  9. added
    area/kubernetesIssues or PRs related to the tenant Kubernetes app
    area/keycloakIssues or PRs related to Keycloak (SSO / identity)
    triage/not-reproducibleIndicates an issue can not be reproduced as described
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Sep 23, 2026
  10. lexfrei commented on Sep 23, 2026

    @lexfrei
    Contributor

    Landed in #3044: the Kubernetes app has spec.oidc.mode (System or CustomConfig) and spec.oidc.users. The guide is docs/oidc-tenant.md.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/keycloakIssues or PRs related to Keycloak (SSO / identity)area/kubernetesIssues or PRs related to the tenant Kubernetes appkind/featureCategorizes issue or PR as related to a new featurelifecycle/frozenIndicates that an issue or PR should not be auto-closed due to stalenesstriage/not-reproducibleIndicates an issue can not be reproduced as described

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions