<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>openshift on Live Average</title>
    <link>https://liveaverage.com/tags/openshift/</link>
    <description>Recent content in openshift on Live Average</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Apr 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://liveaverage.com/tags/openshift/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Selective OpenShift IPI on AWS GovCloud without Route 53</title>
      <link>https://liveaverage.com/blog/selective-openshift-ipi-without-route53/</link>
      <pubDate>Tue, 27 Apr 2021 00:00:00 +0000</pubDate>
      
      <guid>https://liveaverage.com/blog/selective-openshift-ipi-without-route53/</guid>
      <description>Overview If you&amp;rsquo;ve deployed OpenShift on AWS using the IPI (Installer Provisioned Infrastructure) deployment method then you&amp;rsquo;re aware of the hardline requirement for Route 53 public/private zones, depending on the publish method set in your OpenShift install-config.yaml. This typically doesn&amp;rsquo;t present a problem for most customers, but select companies disallow use of Route 53 in favor of their own managed DNS (e.g. Infoblox). Unfortunately this limitation forces most customers to pursue a UPI (User Provisioned Infrastructure) deployment, which may (read: should) require custom terraform/ansible automation to standup all other prerequisities such as subnets, security groups, load balancers, EC2 instances, S3 buckets, etc.</description>
    </item>
    
    <item>
      <title>Practical OpenShift 4 Installation Troubleshooting</title>
      <link>https://liveaverage.com/blog/practical-openshift-4-installation-troubleshooting/</link>
      <pubDate>Thu, 04 Feb 2021 00:00:00 +0000</pubDate>
      
      <guid>https://liveaverage.com/blog/practical-openshift-4-installation-troubleshooting/</guid>
      <description>There&amp;rsquo;s a lot of great documentation on running, administering, consuming, and troubleshooting OpenShift 4, but the installation process is still a bit vague for some admins, and even more obscure if failures are encountered. I recently stepped through general installation troubleshooting for a failed OpenShift 4.6.8 deployment which hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1895024 - The core issue relates to low entropy on my VMs, but this bug was repeatable and offered a great exercise to share troubleshooting/diagnostic steps.</description>
    </item>
    
  </channel>
</rss>
