apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63175" uid: 0fc9f5da-d297-4867-a8a2-ce1aa4a542e3 spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T02:48:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 1.16879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 1.377553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 1.265978ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 942.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 1.123139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:18:42Z" - latency: 1.250706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:17:42Z" - latency: 1.417434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:16:42Z" - latency: 1.071523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:15:42Z" - latency: 1.077822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63177" uid: 2ee32eed-ddbe-4cef-a6e8-d5e8ce7b8c4c spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:47:42Z" message: 'load-balancer-api-external: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.888613ms message: 'load-balancer-api-external: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 7.714054ms message: 'load-balancer-api-external: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:23:42Z" - latency: 4.268572ms message: 'load-balancer-api-external: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 9.273957ms message: 'load-balancer-api-external: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:22:42Z" - latency: 4.597342ms message: 'load-balancer-api-external: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 9.48935ms message: 'load-balancer-api-external: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:21:42Z" - latency: 5.469193ms message: 'load-balancer-api-external: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 8.816609ms message: 'load-balancer-api-external: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:20:42Z" - latency: 4.766339ms message: 'load-balancer-api-external: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 7.771005ms message: 'load-balancer-api-external: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:19:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63176" uid: 566bb70a-0bd6-4903-b06d-7a3d2b0d7e68 spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:47:42Z" message: 'load-balancer-api-internal: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.152019ms message: 'load-balancer-api-internal: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 7.756664ms message: 'load-balancer-api-internal: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:23:42Z" - latency: 4.251ms message: 'load-balancer-api-internal: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 9.37905ms message: 'load-balancer-api-internal: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:22:42Z" - latency: 3.461987ms message: 'load-balancer-api-internal: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 9.490644ms message: 'load-balancer-api-internal: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:21:42Z" - latency: 3.453863ms message: 'load-balancer-api-internal: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 8.913331ms message: 'load-balancer-api-internal: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:20:42Z" - latency: 3.865252ms message: 'load-balancer-api-internal: tcp connection to ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 7.795007ms message: 'load-balancer-api-internal: resolved host name ad47c2506a1bd40caa76140849de666e-c6ed6307f1716a13.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:19:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-ip-10-0-130-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63171" uid: feb6566a-a357-4cc8-a873-41b204ce8939 spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:48:42Z" message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.080538ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 890.239µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 1.681547ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 992.814µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 843.177µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 1.756502ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:18:42Z" - latency: 935.164µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:17:42Z" - latency: 1.520245ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:16:42Z" - latency: 933.672µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:15:42Z" - latency: 861.543µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-ip-10-0-133-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63173" uid: 64614f64-4ac1-4fb9-86c5-6dac44522bd5 spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:48:42Z" message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.824154ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 2.312608ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 2.065274ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 1.833035ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 1.927785ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 1.996333ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:18:42Z" - latency: 1.698063ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:17:42Z" - latency: 2.107316ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:16:42Z" - latency: 2.04266ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:15:42Z" - latency: 2.162053ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-ip-10-0-143-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63172" uid: a45bb796-f99a-44d8-a4d7-2adcbcdc3ad1 spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:48:42Z" message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.48251ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 2.129862ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 2.847192ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 2.600206ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 1.978905ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 2.070359ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:18:42Z" - latency: 2.145036ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:17:42Z" - latency: 2.527381ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:16:42Z" - latency: 1.875141ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:15:42Z" - latency: 2.100816ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:41:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 3ca2ea24-c4dd-4649-95fe-a54e15a8a539 resourceVersion: "63174" uid: 50568cf1-fdd7-4e6a-9263-256c155b275d spec: sourcePod: network-check-source-7bc5b6bf85-gzdtn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T02:47:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028232ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:23:42Z" - latency: 2.704333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:23:42Z" - latency: 767.701µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:22:42Z" - latency: 2.134831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:22:42Z" - latency: 1.235807ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:21:42Z" - latency: 1.934189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:21:42Z" - latency: 798.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:20:42Z" - latency: 1.883939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:20:42Z" - latency: 997.621µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:19:42Z" - latency: 1.740923ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:19:42Z" kind: List metadata: resourceVersion: ""