Configuring the ingress controller service

You must have a Kubernetes ingress controller to deploy Sitecore Kubernetes specification files. The ingress controller acts as a reverse proxy between the browser and the Sitecore software containers.

To support client IP address tracking and personalization, you must configure the ingress controller to preserve the client source IP address in the X-Forwarded-For HTTP header.

To preserve the client source IP address, set the ingress controller externalTrafficPolicy setting to Local. For more information, see the Kubernetes documentation and the NGINX Ingress Controller Configuration documentation.

You must explicitly enable use of a proxy server in your Sitecore Configuration. For more information about setting up a proxy server, see the Sitecore Experience Platform Set up Sitecore IP Geolocation page.

To change this configuration for use in Kubernetes, We recommend that you build a new container image that contains this configuration change for both the Content Management and Content Delivery roles.

For more information about building new container images with configuration changes, see the Sitecore Docker Examples repository on GitHub.