apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:20:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "136212" uid: 4007de78-412b-4d31-8230-e90654125a37 spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T23:27:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.237101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:11Z" - latency: 1.473081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:11Z" - latency: 1.118058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:11Z" - latency: 1.064646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:11Z" - latency: 2.126535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:11Z" - latency: 928.289µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:11Z" - latency: 891.331µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:10:11Z" - latency: 1.25407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:09:11Z" - latency: 1.513503ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:08:11Z" - latency: 1.181086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:07:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:20:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "141254" uid: 1b036e21-0369-43d1-8875-a6bb65764497 spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T23:26:11Z" message: 'load-balancer-api-external: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.67281ms message: 'load-balancer-api-external: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:11Z" - latency: 6.915834ms message: 'load-balancer-api-external: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:20:11Z" - latency: 5.26761ms message: 'load-balancer-api-external: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:11Z" - latency: 7.371697ms message: 'load-balancer-api-external: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:19:11Z" - latency: 5.931389ms message: 'load-balancer-api-external: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:11Z" - latency: 6.996781ms message: 'load-balancer-api-external: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:18:11Z" - latency: 5.163197ms message: 'load-balancer-api-external: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:11Z" - latency: 6.867174ms message: 'load-balancer-api-external: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:17:11Z" - latency: 5.136498ms message: 'load-balancer-api-external: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:11Z" - latency: 7.72784ms message: 'load-balancer-api-external: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:16:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:20:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "141255" uid: 7dfffbee-8b17-40ce-beb9-58ba08471c25 spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T23:26:11Z" message: 'load-balancer-api-internal: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.50033ms message: 'load-balancer-api-internal: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:11Z" - latency: 6.986233ms message: 'load-balancer-api-internal: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:20:11Z" - latency: 5.28734ms message: 'load-balancer-api-internal: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:11Z" - latency: 7.41134ms message: 'load-balancer-api-internal: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:19:11Z" - latency: 5.659966ms message: 'load-balancer-api-internal: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:11Z" - latency: 7.077561ms message: 'load-balancer-api-internal: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:18:11Z" - latency: 5.180622ms message: 'load-balancer-api-internal: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:11Z" - latency: 6.78474ms message: 'load-balancer-api-internal: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:17:11Z" - latency: 5.148251ms message: 'load-balancer-api-internal: tcp connection to a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:11Z" - latency: 7.80671ms message: 'load-balancer-api-internal: resolved host name a89e5e1c7169248cead0c4e7f1cca8d1-9b02837b85ac7765.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:16:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:20:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-network-check-target-ip-10-0-134-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "136211" uid: d9d10cec-9d2b-4c5f-8e79-89efe93d40c5 spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:27:11Z" message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.389423ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:11Z" - latency: 2.726278ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:11Z" - latency: 2.925875ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:11Z" - latency: 2.528058ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:11Z" - latency: 3.079876ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:11Z" - latency: 2.03764ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:11Z" - latency: 2.170542ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:10:11Z" - latency: 2.967554ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:09:11Z" - latency: 2.58596ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:08:11Z" - latency: 2.251868ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:07:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:57:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-network-check-target-ip-10-0-137-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "140490" uid: 96e50fd8-54fa-4347-b1d5-75134b070add spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:04:49Z" message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.884069ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:49Z" - latency: 2.118046ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:49Z" - latency: 2.966626ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:49Z" - latency: 2.511841ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:49Z" - latency: 2.394452ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:49Z" - latency: 2.407183ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:49Z" - latency: 2.29656ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:49Z" - latency: 2.420117ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:49Z" - latency: 2.598824ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:10:49Z" - latency: 2.419171ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:09:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:20:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-network-check-target-ip-10-0-142-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "136210" uid: 75b6e6e1-4d63-4aff-8bae-96cff4f5fe4c spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T23:27:11Z" message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.521µs message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:11Z" - latency: 1.225185ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:15:11Z" - latency: 1.071567ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:14:11Z" - latency: 1.363832ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:13:11Z" - latency: 1.657641ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:12:11Z" - latency: 1.196442ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:11:11Z" - latency: 943.589µs message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:10:11Z" - latency: 885.008µs message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:09:11Z" - latency: 1.536413ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:08:11Z" - latency: 1.553426ms message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:07:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:20:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-208-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-208.us-east-2.compute.internal uid: ba680623-d47e-47fb-9964-a2202f6ed449 resourceVersion: "141253" uid: 28008e44-f5b8-4500-bf7e-2e885cc000b6 spec: sourcePod: network-check-source-6f78d59f99-flrmm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T23:26:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.527µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:20:11Z" - latency: 2.020004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:20:11Z" - latency: 903.846µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:19:11Z" - latency: 2.1148ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:19:11Z" - latency: 1.217416ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:18:11Z" - latency: 2.015719ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:18:11Z" - latency: 2.19944ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:17:11Z" - latency: 2.106504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:17:11Z" - latency: 940.316µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:16:11Z" - latency: 2.081931ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:16:11Z" kind: List metadata: resourceVersion: ""