Install Payara Qube

Payara Qube is a cloud native application platform that allows you to deploy and operate Java applications in an EKS cluster. This installation script will guide you through prerequisites and collect necessary information to prepare installation package.

Installation package will be provided in form of Pulumi script that you will execute locally with appropriate AWS credentials. That script will also serve for future upgrades of the infrastrcture.

First please provide the credentials of technical account for the Nexus Repository that you have been given as part of the welcome email. These credentials are will be used to estabilish access for Qube to required installation components.

Nexus User Name (required)*

Nexus Password (required)*

Name of the installation will serve as prefix for all cloud resources that will be created in this installation. The resources entail:

• VPC
• EKS cluster
• Multiple S3 buckets
• Multiple IAM groups, roles and policies
• Cloudwatch log groups
• PogresSQL RDS instance

Installation Name (required) Base name for cloud resources. Example qube-prod*

Payara Qube will use two DNS zones that need to be accessible from public internet – one for hosting its management interfaces (control plane) and another to host deployed applications on. Additionally a custom domain may be used for specific namespace. For all domains an appropriate certificate is obtained from LetsEncrypt and renewed automatically.

Control plane domain will host manage.control-plane.domain for its main user interfaces and users.control-plane.domain for the login and user management. It is recommended that this domain is not a sibling of the application domain to prevent cookie sharing. The records will be added into existing DNS zone that needs to be present in target account.

Application domain will create new address entry project-stage-suffix.application.domain for every namespace deployed in Qube. A wildcard certificate will be obtained for this domain. A new DNS zone will be created in target account for application domain and if its parent domain is specified and present in target account, the subzone records will be created appropriately. If not specified, you will need to create appropriate NS records in the parent zone to make it available to the public.

In order to obtain LetsEncrypt certificates a contact email address needs to be provided.

Control Plane Domain (required) This domain will host management interfaces and user management.*

Control Plane DNS Zone (required) Existing DNS zone in target account which is parent of the control plane domain.*

Application Domain (required) This domain will host deployed applications.*

Application DNS Zone Existing DNS zone in target account which is parent of the application domain.

LetsEncrypt contact email (required) Email address used to obtain LetsEncrypt certificates.*

Payara Qube will use SMTP server to send invitations and facilitate user management. While it will work without SMTP server, you will need to pass invitation emails by other means, as well as set up user registration process.

SMTP From The email address that will be used as the sender of the emails sent by Payara Qube.
To specify the display name and email address, use the format: "Display Name" <emailaddress@domain.tld>

SMTP Host Hostname of the SMTP server.

SMTP Port Port of the SMTP server.

SMTP Username Username for the SMTP server.

SMTP Password Password for the SMTP server.

Payara Qube will create a new EKS cluster in the target account. The cluster will be created in a new VPC with a public and private subnets.

EKS Instance Type (required) EC2 instance type for the EKS cluster.*

EKS Minimum Cluster Size (required) Minimum number of nodes in the EKS cluster.*

EKS Maximum Cluster Size (required) Maximum number of nodes in the EKS cluster.*

This cluster will also serve as a target for provisioning the applications. This is referred to as the provisioning region in Payara Qube. Multiple provisioning regions may be defined by running different variant of installation wizard.

In same way as any provisioning region this initial one needs to have its internal id defined, and its description. It is recommended to keep the id equal to the name, and description should name the AWS region this cluster will be created in.

Provisioning Region ID (required) Unique identifier for the provisioning region.*

Provisioning Region Description (required) Description of the provisioning region.*

AWS Region ID (required) AWS region where the cluster will be created.*