For Tridion Sites - The webapp fails to connect to the hosted CD microservices when running from a Kubernetes container

Article Number:000017400 | Last Updated:6/11/2024 4:02 PM

Scope/Environment

Tridion Sites (Kubernetes) but not product version specific

Symptoms/Context

When a webapp is hosted from a Kubernetes container, the below error message is recorded in the cd_core.log file of the Deployer service.

WARN  c.s.d.t.p.ApiClientAuthentication - Unable to initialize Token Provider.
com.sdl.odata.client.api.exception.ODataClientRuntimeException: Unable to call OData service for "https://HOSTNAME/discovery.svc" URL 
and service query "/TokenServiceCapabilities
...
WARN c.s.w.c.c.c.i.BaseClientConfigurationLoader - Unable to resolve ContentServiceCapability using DiscoveryService: https://HOSTNAME/discovery.svc.
com.sdl.odata.client.api.exception.ODataClientRuntimeException: Unable to call OData service for "https://HOSTNAME/discovery.svc" URL 
and service query "/TokenServiceCapabilities"

Resolution

Possible solutions:

Issue resolved after whitelisting of the Kubernetes container IP range.
Check that the Discovery service endpoint is correctly configured for each service within all environments.

Root Cause

Reference

Send Article Feedback