apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "43566" uid: 9c4ed73b-75a2-4c3d-bb27-35580e3926d9 spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T12:49:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.398561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 765.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 795.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 1.244008ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:07:18Z" - latency: 1.103422ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:06:18Z" - latency: 1.021885ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:05:18Z" - latency: 819.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:04:18Z" - latency: 1.256807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:03:18Z" - latency: 933.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:02:18Z" - latency: 951.481µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:01:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "45754" uid: d26a5542-85a7-422c-b2ef-e4fc972eb953 spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T12:48:18Z" message: 'load-balancer-api-external: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.721763ms message: 'load-balancer-api-external: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:12:18Z" - latency: 7.45877ms message: 'load-balancer-api-external: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:12:18Z" - latency: 5.287482ms message: 'load-balancer-api-external: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:11:18Z" - latency: 6.55808ms message: 'load-balancer-api-external: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:11:18Z" - latency: 4.721485ms message: 'load-balancer-api-external: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 6.41829ms message: 'load-balancer-api-external: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:10:18Z" - latency: 4.548252ms message: 'load-balancer-api-external: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 7.184014ms message: 'load-balancer-api-external: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:09:18Z" - latency: 4.002306ms message: 'load-balancer-api-external: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 11.356682ms message: 'load-balancer-api-external: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:08:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "45755" uid: 8e0aadad-daa6-4034-af76-eef11d4a7234 spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T12:48:18Z" message: 'load-balancer-api-internal: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.738289ms message: 'load-balancer-api-internal: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:12:18Z" - latency: 7.436955ms message: 'load-balancer-api-internal: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:12:18Z" - latency: 5.266095ms message: 'load-balancer-api-internal: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:11:18Z" - latency: 6.528925ms message: 'load-balancer-api-internal: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:11:18Z" - latency: 4.76377ms message: 'load-balancer-api-internal: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 6.516444ms message: 'load-balancer-api-internal: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:10:18Z" - latency: 4.783445ms message: 'load-balancer-api-internal: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 7.159963ms message: 'load-balancer-api-internal: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:09:18Z" - latency: 4.367805ms message: 'load-balancer-api-internal: tcp connection to a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 11.304445ms message: 'load-balancer-api-internal: resolved host name a74dfdc10a4454733a90727596b13809-da38878c58eb0f4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T13:08:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-133-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "43563" uid: 7f9f9a36-640c-458a-a654-683a0a7c0915 spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T12:49:18Z" message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.585849ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 1.109817ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 944.138µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 1.377834ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:07:18Z" - latency: 999.064µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:06:18Z" - latency: 866.909µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:05:18Z" - latency: 780.261µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:04:18Z" - latency: 927.935µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:03:18Z" - latency: 926.921µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:02:18Z" - latency: 968.996µs message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:01:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-142-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "43564" uid: e34b8cdd-36f0-43b2-9bf8-aff579731148 spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T12:49:18Z" message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.287999ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 1.977903ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 2.077044ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 2.286046ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:07:18Z" - latency: 2.28694ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:06:18Z" - latency: 2.210373ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:05:18Z" - latency: 2.123059ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:04:18Z" - latency: 2.436101ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:03:18Z" - latency: 2.233214ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:02:18Z" - latency: 2.060292ms message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:01:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-143-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "43565" uid: 59ca0a2a-ec84-451c-903c-3bc10c227fbe spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T12:49:18Z" message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.268316ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 2.170011ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 2.307668ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 2.474637ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:07:18Z" - latency: 2.271391ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:06:18Z" - latency: 2.156691ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:05:18Z" - latency: 1.881336ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:04:18Z" - latency: 2.405254ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:03:18Z" - latency: 2.26577ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:02:18Z" - latency: 2.239255ms message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:01:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T12:42:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.ec2.internal uid: 15af18cd-a87d-480d-9117-1a16f4b3fb43 resourceVersion: "45753" uid: f7846d1b-eae5-431d-9085-344abc4634f4 spec: sourcePod: network-check-source-7f44b6dd87-g8tvl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T12:48:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.519µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:12:18Z" - latency: 1.672872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T13:12:18Z" - latency: 996.824µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:11:18Z" - latency: 1.942068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T13:11:18Z" - latency: 1.271482ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:10:18Z" - latency: 1.527866ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T13:10:18Z" - latency: 748.555µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:09:18Z" - latency: 2.371368ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T13:09:18Z" - latency: 858.824µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T13:08:18Z" - latency: 1.658774ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T13:08:18Z" kind: List metadata: resourceVersion: ""