Simplified and Cost-Efficient GKE Node Management with NAP:
Secure your spot!
LogoLogo
PerfectScale.ioStart for FreeYour Account
  • Kubernetes Optimization
  • Getting started
    • How to onboard a cluster
    • Onboarding clusters programmatically
    • Onboarding with ArgoCD
    • Updating PerfectScale Agent resources
    • Re-onboarding a cluster
  • Enable automation
    • Automation setup instruction
    • Including a cluster, namespace or workload to the Automation
      • Configuring Automation for a cluster
      • Configuring Automation for a namespace
      • Configuring Automation for a workload
    • Excluding a namespace or workload from the Automation
    • Automation customization
    • Verifying Automation status
    • Exploring Automation KPIs
    • Self-healing mechanism for unschedulable pods
    • Disable automation
    • Troubleshooting
    • Automation with GitOps
  • Cloud billing integration
    • Connecting AWS CUR
    • Connecting Azure Cost Management
  • Clusters' metrics overview
  • Podfit | vertical pod right-sizing
    • Understanding 'At Risk' indicators
    • LimitRange and ResourceQuota
  • Infrafit | node right-sizing
  • Configure alerts
    • Alerts acknowledgement
  • Trends monitoring
  • Revisions history log
  • Product overview
    • How to monitor PerfectScale Agent
    • PerfectScale data collected
    • PerfectScale Autoscaler Objects' Events
    • Outbound Request Ports used by the Exporter and Autoscaler
    • PerfectScale Weekly Report
    • Product architecture
  • Customizations
    • Alerting
      • Resiliency alerts
      • Financial alerts
    • Pricing
      • Custom Pricing configuration
      • AWS CUR configuration
      • Azure Cost Management configuration
    • Ticketing & Bug Tracking
    • Communication & Messaging
      • Slack Integration
        • How to configure slack_token
        • How to configure routings
      • MS Teams Integration
        • How to configure teams_webhook
      • Datadog Alerts Integration
    • Label customizations
    • Grouping
    • Observability
    • Podfit labels
    • Optimization Policy customization
  • Administration
    • Cluster settings
    • User management
    • Roles and permissions
    • Subscription details
    • Help Center
  • PerfectScale trial
    • How to find your allocated vCPU?
  • PerfectScale Prometheus Exporter
  • Security
    • MFA
    • SSO
    • ps-agent RBAC Permissions
    • psc-autoscaler RBAC Permissions
    • ps-exporter via Proxy Configuration
  • Public API
  • Help PerfectScale to improve
  • Go to your account
Powered by GitBook
LogoLogo

© PerfectScale 2025

On this page
  1. Security

ps-exporter via Proxy Configuration

Instruction on how to connect ps-exporter via proxy

Previouspsc-autoscaler RBAC PermissionsNextPublic API

Last updated 5 months ago

If your cluster does not have access to the Internet and you are utilizing a proxy server you can connect the exporter via proxy in order to use PerfectScale.

To configure ps-exporter via proxy you'll need to modify the helm chart while (step: deploy PerfectScale) with additional settings (lines 6,7,8 and 9 in the following command):

helm upgrade --install -n perfectscale --create-namespace perfectscale \
  --set secret.create=true \
  --set secret.clientId="CHNAGE_TO YOUR" \
  --set secret.clientSecret="CHNAGE_TO YOUR" \
  --set settings.clusterName="CHNAGE_TO YOUR" \
  --set settings.httpProxyEnabled=true \
  --set settings.httpProxy="http://proxy.net:8080" \
  --set settings.httpsProxy="http://proxy.net:8080" \
  --set settings.noProxy=".corp\,.svc\,.cluster\,.local\,172.30.0.1\," \
  perfectscale/exporter

--set settings.httpProxyEnabled=true - enables proxy

--set settings.httpProxy="http://proxy.net:8080" \ - your proxy URL with the http protocol

--set settings.httpsProxy="http://proxy.net:8080" \ - your proxy URL with the https protocol

--set settings.noProxy=".corp\,.svc\,.cluster\,.local\,172.30.0.1\," \ - the TLDs are allowed without proxy

To use PerfectScale via a proxy, ensure that your proxy server allows http and https connections to the following endpoints:

  • registry.k8s.io

  • api.app.perfectscale.io/

  • app.perfectscale.io

  • perfectscale-io.github.io

  • public.ecr.aws

  • customer-data-prod-perfectscale-io.s3.eu-central-1.amazonaws.com

  • customer-data-prod-perfectscale-io.s3.dualstack.eu-central-1.amazonaws.com

  • s3.eu-central-1.amazonaws.com

  • s3.dualstack.eu-central-1.amazonaws.com

  • storage.googleapis.com

  • cloudfront.net

6️⃣
7️⃣
8️⃣
9️⃣
connecting the cluster