Skip to content
This repository has been archived by the owner on Feb 15, 2023. It is now read-only.

Orchestrator Shutting Down #22

Open
0xcadams opened this issue Feb 6, 2023 · 0 comments
Open

Orchestrator Shutting Down #22

0xcadams opened this issue Feb 6, 2023 · 0 comments
Assignees
Labels
oip Orchestrator Improvement Proposal

Comments

@0xcadams
Copy link
Owner

0xcadams commented Feb 6, 2023

An update for delegators:

We regret to inform the community that Open Orchestrator will be shutting down due to financial conditions and unsustainable infrastructure costs. This was a difficult decision to make and we are deeply sorry for the inconvenience it may cause.

We have been a part of the Orchestrator community for nearly eight months and we have enjoyed every moment. We understand that this news may come as a surprise to our delegators, and we want to thank you for your loyalty and support.

Since our service will no longer be available, we recommend that you find an alternative orchestrator(s) to meet your needs. We apologize for any disruption this announcement may cause and we wish you the best of luck in finding a suitable replacement.

The source code will remain available indefinitely for anyone looking to spin up a cluster with Kubernetes. We will be spinning down operations on Feb 13, 2023.

Thank you for your understanding.

@0xcadams 0xcadams added the oip Orchestrator Improvement Proposal label Feb 6, 2023
@0xcadams 0xcadams self-assigned this Feb 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
oip Orchestrator Improvement Proposal
Projects
None yet
Development

No branches or pull requests

1 participant