apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "27530" uid: 92931441-86f2-46e4-a0b1-5ca789fd6b94 spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T14:42:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.01028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:49:35Z" - latency: 944.678µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:48:35Z" - latency: 1.005338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 1.207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 1.050091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 1.10269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 1.089821ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 1.041781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:35Z" - latency: 1.396077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:35Z" - latency: 832.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "26327" uid: 08ce9517-733e-475a-a62c-4517132a5f64 spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:41:35Z" message: 'load-balancer-api-external: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.399366ms message: 'load-balancer-api-external: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 9.933713ms message: 'load-balancer-api-external: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:47:35Z" - latency: 4.13408ms message: 'load-balancer-api-external: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 10.027509ms message: 'load-balancer-api-external: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:46:35Z" - latency: 4.25993ms message: 'load-balancer-api-external: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 10.146772ms message: 'load-balancer-api-external: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:45:35Z" - latency: 5.330303ms message: 'load-balancer-api-external: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 9.530738ms message: 'load-balancer-api-external: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:44:35Z" - latency: 5.119387ms message: 'load-balancer-api-external: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 7.974262ms message: 'load-balancer-api-external: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:43:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "26326" uid: 6b51452d-8381-4423-9909-8cceb38ddd5c spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:41:35Z" message: 'load-balancer-api-internal: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.478534ms message: 'load-balancer-api-internal: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 9.914221ms message: 'load-balancer-api-internal: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:47:35Z" - latency: 4.438614ms message: 'load-balancer-api-internal: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 9.977744ms message: 'load-balancer-api-internal: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:46:35Z" - latency: 4.230497ms message: 'load-balancer-api-internal: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 10.049867ms message: 'load-balancer-api-internal: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:45:35Z" - latency: 5.316459ms message: 'load-balancer-api-internal: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 9.498937ms message: 'load-balancer-api-internal: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:44:35Z" - latency: 4.257766ms message: 'load-balancer-api-internal: tcp connection to a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 7.901671ms message: 'load-balancer-api-internal: resolved host name a9867366353ad417db10ecf20058e293-224dff86356837de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:43:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-network-check-target-ip-10-0-128-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "27528" uid: 945f1247-a64b-42c7-8443-4b5ef42b3f55 spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:42:35Z" message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.289594ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:49:35Z" - latency: 2.91385ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:48:35Z" - latency: 2.23212ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 2.367866ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 2.40973ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 2.392424ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 2.55515ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 2.38064ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:35Z" - latency: 2.340722ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:35Z" - latency: 3.032172ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-network-check-target-ip-10-0-140-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "27527" uid: 400cc638-8b6c-4597-a29f-66d687eeeff0 spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:42:35Z" message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.350421ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:49:35Z" - latency: 902.938µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:48:35Z" - latency: 881.233µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 889.884µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 890.08µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 910.632µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 801.56µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 1.267493ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:35Z" - latency: 890.734µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:35Z" - latency: 874.847µs message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-network-check-target-ip-10-0-141-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "27529" uid: 9965cf69-373b-44b8-884e-4cfd44c7b9b1 spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:42:35Z" message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.263523ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:49:35Z" - latency: 2.041003ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:48:35Z" - latency: 2.127973ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 1.997943ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 2.155754ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 2.352631ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 2.316565ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 2.239253ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:35Z" - latency: 2.286838ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:35Z" - latency: 2.259303ms message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:35:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-144-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-144.ec2.internal uid: dbc9ed74-ceb3-433d-8bfb-c1237addf952 resourceVersion: "26325" uid: 4bccfb70-6302-4d8b-95dc-34d54bfb369b spec: sourcePod: network-check-source-7b678d77c7-q47lm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T14:41:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.515µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:47:35Z" - latency: 1.742187ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:47:35Z" - latency: 1.072995ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:46:35Z" - latency: 1.919307ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:46:35Z" - latency: 1.221808ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:45:35Z" - latency: 1.775369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:45:35Z" - latency: 1.243234ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:35Z" - latency: 1.737196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:44:35Z" - latency: 829.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:35Z" - latency: 1.769933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:43:35Z" kind: List metadata: resourceVersion: ""