Issues in OpenShift After Change in IPTables (dial tcp 172.30.0.1:443: i/o timeout)

Solution In Progress - Updated -

Issue

  • Pod to pod networking stopped working after making an iptables modification
  • How to keep OpenShift cluster functioning after iptables rule change
  • Pods in Failed state
$ oc logs app-7-deploy
error: couldn't get deployment app-7: Get https://172.30.0.1:443/api/v1/namespaces/default/replicationcontrollers/app-7: dial tcp 172.30.0.1:443: i/o timeout

Environment

  • Red Hat OpenShift Container Platform
    • 3.2, 3.3, 3.4, 3.5

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