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] - e2e test for Cluster Bootstrap #291

Open
Tracked by #538
IvoGoman opened this issue Jun 11, 2024 · 0 comments
Open
Tracked by #538

[FEAT] - e2e test for Cluster Bootstrap #291

IvoGoman opened this issue Jun 11, 2024 · 0 comments
Assignees
Labels
backlog Issues that are part of the backlog core Part of the Greenhouse Core Backlog feature
Milestone

Comments

@IvoGoman
Copy link
Contributor

IvoGoman commented Jun 11, 2024

Priority

(Medium) I'm annoyed but I'll live

Description

This test ensures that:

  • remote cluster can be onboarded
    • differentiate on USE_EXISTING_CLUSTER:
      • false: spin Up "remote" envtest controlplane to test against as in this example
      • true: test against remote cluster specified by kubeconfig located at TEST_REMOTE_KUBECONFIG
        • Testrunner can decide wether to run against local KIND or existing cluster
  • cluster status is reconciled, see status_controller.go
    • Namely: kubeConfigValidCondition, allNodesReadyCondition, readyCondition,
  • expected resources are present on the remote cluster, mainly see direct_access_controller.go
    • Cluster resource present on central Greenhouse Cluster
    • Namespace in remote Cluster
    • SA in remote Cluster
    • ClusterRoleBinding for SA in remote Cluster
    • ServiceAccountToken
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Issues that are part of the backlog core Part of the Greenhouse Core Backlog feature
Projects
Status: Sprint Backlog
Status: Backlog
Development

No branches or pull requests

2 participants