v1.0.0-alpha.5

The backend is a set of Kubernetes API extensions written in Go that is accessible via the API calls, kubectl, and, frontend. It gets the benefit of client-go and Go packages for talking to the Kubernetes cluster of EdgeNet and makes use of the Amazon Route 53 API. In addition to these, Kubernetes custom controller called nodelabeler lists and watches the nodes of the cluster to detect add & edit node operations, and then attaches geolabels on them by using GeoLite2. Then Kubernetes custom controller called selectivedeployment gives you the opportunity to do so based on continent, country, state/region, and city, as well as on polygons that you describe using latitudes and longitudes. Briefly other essential custom resources; tenant to make authorizations to use EdgeNet handed out hierarchically, so that local administrators approve local users who they know, user who does actions that correspond to the collaborator role under its authority, subnamespace to establish hierarchical namespaces, tenantresourcequota to assign a quota to a tenant that encompasses all subnamespaces of that tenant, slice to form a subcluster isolated from multitenant workloads, nodecontribution to allow providers to make their nodes join, and vpnpeer to maintain a VPN in the cluster to access nodes behind NATs.

This backend works with the Console and the landing app, which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.

v1.0.0-alpha.4

The backend is a set of Kubernetes API extensions written in Go that is accessible via the API calls, kubectl, and, frontend. It gets the benefit of client-go and Go packages for talking to the Kubernetes cluster of EdgeNet and makes use of the Amazon Route 53 API. In addition to these, Kubernetes custom controller called nodelabeler lists and watches the nodes of the cluster to detect add & edit node operations, and then attaches geolabels on them by using GeoLite2. Then Kubernetes custom controller called selectivedeployment gives you the opportunity to do so based on continent, country, state/region, and city, as well as on polygons that you describe using latitudes and longitudes. Briefly other essential custom resources; tenant to make authorizations to use EdgeNet handed out hierarchically, so that local administrators approve local users who they know, user who does actions that correspond to the collaborator role under its authority, subnamespace to establish hierarchical namespaces, tenantresourcequota to assign a quota to a tenant that encompasses all subnamespaces of that tenant, slice to form a subcluster isolated from multitenant workloads, nodecontribution to allow providers to make their nodes join, and vpnpeer to maintain a VPN in the cluster to access nodes behind NATs.

This backend works with the Console and the landing app, which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.

v1.0.0-alpha.3

The backend is a set of Kubernetes API extensions written in Go that is accessible via the API calls, kubectl, and, frontend. It gets the benefit of client-go and Go packages for talking to the Kubernetes cluster of EdgeNet and makes use of the Amazon Route 53 API. In addition to these, Kubernetes custom controller called nodelabeler lists and watches the nodes of the cluster to detect add & edit node operations, and then attaches geolabels on them by using GeoLite2. Then Kubernetes custom controller called selectivedeployment gives you the opportunity to do so based on continent, country, state/region, and city, as well as on polygons that you describe using latitudes and longitudes. Briefly other essential custom resources; tenant to make authorizations to use EdgeNet handed out hierarchically, so that local administrators approve local users who they know, user who does actions that correspond to the collaborator role under its authority, subnamespace to establish hierarchical namespaces, tenantresourcequota to assign a quota to a tenant that encompasses all subnamespaces of that tenant, slice to form a subcluster isolated from multitenant workloads, nodecontribution to allow providers to make their nodes join, and vpnpeer to maintain a VPN in the cluster to access nodes behind NATs.

This backend works with the Console and the landing app, which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.

v1.0.0-alpha.2

The backend is a set of Kubernetes API extensions written in Go that is accessible via the API calls, kubectl, and, frontend. It gets the benefit of client-go and Go packages for talking to the Kubernetes cluster of EdgeNet and makes use of the Amazon Route 53 API. In addition to these, Kubernetes custom controller called nodelabeler lists and watches the nodes of the cluster to detect add & edit node operations, and then attaches geolabels on them by using GeoLite2. Then Kubernetes custom controller called selectivedeployment gives you the opportunity to do so based on continent, country, state/region, and city, as well as on polygons that you describe using latitudes and longitudes. Briefly other essential custom resources; tenant to make authorizations to use EdgeNet handed out hierarchically, so that local administrators approve local users who they know, user who does actions that correspond to the collaborator role under its authority, subnamespace to establish hierarchical namespaces, tenantresourcequota to assign a quota to a tenant that encompasses all subnamespaces of that tenant, slice to form a subcluster isolated from multitenant workloads, nodecontribution to allow providers to make their nodes join, and vpnpeer to maintain a VPN in the cluster to access nodes behind NATs.

This backend works with the Console and the landing app, which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.

v1.0.0-alpha.1

The backend is a Kubernetes API extension written in Go that is accessible via the API calls, kubectl, and, frontend. For various routes in its app, it gets the benefit of client-go and Go packages for talking to the Kubernetes cluster of EdgeNet and makes use of the Namecheap API. In addition to these, Kubernetes custom controller called nodelabeler lists and watches the nodes of the cluster to detect add & edit node operations, and then attaches geolabels on them by using GeoLite2. Then Kubernetes custom controller called selectivedeployment gives you the opportunity to do so based on continent, country, state/region, and city, as well as on polygons that you describe using latitudes and longitudes. Briefly other essential custom resources; authority to make authorizations to use EdgeNet handed out hierarchically, so that local administrators approve local users who they know, user who does actions that correspond to the user role under its authority, slice to allocate resources into namespaces that are workspaces for users, and team brings users together to give them the right to create slices freely. The API documentation which describes the main functionalities of the head node is created by Postman.

This backend works with the Console which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.

v1.0.0-alpha.0

The back end is an app written in Go that is only accessible via the front end. For various routes in its app, it gets the benefit of client-go and Go packages for talking to the Kubernetes cluster of EdgeNet and makes use of the Namecheap API. Addition to these, Kubernetes custom controller called nodelabeler lists and watches the nodes of the cluster to detect add & edit node operations, and then attaches geolabels on them by using GeoLite2. Then Kubernetes custom controller called selectivedeployment gives you the opportunity to do so based on continent, country, state/region, and city, as well as on polygons that you describe using latitudes and longitudes. The API documentation which describes the main functionallities of the head node is created by Postman.

This backend works with the Portal which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.

v0.9.0

The backend is a Flask app that is only accessible by the frontend. For various routes in its app, it calls down into shell scripts that interface with kubectl, the Kubernetes control tool, to create users, list the available nodes and namespaces, and generates the actual per-user config file (including certificates) that the frontend serves.

This backend works with the Portal which is where you register for using EdgeNet, and receive the required configuration files for later accessing your personalized Kubernetes (or "K8s") dashboard to administrate your EdgeNet resources.