Skip to main content

There are specific IFS Connect Routing Rules set up that allow Kubernetes to determine if the service is ready.

Should these rules be deleted or amended then the IFS Connect container will not start and therefore the application will be unavailable.

Always make sure that an Inbound Routing Rule with the name ‘READINESS_PROBE’ is available in the environment in questions. If it is available then make sure that it is Enabled as well.

An enhancement request has been created to make sure routing rules of this type are read only in future.

Hi @cditchburn  ,

Any good probes that we could use to communicate to the outside world (from on-prem) that all is up and well without login?

Our client wishes to use Netscaler to monitor IFS Cloud and alert if anything stops responding.
(https://docs.netscaler.com/en-us/citrix-adc/current-release/load-balancing/load-balancing-configure-monitors)

Reply


Terms & ConditionsCookie settings