Eternet Portal Documentation
Additional Cloud Resource Pages
Kubernetes clusters
The cluster page requests Kubernetes cluster records through the Cloud API endpoint /server/GetKubernetesClusterList, with pagination parameters.
VPS, load balancing, and DevOps
These routes exist in the portal route tree. Their actual data and actions depend on their respective page components and configured Cloud API contracts. Verify each operation against the service before representing it as a working provisioning workflow; route existence alone is not proof of backend support.
Shared boundary
Cloud API calls are made server-side using the signed-in user’s access token. Failed or unavailable upstream calls are converted to empty results in the common data loader, so operational status should be considered when interpreting an empty page.
Kubernetes cluster inventory
The cluster route calls the Cloud API’s Kubernetes cluster-list operation with pagination parameters. Its purpose is to display the clusters associated with the current account so an operator can inspect the available cluster records. A returned cluster record can help identify an environment, but the portal should not infer node health, workload readiness, or successful deployment unless those details are explicitly returned and refreshed. Cluster lifecycle operations such as creating, scaling, upgrading, or deleting a cluster are separate mutations and should be verified against the actual API before being included in a customer commitment.
VPS and other infrastructure pages may provide more detailed service views, but each has a separate route and component. The existence of a URL does not demonstrate that a full backend workflow is connected. For example, a page can contain forms or product information that are not bound to a provisioning endpoint. Separate the concepts of catalog, inventory, and lifecycle control when presenting these routes: catalog helps compare options; inventory reflects returned existing resources; lifecycle controls change provider state.
How to assess readiness
Before demonstrating any cloud resource page, sign in with an account that has known resources, inspect the network response, and compare displayed identifiers and statuses with the Cloud API. Verify pagination, loading behavior, empty states, error visibility, and authorization. If the common loader converts request failures to an empty list, check logs or the direct API response through the service layer before interpreting the UI. Confirm that the current user is allowed to see only their intended resources and that no secrets or upstream credentials are returned to browser code.
For a production-grade operations workflow, resource state should carry a clear refresh time, status source, and action feedback. Destructive or disruptive actions should require confirmation and report the final authoritative state. The current text presentation does not claim that these extra operational guarantees exist; they are readiness questions to validate for each route.
Customer value
Keeping cluster, VPS, network, and storage resources under one Cloud navigation helps customers understand the infrastructure supporting their IoT and analytics workloads. It offers a starting point for reviewing what is provisioned and where it belongs. The Cloud service remains responsible for resource state and mutations, while the portal provides authenticated navigation and presentation. During a customer walkthrough, use only actions that have been tested against a safe environment and distinguish an inventory record from a running, healthy workload.