apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "128528" uid: 4d57dd4a-8122-4ac4-90ef-9d9a1fe8f1c0 spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T17:23:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.018962ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 1.437982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 1.612196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:17:34Z" - latency: 1.304481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:16:34Z" - latency: 915.519µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:15:34Z" - latency: 1.200944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:14:34Z" - latency: 1.385106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:13:34Z" - latency: 1.170741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:12:34Z" - latency: 1.328937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:11:34Z" - latency: 1.386129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:10:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "130214" uid: ffd4e28d-4e0f-43c1-b9da-c281780ca0df spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T17:22:34Z" message: 'load-balancer-api-external: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.195483ms message: 'load-balancer-api-external: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:22:34Z" - latency: 7.564718ms message: 'load-balancer-api-external: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:22:34Z" - latency: 17.638396ms message: 'load-balancer-api-external: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:21:34Z" - latency: 7.205418ms message: 'load-balancer-api-external: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:21:34Z" - latency: 14.019432ms message: 'load-balancer-api-external: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:20:34Z" - latency: 7.336615ms message: 'load-balancer-api-external: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:20:34Z" - latency: 16.550795ms message: 'load-balancer-api-external: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 6.943628ms message: 'load-balancer-api-external: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:19:34Z" - latency: 15.591719ms message: 'load-balancer-api-external: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 7.7918ms message: 'load-balancer-api-external: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:18:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "130242" uid: 79691824-c729-4410-8196-1aa8c988d6a3 spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T17:22:34Z" message: 'load-balancer-api-internal: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.34934137s message: 'load-balancer-api-internal: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:22:34Z" - latency: 7.634039ms message: 'load-balancer-api-internal: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:22:34Z" - latency: 14.591223ms message: 'load-balancer-api-internal: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:21:34Z" - latency: 7.331407ms message: 'load-balancer-api-internal: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:21:34Z" - latency: 17.051249ms message: 'load-balancer-api-internal: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:20:34Z" - latency: 7.433329ms message: 'load-balancer-api-internal: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:20:34Z" - latency: 15.258739ms message: 'load-balancer-api-internal: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 6.900269ms message: 'load-balancer-api-internal: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:19:34Z" - latency: 15.568681ms message: 'load-balancer-api-internal: tcp connection to adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 7.866669ms message: 'load-balancer-api-internal: resolved host name adeac0b519703453b88175bb523ccdba-ddf1f10164cc386f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:18:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-network-check-target-ip-10-0-138-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "128525" uid: d77d0896-c4e7-46b5-93d2-8c9920dce703 spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T17:23:34Z" message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.359463ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 2.261928ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 2.166251ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:17:34Z" - latency: 2.53725ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:16:34Z" - latency: 2.385409ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:15:34Z" - latency: 2.499114ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:14:34Z" - latency: 1.864242ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:13:34Z" - latency: 1.993597ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:12:34Z" - latency: 2.494835ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:11:34Z" - latency: 2.553935ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:10:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-network-check-target-ip-10-0-140-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "128527" uid: dd3cf7e2-8dcf-4838-82be-867e6faee02d spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T17:23:34Z" message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.414947ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 2.311559ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 2.436709ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:17:34Z" - latency: 2.776329ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:16:34Z" - latency: 2.622444ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:15:34Z" - latency: 2.430997ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:14:34Z" - latency: 2.200232ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:13:34Z" - latency: 2.112585ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:12:34Z" - latency: 2.569573ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:11:34Z" - latency: 2.36078ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:10:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-network-check-target-ip-10-0-142-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "128524" uid: e76b0826-15aa-462f-a432-c315295dd615 spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T17:23:34Z" message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.325796ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 1.305913ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 1.322402ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:17:34Z" - latency: 1.773782ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:16:34Z" - latency: 1.608928ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:15:34Z" - latency: 1.057515ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:14:34Z" - latency: 1.021398ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:13:34Z" - latency: 1.111496ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:12:34Z" - latency: 1.093446ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:11:34Z" - latency: 1.203632ms message: 'network-check-target-ip-10-0-142-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:10:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:16:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-138.ec2.internal uid: 1dc8250e-3380-46e6-8ec7-10b1e6a09049 resourceVersion: "130213" uid: c96ea706-5c01-4b97-b411-5b5c8271126e spec: sourcePod: network-check-source-6f78d59f99-4dhsh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T17:22:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.227085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:22:34Z" - latency: 2.113768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:22:34Z" - latency: 972.995µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:21:34Z" - latency: 2.434763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:21:34Z" - latency: 1.214142ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:20:34Z" - latency: 2.328228ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:20:34Z" - latency: 1.206003ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:19:34Z" - latency: 2.386407ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:19:34Z" - latency: 1.300657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:18:34Z" - latency: 1.966952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:18:34Z" kind: List metadata: resourceVersion: ""