APIcast currently requires loading the complete list of client certificates for all products at startup. In environments with large certificate whitelists (sometimes thousands of entries per API), this design causes slow initialization and forces administrators to adjust probes and timeouts to avoid CrashLoopBackOff errors. All certificates are also cached in memory, resulting in high memory consumption and duplication when the same lists are used across multiple APIs. The customer is requesting the ability to externalize the certificate whitelist so that only certificate fingerprints (instead of full certificate values) are stored in an external system, such as Redis or a database. This would improve performance, reduce memory usage, and simplify operations when managing large-scale environments.