Trial Account Limitations: Kubernetes Cluster
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Trial Account Limitations: Kubernetes Cluster on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
PackageKubernetes Clusterby Ruk-Com supports the possibility to install intrial accountsHere, certain limitations apply to such installations due to:limitationsof account type
1. Normally, demo accounts may not be able to install production topology and will receive appropriate warnings.
2. In case thebuilt-in SSLis disabled, an additional warning will be displayed during installation and access to the Kubernetes will be provided viaendpoint(instead of theingress).
2. In case of deactivationbuilt-in SSLAdditional warnings will be displayed during installation and access to Kubernetes will be done throughendpoint(instead ofingress)
3. Remote API connections still have limitations - command-line utilities (e.g.kubectl) The remote cluster cannot be accessed using HTTP links this way. Kubernetes Dashboard and kubectl from the master node are the only options to interact with the K8s cluster.