The Cloud Native Computing Foundation<\/a> , which encourages cloud portability without vendor lock-in, supports the Kubernetes project. It is possible to deploy Kubernetes clusters on bare metal, public cloud, and private cloud environments.<\/p>\n However, setting up a Kubernetes cluster from scratch on your own servers is complex. It calls for a thorough comprehension of the cluster’s constituent parts, their interconnections, and the ability to monitor and troubleshoot. For a detailed guide, refer to the Kubernetes The Hard Way<\/a> article.<\/p>\n Managed Kubernetes services simplify and automate many operations, but the challenge of right-sizing<\/a> still remains. You need to be quite exact in estimating the number of worker nodes and the containers that operate on them in order to maximize efficiency. Otherwise, you risk paying for large, underutilized workers or using small VMs and relying on automatic horizontal scaling, which can add complexity.<\/p>\n AccuWeb.Cloud has addressed several challenges and provided essential features to simplify Kubernetes hosting<\/a>\u00a0 while optimizing resource consumption:<\/p>\n AccuWeb.Cloud PaaS provides a Kubernetes cluster with the following pre-installed components:<\/p>\n Step 1.<\/strong> To begin, log in to the dashboard, locate the Kubernetes Cluster in the Marketplace, and click Install. This clustering solution is only accessible to billing clients; learn more about trial limits.<\/p>\n Step 2.<\/strong> Next, select the required cluster topology. Two options are available:<\/p>\n Step 3.<\/strong> Attach dedicated NFS Storage<\/strong> with dynamic volume provisioning.<\/p>\n Every node has a read-write filesystem with read-write permissions by default. However, for access from other containers or persistence after redeployments, data should be placed on a dedicated volume.<\/p>\n You can use a custom dynamic volume provisioner by specifying the required settings in your deployment YAML files.<\/p>\n Alternatively, you can use the pre-configured volume manager and NFS Storage built into the AccuWeb.Cloud Kubernetes cluster. As a result, physical volumes will be provisioned dynamically on demand and connected to the containers. The Storage Node can be accessed and managed using the file manager via the dashboard, SFTP, or any NFS client.<\/p>\n Step 4.<\/strong> If needed, you can install additional software to monitor and troubleshoot your Kubernetes (K8s) cluster, and enable API access using the provided checkboxes:<\/p>\n If you choose not to install these now, you can add them later using the specific Cluster Configuration<\/strong> add-on.<\/p>\n Step 5.<\/strong> To showcase all the package features and details, we will install the Open Liberty application server runtime in a Production<\/strong> Kubernetes cluster topology with built-in NFS storage.<\/strong><\/p>\n Click the Install<\/strong> button and wait a few minutes. Once the installation is complete, the cluster topology will look as follows:<\/p>\n Step 6.<\/strong> You can access the Kubernetes administration dashboard and the Open Liberty application server welcome page from the successful installation window.<\/p>\n Use the Access Token<\/strong> and follow the Kubernetes dashboard link to manage your Kubernetes cluster.<\/p>\n Access the default Kubernetes page by pressing the Open in Browser<\/strong> button.<\/p>\n AccuWeb.Cloud K8s package includes specific add-ons available at the master node, designed to:<\/p>\n which are designed to:<\/p>\n First, attach a public IP to one of the worker nodes.<\/p>\n Create an A record for your external domain (e.g., SSLservice.accu.website<\/strong>) using the public IP.<\/p>\n Enter this domain name in the Certificate Manager user interface and press Apply.<\/p>\n This tool not only manages SSL certificates but also deploys a separate ingress controller to balance workloads among applications tied to the workers’ public IPs. Consequently, all internal resources become accessible via worker nodes’ hostnames like node${nodeId}-${envName}.${platformDomain},<\/strong> except for the worker node using the public IP bound to the external domain (e.g., myservice.jele.website) through the Certificate Manager.<\/p>\n After installation, you’ll receive an email and a pop-up with access credentials.<\/p>\n Similarly, after installation, an email and a pop-up with access credentials will be sent.<\/p>\n To remotely access and manage your created Kubernetes cluster using the API, select the Enable Remote API Access checkbox.<\/strong><\/p>\n Use the provided Remote API Endpoint<\/strong> link and access Token<\/strong> to connect to the Kubernetes API server (Balancer or Master node).<\/p>\n The best way to interact with the API server is through the Kubernetes command line tool, kubectl:<\/strong><\/p>\n Now, you can manage your Kubernetes cluster from your local computer by following the official tutorial. To disable or enable the API service after installation, use the Master node Configuration Add-On.<\/p>\n To keep your Kubernetes cluster software up-to-date, use the Cluster Upgrade Add-On.<\/strong> Simply click the Start Cluster Upgrade<\/strong> button.<\/p>\n The add-on will check if a new version is available, and if so, it will install the update. During the upgrade, all nodes, including masters and workers, will be redeployed to the new version one by one, while preserving all existing data and settings.<\/p>\n Note that the upgrade process is sequential, so if your current version is significantly outdated, you may need to run the upgrade multiple times to reach the latest version. The upgrade option becomes available only when a new version is globally released by the AccuWeb.Cloud team.<\/p>\n To avoid application downtime during the redeployment, consider using multiple replicas for your services.<\/p>\n AccuWeb.Cloud provides automatic vertical scaling for each worker and master node in a Kubernetes cluster, allocating resources on demand based on real-time load. This means you don\u2019t need to constantly monitor changes, as the system does it for you.<\/p>\n Additionally, you can easily check the current load across a group of nodes or each node individually by pressing the Statistics<\/strong> button next to the desired layer or node.<\/p>\n This highly automated scaling and full containerization enable AccuWeb.Cloud PaaS offers a billing model that is relatively new to cloud computing. This “pay-per-use” or “pay-as-you-use” approach is considered the most cost-effective, as you only pay for the resources you actually use. This model eliminates the need to over allocate resources, solving the “right-sizing” problem inherent in the older “pay-per-limits” or “pay-as-you-go” models.<\/p>\n The billing process is transparent and can be tracked through the dashboard under Balance > Billing History.<\/strong> The price is based on the number of consumed resource units, called cloudlets (128MiB + 400MHz). This granularity provides flexibility in billing and clarity in cloud expenditures.<\/p>\n\n
![\"Jelastix](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/kubernetes-cluster-768x813-new.jpg\" "\\"Jelastix")
<\/a><\/p>\n\n
Kubernetes Cluster Installation<\/h2>\n
![\"Kubernetes](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-02.jpg\" "\\"Kubernetes")
<\/a><\/p>\n\n
![\"Select](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-03.jpg\" "\\"Select")
<\/a><\/p>\n![\"NFS](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-04.jpg\" "\\"NFS")
<\/a><\/p>\n\n
![\"Enable](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-05.jpg\" "\\"Enable")
<\/a><\/p>\n![\"Open](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-06.jpg\" "\\"Open")
<\/a><\/p>\n![\"Access](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-07.jpg\" "\\"Access")
<\/a><\/p>\n![\"Token\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-26.png\" "\\"Token\\"")
<\/a><\/p>\n![\"Kubernetes](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-08.jpg\" "\\"Kubernetes")
<\/a><\/p>\n![\"Open](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-09.jpg\" "\\"Open")
<\/a><\/p>\n![\"Result](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-10.jpg\" "\\"Result")
<\/a><\/p>\nAccuWeb.Cloud Kubernetes Distribution Add-Ons<\/h2>\n
![\"Add-Ons\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-11.jpg\" "\\"Add-Ons\\"")
<\/a><\/p>\nInstall SSL Certificate Manager:<\/h3>\n
![\"Install](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-12.jpg\" "\\"Install")
<\/a><\/p>\n\n
![\"Remote](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-13.jpg\" "\\"Remote")
<\/a><\/p>\n\n
\n
![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-14.jpg\")
<\/a><\/p>\n![\"Credentials](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-15.jpg\" "\\"Credentials")
<\/a><\/p>\n\n
![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-16.jpg\")
<\/a><\/p>\n![\"Access](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-17.jpg\" "\\"Access")
<\/a><\/p>\nRemote API Access to Kubernetes Cluster<\/h2>\n
![\"Remote](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-18.jpg\" "\\"Remote")
<\/a><\/p>\n![\"Remote](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-19.jpg\" "\\"Remote")
<\/a><\/p>\n\n
\r\n$ kubectl config set-cluster mycluster --server={API_URL}\r\n$ kubectl config set-context mycluster --cluster=mycluster\r\n$ kubectl config set-credentials user --token={TOKEN}\r\n$ kubectl config set-context mycluster --user=user\r\n$ kubectl config use-context mycluster\r\nWhere:\r\n{API_URL} - Remote API Endpoint link\r\n{TOKEN} - Access Token<\/code><\/pre>\n
\nFor instance, to view all available nodes in your cluster, open a local terminal and run the following kubectl command:<\/p>\n\r\nkubectl get nodes<\/code><\/pre>\n![\"Manage](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-20.jpg\" "\\"Manage")
<\/a><\/p>\n![\"Remote](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-21.jpg\" "\\"Remote")
<\/a><\/p>\n![\"Enable](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-22.jpg\" "\\"Enable")
<\/a><\/p>\nCluster Upgrade<\/h2>\n
![\"Start](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-23.jpg\" "\\"Start")
<\/a><\/p>\nStatistics and Pay-per-Use Billing<\/h2>\n
![\"Statistics\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-24.jpg\" "\\"Statistics\\"")
<\/a><\/p>\n
![\"Billing](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/Kubernetes-Cluster-Setup-25.jpg\" "\\"Billing")
<\/a><\/p>\n