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

Clarification about amount of possible seeds with CE #1120

Closed
almereyda opened this issue Jul 29, 2022 · 6 comments
Closed

Clarification about amount of possible seeds with CE #1120

almereyda opened this issue Jul 29, 2022 · 6 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale.
Milestone

Comments

@almereyda
Copy link
Contributor

This statement in the documentation for the v2.20 Kubermatic release implies, that there can be only one seed resource within the CE.

The Seed resource itself needs to be called `kubermatic` (for the Community Edition) and needs to reference the new
kubeconfig Secret like so:

This is due to the fact that a specific name can only be assigned once.

The overview of the installation instruction speaks about clusters in the plural before:

The setup procedure for seed clusters happens in multiple stages:

This might imply that it is possible to add more than one seed cluster. The architecture document and the images within it also suggests this.

Am I correct in concluding that the CE only allows a single seed cluster?

@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2022
@kubermatic-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubermatic-bot kubermatic-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 2, 2022
@kubermatic-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubermatic-bot
Copy link
Contributor

@kubermatic-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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/test-infra repository.

@embik
Copy link
Member

embik commented Jan 19, 2023

Hey @almereyda, sorry this got closed due to inactivity. We added a note to the top of https://docs.kubermatic.com/kubermatic/main/installation/install-kkp-ce/add-seed-cluster-ce/ that mentions this more clearly. Does that fulfil your request adequately?

@almereyda
Copy link
Contributor Author

Yes, many thanks! That seems to be precise enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale.
Projects
None yet
Development

No branches or pull requests

4 participants