Private zones allow you to add managed infrastructure to your Napptive account, so you can create environment and deploy applications in your own infrastructure. The infrastructure will be used by the Napptive Playground for the purpose of deploying applications, but we will not ask you for your cloud provider credentials. You will be still in control of your cloud provider details.
If you are interested in using your own infrastructure with the Napptive Playground contact us, so we can guide you through the installation.
To setup your private zone, you will need to provide a Kubernetes cluster with the following characteristics:
- A Kubernetes cluster v1.22+
- The Napptive Playground is compatible with all major Kubernetes distributions, including: EKS, GKE, AKS, and RKE(2).
- The cluster will need 2 public load balancers: application ingresses, and Napptive services. The load balancers need to be reachable from the Napptive Playground service, so it is possible to restrict incoming traffic to a set of allowed IPs.
- Adding two entries to your DNS
- Certificates or compatibility with cert-manager to issue loadbalancer certificates.
- An ingress controller such as Nginx to route deployed application requests
The setup of the Napptive Zone will create a napptive namespace that contains all required elements.
Once the base system is installed, you will be assisted by Napptive engineers with the installation process, so that the zone is associated to your account and selectable to create new environments.
Private zone support quota restrictions that allow you to limit the amount of resources that can be used by napptive managed environments/namespaces. Among the different parameters supported you will be able to restrict:
- Number of available CPU
- Maximum RAM Memory
- Maximum ephemeral and persistent storage
As the owner of a private zone, you will be able to tailor the security and restrictions for the deployed applications to better reflect company policies and requirements.