apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89529" uid: 66c4d943-c893-42d0-a2e2-35fa32d39428 spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:11:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.04771ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 889.111µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 1.157195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 941.475µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 912µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 972.201µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:23:41Z" - latency: 1.074853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:22:41Z" - latency: 855.987µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:21:41Z" - latency: 1.418281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:20:41Z" - latency: 1.054644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:19:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89531" uid: ffa37020-7f8c-4e5f-a16e-df52b3ba7193 spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:10:41Z" message: 'load-balancer-api-external: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.38599ms message: 'load-balancer-api-external: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 7.502846ms message: 'load-balancer-api-external: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:28:41Z" - latency: 5.94695ms message: 'load-balancer-api-external: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 12.755233ms message: 'load-balancer-api-external: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:27:41Z" - latency: 5.182067ms message: 'load-balancer-api-external: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 7.386161ms message: 'load-balancer-api-external: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:26:41Z" - latency: 4.896756ms message: 'load-balancer-api-external: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 6.753891ms message: 'load-balancer-api-external: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:25:41Z" - latency: 5.460475ms message: 'load-balancer-api-external: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 6.627412ms message: 'load-balancer-api-external: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:24:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89530" uid: 22aa732b-0827-4a79-b1e1-bd03f628849c spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:10:41Z" message: 'load-balancer-api-internal: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.353676ms message: 'load-balancer-api-internal: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 7.543714ms message: 'load-balancer-api-internal: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:28:41Z" - latency: 5.955866ms message: 'load-balancer-api-internal: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 12.790417ms message: 'load-balancer-api-internal: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:27:41Z" - latency: 5.17362ms message: 'load-balancer-api-internal: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 7.453384ms message: 'load-balancer-api-internal: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:26:41Z" - latency: 4.880412ms message: 'load-balancer-api-internal: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 6.735669ms message: 'load-balancer-api-internal: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:25:41Z" - latency: 5.56414ms message: 'load-balancer-api-internal: tcp connection to afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 6.557525ms message: 'load-balancer-api-internal: resolved host name afb35e615998e4024955f70c61cd36d7-c1814657712f161b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:24:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-network-check-target-ip-10-0-132-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89526" uid: 5524e9e6-9f9b-4095-953a-bf7188ea9000 spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:11:41Z" message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.325031ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 2.127668ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 2.189417ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 2.523908ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 2.366599ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 2.163761ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:23:41Z" - latency: 2.666019ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:22:41Z" - latency: 2.384074ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:21:41Z" - latency: 2.155198ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:20:41Z" - latency: 2.251806ms message: 'network-check-target-ip-10-0-132-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:19:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-network-check-target-ip-10-0-137-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89525" uid: 38510412-e9de-42ca-b7bb-140f289244ec spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:11:41Z" message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.437682ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 725.09µs message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 951.943µs message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 836.014µs message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 1.101313ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 1.058047ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:23:41Z" - latency: 1.000715ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:22:41Z" - latency: 1.262795ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:21:41Z" - latency: 863.797µs message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:20:41Z" - latency: 894.369µs message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:19:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-network-check-target-ip-10-0-143-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89527" uid: 44878c04-7047-4872-a407-267597ca4141 spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:11:41Z" message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458064ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 2.209367ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 2.4037ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 2.431209ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 1.939475ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 2.376714ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:23:41Z" - latency: 2.27437ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:22:41Z" - latency: 2.19317ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:21:41Z" - latency: 2.491472ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:20:41Z" - latency: 2.216644ms message: 'network-check-target-ip-10-0-143-86: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:19:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:04:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-134.ec2.internal uid: 87587fae-6364-45f6-a432-d878ad98f532 resourceVersion: "89528" uid: ede95a49-b473-44d7-885a-b3a196185770 spec: sourcePod: network-check-source-7d88cb55d8-888fz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:10:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:28:41Z" - latency: 2.375147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:28:41Z" - latency: 1.228835ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:27:41Z" - latency: 1.687281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:27:41Z" - latency: 987.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:26:41Z" - latency: 2.295474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:26:41Z" - latency: 969.217µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:25:41Z" - latency: 1.973988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:25:41Z" - latency: 823.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:24:41Z" - latency: 1.762144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:24:41Z" kind: List metadata: resourceVersion: ""