ArcGIS Enterprise on Kubernetes Web Adaptor

ArcGIS Enterprise on Kubernetes Web Adaptor enables web-tier authentication using your organization's security policies and can also be used as a load balancer for your ArcGIS Enterprise organization.

Installation types

There are three ArcGIS Enterprise on Kubernetes Web Adaptor installations; one for IIS and two for Java. To get started, determine which installation is needed in your organization.

ArcGIS Enterprise on Kubernetes Web Adaptor (IIS)

You can install ArcGIS Enterprise on Kubernetes Web Adaptor (IIS) on a Windows machine with an IIS web server.

ArcGIS Enterprise on Kubernetes Web Adaptor (Java)

ArcGIS Enterprise on Kubernetes Web Adaptor (Java) can be installed on a Windows or Linux machine with a Java application server.

Installation behavior and requirements

ArcGIS Enterprise on Kubernetes Web Adaptor is installed on a separate machine outside the ArcGIS Enterprise on Kubernetes cluster. Before installing ArcGIS Enterprise on Kubernetes Web Adaptor, keep the following in mind:

  • If you are upgrading from an earlier version and have configured a reverse proxy with your organization, you must stop the reverse proxy before configuring ArcGIS Web Adaptor with your upgraded organization.
  • Verify that your system meets the minimum system requirements.
  • Verify your organization's fully qualified domain name (FQDN) and context path, for example, https://organization.example.com:31443/context/.
    Note:
    The FQDN and context path were specified during deployment.
  • When specifying the ArcGIS Web Adaptor context, it must match the context path specified during deployment.
  • ArcGIS Web Adaptor must be installed on a machine that has the same FQDN as your organization (organization.example.com in the example above).
  • At this release, ArcGIS Web Adaptor is only supported on default ports, for example, ports 80 (HTTP) and 443 (HTTPS).
  • After ArcGIS Web Adaptor and IWA or PKI are configured, administrators may use the FQDN, context path, and port to access ArcGIS Enterprise Manager and ArcGIS Enterprise portal, for example, https://organization.example.com:31443/context/.
    Note:

    When accessing apps or administrative endpoints as mentioned above, the context path does not change.