apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "49699" uid: 23df570c-7d0f-4178-a800-5b0aab9c8b18 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T19:35:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.438515ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 1.285634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 950.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 1.172598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 1.219166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:17Z" - latency: 1.339157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:17Z" - latency: 962.21µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:17Z" - latency: 1.395942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:17Z" - latency: 2.338045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:17Z" - latency: 1.432946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "50529" uid: c133eefe-3f7c-4b6c-bd6f-daca5b975af2 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:34:17Z" message: 'load-balancer-api-external: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.273389ms message: 'load-balancer-api-external: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:04:17Z" - latency: 7.48539ms message: 'load-balancer-api-external: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:04:17Z" - latency: 4.113936ms message: 'load-balancer-api-external: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 7.960929ms message: 'load-balancer-api-external: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:03:17Z" - latency: 6.452863ms message: 'load-balancer-api-external: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 7.152099ms message: 'load-balancer-api-external: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:02:17Z" - latency: 5.426282ms message: 'load-balancer-api-external: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 6.540797ms message: 'load-balancer-api-external: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:01:17Z" - latency: 5.336272ms message: 'load-balancer-api-external: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 6.925731ms message: 'load-balancer-api-external: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:00:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "50528" uid: de68737b-74a0-4aba-a1a3-0ee37e7c8f30 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:34:17Z" message: 'load-balancer-api-internal: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.480137ms message: 'load-balancer-api-internal: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:04:17Z" - latency: 7.39598ms message: 'load-balancer-api-internal: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:04:17Z" - latency: 4.951503ms message: 'load-balancer-api-internal: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 7.991026ms message: 'load-balancer-api-internal: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:03:17Z" - latency: 6.524795ms message: 'load-balancer-api-internal: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 6.987364ms message: 'load-balancer-api-internal: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:02:17Z" - latency: 5.36571ms message: 'load-balancer-api-internal: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 6.499757ms message: 'load-balancer-api-internal: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:01:17Z" - latency: 5.307642ms message: 'load-balancer-api-internal: tcp connection to a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 6.958603ms message: 'load-balancer-api-internal: resolved host name a14a4ca6f19b94c2582aef2bf518b257-fbc566c347a8adb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:00:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-network-check-target-ip-10-0-131-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "49697" uid: 5dc5b0ba-6bac-4af4-9627-590bf726f846 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:35:17Z" message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.2324ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 2.46086ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 2.036005ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 2.327075ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 2.318323ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:17Z" - latency: 2.435643ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:17Z" - latency: 2.364654ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:17Z" - latency: 3.684981ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:17Z" - latency: 2.185834ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:17Z" - latency: 2.436637ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-network-check-target-ip-10-0-133-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "49698" uid: 98b3d616-e7df-4594-bf05-32337f8a8717 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:35:17Z" message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.316049ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 2.14242ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 2.005681ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 2.298358ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 2.188869ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:17Z" - latency: 1.995415ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:17Z" - latency: 1.943369ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:17Z" - latency: 3.44863ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:17Z" - latency: 3.035808ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:17Z" - latency: 2.289894ms message: 'network-check-target-ip-10-0-133-207: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-network-check-target-ip-10-0-143-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "49696" uid: 4836b7de-0b71-4441-8fbe-adb4d22b9fa0 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:35:17Z" message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.853911ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 1.505609ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 1.370406ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 1.717208ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 1.56086ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:17Z" - latency: 1.629699ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:17Z" - latency: 1.124869ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:17Z" - latency: 7.445464ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:17Z" - latency: 3.667855ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:17Z" - latency: 1.809196ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:28:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-242.ec2.internal uid: 0691830d-6822-4e8d-af7d-bea8324e86fb resourceVersion: "50527" uid: 3a188ec1-2e80-44a6-b1e7-16aa8bb9b409 spec: sourcePod: network-check-source-989f8b8dc-hvd2s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T19:34:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.048µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:04:17Z" - latency: 2.118837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:04:17Z" - latency: 898.524µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:03:17Z" - latency: 2.791292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:03:17Z" - latency: 973.752µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:02:17Z" - latency: 2.249143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:02:17Z" - latency: 839.862µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:17Z" - latency: 2.166168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:01:17Z" - latency: 878.882µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:17Z" - latency: 2.011917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:00:17Z" kind: List metadata: resourceVersion: ""