Please contact the security team at email@example.com for questions not covered in the documentation.
This section captures details about the SaaS Controller that customers can use to optionally whitelist inbound (emails) and outbound (control channel destinations) in their enterprise's firewalls and proxies.
A 3rd Party service is used for emails sent by the SaaS Controller (i.e. for first time user activation, password resets, notifications etc). To guarantee delivery of emails from the SaaS Controller to users in the customer org, we strongly recommend that customers "whitelist" the IP address used for sending emails in their inbound email security systems.
The dedicated IP address currently used for sending emails from the Controller is "126.96.36.199"
The SaaS Controller has been specially designed so that customers can deploy and manage their clusters in both Internet (public IP) and on-premises (private IP) type environments.
|Internet Facing, Public IP|
|Non Internet Facing, Private IP|
To onboard an on-premise or cloud-based cluster onto the Controller for ongoing operations and lifecycle management
- A “Kubernetes Operator” is installed on each managed cluster.
- This establishes and maintains a "long-running" outbound TLS based control channel to the Controller (hosted in Amazon Web Services (AWS) for SaaS).
- No Inbound Ports need to be opened on the customer's external firewall for control plane traffic.
The Kubernetes Management Operator deployed on the customer's cluster uses only "TCP Port 443, Outbound" to communicate with the SaaS Controller.
|443/tcp||TLS with Mutual Auth||All Control Plane functionality|
SaaS Controller IP¶
Customers that wish to lock down communication further can optionally whitelist the IP addresses of the SaaS Controller in their firewalls to ensure that outbound connectivity is only allowed to these IPs.
The SaaS Controller is currently deployed in a highly available manner across three availability zones (AZ) on AWS. The three, load balanced IP Addresses for the SaaS Controller are:
|IP Address 1||188.8.131.52|
|IP Address 2||184.108.40.206|
|IP Address 3||220.127.116.11|
Managed Cluster -> Controller FQDNs¶
The Kubernetes Management Operator components (deployed on managed clusters) will make outbound connections over port 443 to the Controller on the following FQDNs. Add these to your firewall's whitelist if necessary.
End User -> Controller FQDNs¶
Add the following to your organization's firewall or proxy whitelist if end users of your Org will be on the corporate network and need to interact with the controller from their laptops/desktops. For example, developers that need to remotely perform Kubectl operations on managed clusters using the zero trust kubectl service.
ECR Registry Access¶
Users that use the controller's integration with AWS ECR (managed container registry) will need to white list the following controller IP addresses.
The ECR integration allows the users to use the SaaS Controller to "configure, update and validate" access credentials with ECR.
The System Container Registry (RCR) is available as an option for customers to manage their container images. This is based on Docker Registry v2. It uses OAuth2 for authentication (laptops etc using the RCTL CLI).
Users are automatically redirected to an OAuth service which uses the provided credentials in docker login to authenticate and authorize the request for a resource on the registry. For successful requests, a bearer token is returned, which is used to access a resource on the Container Registry.
Please ensure that the network security policies implemented either in the corporate network OR the endpoint are configured to allow outbound connections from the RCTL CLI to the Controller on the ports listed below.
|443/tcp||TLS (https)||Access the Controller Platform via REST APIs|
Please add the following ports if you wish to use the System Container Registry.
|5001/tcp||TLS (https)||OAuth Authentication Service for Hosted Container Registry|
|6000/tcp||TLS (https)||Access to Hosted Container Registry|