<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgresql on 404 Code Not Found</title><link>https://www.404-code-not-found.com/tags/postgresql/</link><description>Recent content in Postgresql on 404 Code Not Found</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Jul 2026 08:00:00 -0600</lastBuildDate><atom:link href="https://www.404-code-not-found.com/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>Running Terraform Enterprise Active-Active on OpenShift: Lessons Learned</title><link>https://www.404-code-not-found.com/posts/tfe-on-openshift-active-active/</link><pubDate>Thu, 02 Jul 2026 08:00:00 -0600</pubDate><guid>https://www.404-code-not-found.com/posts/tfe-on-openshift-active-active/</guid><description>&lt;p>&lt;img src="https://www.404-code-not-found.com/posts/tfe-on-openshift-active-active/article.png" alt="Data center corridor with server racks lit by purple and orange accent lighting">&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>In my &lt;a href="https://www.404-code-not-found.com/posts/vault-on-openshift-hcp-autounseal">last post&lt;/a>, I covered the four
challenges I hit running Vault Enterprise on OpenShift. That same lab cluster
also runs Terraform Enterprise (TFE) in active-active mode, using that Vault
cluster as its secrets backend. TFE brought its own set of OpenShift-specific
problems — some in TFE itself, some in the supporting PostgreSQL and object
storage layers, and one that turned out to be the same VSO bug from the Vault
post showing up again in a different place.&lt;/p></description></item></channel></rss>