# Connecting Private Resources Cleric provides a lightweight Connector that you deploy inside your private network (on a VM or inside Kubernetes). The Connector functions as a simple network proxy, allowing Cleric to query your private endpoints, such as your Kubernetes API servers. ## How It Works You configure what Cleric can access by providing configuration to the Connector. Cleric cannot reach any part of your network beyond the endpoints you configure. The Connector creates a secure connection from your private environment to ours. No public IPs, VPN appliances, or special firewall rules required. The connection is end-to-end encrypted, ensuring that your data stays protected. ## Use Cases Common scenarios for the Connector include: * **Private Kubernetes clusters**: Access clusters without public API server endpoints * **Internal monitoring systems**: Connect to Prometheus, Grafana, or other tools behind a firewall * **On-premises infrastructure**: Query resources in data centers not exposed to the internet ## Getting Started Connector deployment is guided by the Cleric team. Reach out via your dedicated Slack Connect channel to set up private resource access for your environment. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cleric.ai/integrations/private-resources.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.