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.

Sign up for GitHub

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

Jump to bottom

Move facility from Machine to Cluster #139

Closed
gianarb opened this issue Jun 29, 2020 · 0 comments · Fixed by #140
Closed

Move facility from Machine to Cluster #139

gianarb opened this issue Jun 29, 2020 · 0 comments · Fixed by #140
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API

Comments

@gianarb
Copy link
Contributor

gianarb commented Jun 29, 2020

Right now the facility is part of the PacketMachine Spec. This has two issues:

  1. It drives you to the wrong assumption that you can easily deploy machines that are part of the same cluster in multiple facilities. This is not currently possible and very hard to achieve because it requires network configuration, security concerns, latency. Nobody in the Kubernetes community suggests for that and we should not.
  2. I am in the process of supporting multi-master Multi master #47. We requiring an IP for the cluster we have to specify the facility. The fact that it is not part of the Cluster makes the process of selecting the facility not easy, flaky.
@gianarb gianarb added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Jun 29, 2020
@gianarb gianarb mentioned this issue Jun 29, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move facility from packetmachine to packetcluster
1 participant
@gianarb