Before deploying ArcGIS Enterprise on Kubernetes, identify the URL that will be used to represent your ArcGIS Enterprise organization and enable client access to it. This single URL provides access to multiple resources such as apps, administrative tools, and APIs and defines how responses are formed to client requests.
The ArcGIS Enterprise organization is accessed by a single URL that is composed of a scheme, host, and context, as shown below.
The terms in the example above are defined as follows:
- Scheme—Communicates to the requester or browser to access the organization's URL over HTTPS
- Host—Describes the fully qualified domain name (FQDN) or Domain Name System (DNS) alias for the organization
- Context—Refers to the name an administrator provides when installing the ArcGIS Web Adaptor component
Network flow
The organization URL includes the FQDN used to direct client traffic to an ArcGIS Enterprise organization. The FQDN is resolved via a DNS record to an edge load balancer that routes traffic back to the bundled ingress controller. Between those two network hops, additional load balancers, Web Adaptors, or ingress controllers can exist and affect the network flow. However, once the request reaches the bundled ingress controller, a set of managed and namespaced ingress objects is used to direct requests to the correct backend microservice.
If you are using a layer 7 load balancer at any point in the network path, you must set the X-Forwarded-Host header to match the FQDN of the organization for proper routing of the proxied requests and ensure they persist all the way back to the bundled ingress controller.
