⭕
OpenShift Network Playground
  • Getting Started
    • OpenShift Network Playground Overview
    • Architecture
      • Fedora CoreOS
      • Network
      • DNS
      • DHCP
      • Proxy
      • DNS64
      • NAT64
      • PXE
  • Installation
    • Prerequisites
    • vSphere
    • RHEV
    • Libvirt
  • User Guide
    • Cockpit Console
    • CLI Tool
    • OpenShift Bare Metal IPI Cluster
    • Single Node OpenShift Cluster
    • Backup OpenShift Releases
    • Additional Network Interfaces
    • Cluster Node Access
    • Tools
    • Collection of Manifests
  • Troubleshooting
    • Cockpit Cluster deployment
  • FAQ
    • What is ONP?
    • What problem it solves?
    • How to access the cluster that is deployed inside the ONP?
Powered by GitBook
On this page
  1. Getting Started
  2. Architecture

Proxy

The OpenShift Network Playground uses squid for the proxy. It is a SSL-bump proxy. The certificates associated with it will be placed inside /opt/openshift-network-playground/proxy/certs/ directory. However, the compact OpenShift cluster which is deployed by the OpenShift Network Playground automatically adds that in the install-config.yaml file.

The proxy service is managed by systemd service named proxy.service.

Directory

/opt/openshift-network-playground/proxy/

Service

proxy.service

INFO

By default only compact cluster uses the proxy and not SNO cluster.

All the files (Containerfile and configuration) related to the proxy will be placed under the /opt/openshift-network-playground/proxy/ directory.

PreviousDHCPNextDNS64

Last updated 1 year ago