Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.zylon.ai/llms.txt

Use this file to discover all available pages before exploring further.

Proxy support is available starting from Zylon 1.48 and CLI version 1.23
If your Zylon installation is running in a LAN network that requires a proxy for internet access, follow these steps to configure the proxy settings.
1

Determine your proxy type

There are two types of proxies:SSL Inspection Proxy:
  • Intercepts and inspects HTTPS traffic
  • Decrypts traffic using its own SSL certificate, then re-encrypts it
  • Allows deep packet inspection and content filtering
Transparent Proxy:
  • Forwards HTTPS traffic without inspecting it
  • Does not modify SSL/TLS certificates
  • Acts as a simple pass-through for encrypted connections
To determine which type you have, run the following command, replacing your-proxy-address:port with your proxy details:
curl -x your-proxy-address:port -v https://example.com 2>&1 | grep -A 5 "Server certificate" | grep "issuer:"
Look at the output:
  • If you get an SSL error, you have an SSL inspection proxy
  • If the command succeeds, check the issuer field:
    • If the issuer is a public certificate authority (DigiCert, Let’s Encrypt, etc.), you have a transparent proxy
    • If the issuer is your organization’s internal CA or proxy server name, you have an SSL inspection proxy
2

Configure the proxy settings

Edit /etc/zylon/zylon-conf.yaml based on your proxy type:
proxy:
  enabled: true
  httpProxy: "http://your-proxy-address:port"
  httpsProxy: "http://your-proxy-address:port"
  noProxy: "your,no,proxy,exceptions"
  crt: |-
    -----BEGIN CERTIFICATE-----
    MIIDoTCCAomgAwIBAgIGEAHcBPNvMA0GCSqGSIb3DQEBCwUAMCgxEjAQBgNVBAMM
    ...
    ipRF9TO2AlABfLmTR7uN8o0Opc92
    -----END CERTIFICATE-----
To obtain your proxy CA certificate, you can try running:
echo | openssl s_client -showcerts -connect your-proxy-address:port 2>/dev/null | openssl x509
Note that this may not work with all proxy providers. If it fails, contact your network administrator for the CA certificate.
3

Apply the configuration

Run the sync command to apply the changes:
sudo zylon-cli sync
4

Restart services (optional, if your cluster was already running)

If the cluster was running before applying the proxy settings, restart the k0s controller and recreate the Zylon pods:
sudo systemctl daemon-reload
sudo systemctl restart k0scontroller
# Wait a few seconds until the cluster starts again
kubectl delete pods -n zylon --all