You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2022. It is now read-only.
Right now, we have the Datacenter model which stores information about the datacenter's provider, currently it can be AWS or GCP. We should also add support for holding information about platform used (e.g. Rancher, GKE/Kubernetes, etc.).
We could either add a simple field Datacenter.platform which would hold this information, but this information doesn't really belong to Datacenter. And also, it's not always THAT simple - in some environments, you can run Rancher+Kubernetes, in others you could run Rancher 1.6 which does not use kubernetes. You can also run your service without any orchestrator.
But still, this kind of matadata should be stored somewhere.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, we have the
Datacenter
model which stores information about the datacenter's provider, currently it can beAWS
orGCP
. We should also add support for holding information about platform used (e.g. Rancher, GKE/Kubernetes, etc.).We could either add a simple field
Datacenter.platform
which would hold this information, but this information doesn't really belong toDatacenter
. And also, it's not always THAT simple - in some environments, you can run Rancher+Kubernetes, in others you could run Rancher 1.6 which does not use kubernetes. You can also run your service without any orchestrator.But still, this kind of matadata should be stored somewhere.
The text was updated successfully, but these errors were encountered: