Openshift 4.2 installation on AWS on Private VPC: Failed to generate asset “DNS Config”: getting public zone for “x.com”: No public route53 zone found matching name “x.com”

Solution Verified - Updated -

Issue

  • The fact that the installation is done within a private VPC, expects that a public Route53 shouldn't be required from customer point of view, as private zone should be sufficient, however official installer needs to have a public domain, public ELB and public subnets on Route53. The installer keeps being improved after
  • The default ingress can be made internal with a Day-2 modification.
  • Openshift Container Platform 4.3 allows the deployment on existing private VPC as per documentation

Environment

  • Openshift Container Platform 4.2 [OCP]
  • Amazon Web Services [AWS]

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content