- Documentation
- OpenShift Dedicated
- Cluster administration
- Configuring private connections
- Configuring a private cluster history bug_report picture_as_pdf
- About
- What's new
- Introduction to OpenShift Dedicated
- Architecture
- Red Hat OpenShift Cluster Manager
- Planning your environment
- Getting started
- Installing, accessing, and deleting OpenShift Dedicated clusters
- Support
- Web console
- CLI tools
- Cluster administration
- Security and compliance
- Authentication and authorization
- Authentication and authorization overview
- Understanding authentication
- Managing user-owned OAuth access tokens
- Configuring identity providers
- Revoking privileges and access to an OpenShift Dedicated cluster
- Managing administration roles and users
- Using RBAC to define and apply permissions
- Understanding and creating service accounts
- Using service accounts in applications
- Using a service account as an OAuth client
- Scoping tokens
- Using bound service account tokens
- Managing security context constraints
- Understanding and managing pod security admission
- Syncing LDAP groups
- Upgrading
- CI/CD
- Images
- Overview of images
- Overview of the Cluster Samples Operator
- Using the Cluster Samples Operator with an alternate registry
- Creating images
- Managing images
- Managing image streams
- Using image streams with Kubernetes resources
- Triggering updates on image stream changes
- Image configuration resources
- Using templates
- Using Ruby on Rails
- Using images
- Add-on services
- Storage
- Registry
- Operators
- Operators overview
- Understanding Operators
- User tasks
- Administrator tasks
- Developing Operators
- About the Operator SDK
- Installing the Operator SDK CLI
- Go-based Operators
- Ansible-based Operators
- Helm-based Operators
- Defining cluster service versions (CSVs)
- Working with bundle images
- Complying with pod security admission
- Validating Operators using the scorecard
- Validating Operator bundles
- High-availability or single-node cluster detection and support
- Configuring built-in monitoring with Prometheus
- Configuring leader election
- Object pruning utility
- Migrating package manifest projects to bundle format
- Operator SDK CLI reference
- Migrating to Operator SDK v0.1.0
- Networking
- Building applications
- Building applications overview
- Projects
- Creating applications
- Viewing application composition using the Topology view
- Working with Helm charts
- Deployments
- Quotas
- Using config maps with applications
- Monitoring project and application metrics using the Developer perspective
- Monitoring application health
- Editing applications
- Working with quotas
- Pruning objects to reclaim resources
- Idling applications
- Deleting applications
- Using the Red Hat Marketplace
- Nodes
- Overview of nodes
- Working with pods
- Automatically scaling pods with the Custom Metrics Autoscaler Operator
- Release notes
- Custom Metrics Autoscaler Operator overview
- Installing the custom metrics autoscaler
- Understanding the custom metrics autoscaler triggers
- Understanding the custom metrics autoscaler trigger authentications
- Pausing the custom metrics autoscaler
- Gathering audit logs
- Gathering debugging data
- Viewing Operator metrics
- Understanding how to add custom metrics autoscalers
- Removing the Custom Metrics Autoscaler Operator
- Controlling pod placement onto nodes (scheduling)
- About pod placement using the scheduler
- Placing pods relative to other pods using pod affinity and anti-affinity rules
- Controlling pod placement on nodes using node affinity rules
- Placing pods onto overcommited nodes
- Placing pods on specific nodes using node selectors
- Controlling pod placement using pod topology spread constraints
- Using jobs and daemon sets
- Working with nodes
- Working with containers
- Understanding containers
- Using Init Containers to perform tasks before a pod is deployed
- Using volumes to persist container data
- Mapping volumes using projected volumes
- Allowing containers to consume API objects
- Copying files to or from a container
- Executing remote commands in a container
- Using port forwarding to access applications in a container
- Working with clusters
- Observability
- Observability overview
- Monitoring
- Monitoring overview
- Accessing monitoring for user-defined projects
- Configuring the monitoring stack
- Disabling monitoring for user-defined projects
- Enabling alert routing for user-defined projects
- Managing metrics
- Managing alerts
- Reviewing monitoring dashboards
- Accessing third-party monitoring APIs
- Troubleshooting monitoring issues
- Config map reference for the Cluster Monitoring Operator
- Service Mesh
- Service Mesh 2.x
- About OpenShift Service Mesh
- Service Mesh 2.x release notes
- Service Mesh architecture
- Service Mesh deployment models
- Service Mesh and Istio differences
- Preparing to install Service Mesh
- Installing the Operators
- Creating the ServiceMeshControlPlane
- Adding workloads to a service mesh
- Enabling sidecar injection
- Upgrading Service Mesh
- Managing users and profiles
- Security
- Traffic management
- Metrics, logs, and traces
- Performance and scalability
- Deploying to production
- Federation
- Extensions
- 3scale WebAssembly for 2.1
- 3scale Istio adapter for 2.0
- Troubleshooting Service Mesh
- Control plane configuration reference
- Kiali configuration reference
- Jaeger configuration reference
- Uninstalling Service Mesh
- Service Mesh 2.x
- Serverless
Configuring a private cluster
An OpenShift Dedicated cluster can be made private so that internal applications can be hosted inside a corporate network. In addition, private clusters can be configured to have only internal API endpoints for increased security.
OpenShift Dedicated administrators can choose between public and private cluster configuration from within OpenShift Cluster Manager. Privacy settings can be configured during cluster creation or after a cluster is established.
Enabling a private cluster during cluster creation
You can enable private cluster settings when creating a new cluster.
-
The following private connections must be configured to allow private access:
-
VPC Peering
-
Cloud VPN
-
DirectConnect (AWS only)
-
TransitGateway (AWS only)
-
Cloud Interconnect (GCP only)
-
-
Log in to OpenShift Cluster Manager.
-
Click Create cluster → OpenShift Dedicated → Create cluster.
-
Configure your cluster details.
-
When selecting your preferred network configuration, select Advanced.
-
Select Private.
When set to Private, you cannot access your cluster unless you have configured the private connections in your cloud provider as outlined in the prerequisites.
-
Click Create cluster. The cluster creation process begins and takes about 30-40 minutes to complete.
-
The Installing cluster heading, under the Overview tab, indicates that the cluster is installing and you can view the installation logs from this heading. The Status indicator under the Details heading indicates when your cluster is Ready for use.
Enabling an existing cluster to be private
After a cluster has been created, you can later enable the cluster to be private.
-
The following private connections must be configured to allow private access:
-
VPC Peering
-
Cloud VPN
-
DirectConnect (AWS only)
-
TransitGateway (AWS only)
-
Cloud Interconnect (GCP only)
-
-
Log in to OpenShift Cluster Manager.
-
Select the public cluster you would like to make private.
-
On the Networking tab, select Make API private under Control Plane API endpoint.
When set to Private, you cannot access your cluster unless you have configured the private connections in your cloud provider as outlined in the prerequisites.
-
Click Change settings.
Transitioning your cluster between private and public can take several minutes to complete.
Enabling an existing private cluster to be public
After a private cluster has been created, you can later enable the cluster to be public.
-
Log in to OpenShift Cluster Manager.
-
Select the private cluster you would like to make public.
-
On the Networking tab, deselect Make API private under Control Plane API endpoint.
-
Click Change settings.
Transitioning your cluster between private and public can take several minutes to complete.