Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] - Cluster supports StructuredAuth for access #878

Open
2 tasks
IvoGoman opened this issue Feb 4, 2025 · 0 comments
Open
2 tasks

[FEAT] - Cluster supports StructuredAuth for access #878

IvoGoman opened this issue Feb 4, 2025 · 0 comments
Assignees
Labels

Comments

@IvoGoman
Copy link
Contributor

IvoGoman commented Feb 4, 2025

Priority

None

User Story

As a Cluster administrator, I would like to be able to choose the Cluster auth method, so that I can decide how greenhouse accesses my cluster.

Description

Currently, Greenhouse manages a ServiceAccount on the remote cluster and automatically rotates the token. In case of prolonged downtime of either Greenhouse central, Remote cluster or longer connectivity issues, this token may expire. Once a token is expired it cannot be remediated by Greenhouse but requires manual intervention.

The Cluster CRD needs a field to specify which authentication method is used.
The controllers need to get the kube client used for reconciliation from the Cluster resource.

Acceptance Criteria

  • Cluster CRD allows to specify which auth method to use
  • Controllers get KubeClient from Cluster

Reference Issues

No response

@IvoGoman IvoGoman changed the title [FEAT] - Cluster allows ServiceAccount as another [FEAT] - Cluster supports StructuredAuth for access Feb 4, 2025
@github-project-automation github-project-automation bot moved this to Sprint Backlog in Greenhouse Core Roadmap Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Sprint Backlog
Development

No branches or pull requests

2 participants