apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "54594" uid: f571c1e7-a475-4dce-a480-b6d8eaae0722 spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T02:24:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.244µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 1.107615ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 965.78µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 1.235151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 1.009698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:48:21Z" - latency: 1.514507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:47:21Z" - latency: 1.061588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:46:21Z" - latency: 970.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:45:21Z" - latency: 1.183474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:44:21Z" - latency: 1.007908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "55558" uid: 8b826f86-99df-46bd-8a5c-e54a7afe7c07 spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:23:21Z" message: 'load-balancer-api-external: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.105625ms message: 'load-balancer-api-external: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:21Z" - latency: 8.717326ms message: 'load-balancer-api-external: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:53:21Z" - latency: 3.579591ms message: 'load-balancer-api-external: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 9.01535ms message: 'load-balancer-api-external: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:52:21Z" - latency: 4.805447ms message: 'load-balancer-api-external: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 8.467197ms message: 'load-balancer-api-external: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:51:21Z" - latency: 4.749028ms message: 'load-balancer-api-external: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 8.841418ms message: 'load-balancer-api-external: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:50:21Z" - latency: 4.289605ms message: 'load-balancer-api-external: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 8.919126ms message: 'load-balancer-api-external: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "55559" uid: 0134976f-fd8d-4970-bb00-934bb1dad199 spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:23:21Z" message: 'load-balancer-api-internal: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.13099ms message: 'load-balancer-api-internal: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:21Z" - latency: 8.624917ms message: 'load-balancer-api-internal: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:53:21Z" - latency: 3.54454ms message: 'load-balancer-api-internal: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 9.092942ms message: 'load-balancer-api-internal: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:52:21Z" - latency: 4.370896ms message: 'load-balancer-api-internal: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 8.352531ms message: 'load-balancer-api-internal: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:51:21Z" - latency: 4.717544ms message: 'load-balancer-api-internal: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 8.908415ms message: 'load-balancer-api-internal: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:50:21Z" - latency: 4.259731ms message: 'load-balancer-api-internal: tcp connection to ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 8.722368ms message: 'load-balancer-api-internal: resolved host name ad5076076e8c34356b8a92995c649b03-6f26f35864784bda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-network-check-target-ip-10-0-132-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "54593" uid: 449e5378-7a72-47a3-aa98-856027bac252 spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:24:21Z" message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.3297ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 2.311205ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 2.476536ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 2.084457ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 2.363065ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:48:21Z" - latency: 2.299456ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:47:21Z" - latency: 2.359595ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:46:21Z" - latency: 2.323708ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:45:21Z" - latency: 2.316568ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:44:21Z" - latency: 2.419338ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-network-check-target-ip-10-0-140-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "54592" uid: 1d55b0a8-2fe1-4295-a91f-05bc8d131134 spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:24:21Z" message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.218713ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 2.406671ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 2.50821ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 2.104641ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 2.657969ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:48:21Z" - latency: 2.432005ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:47:21Z" - latency: 2.369584ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:46:21Z" - latency: 2.400146ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:45:21Z" - latency: 2.264347ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:44:21Z" - latency: 2.356062ms message: 'network-check-target-ip-10-0-140-223: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-network-check-target-ip-10-0-143-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "54591" uid: 179db3a1-d03f-4329-ab5f-e5f443488f4f spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:24:21Z" message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.051057ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 911.083µs message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 960.879µs message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 1.537285ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 1.451457ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:48:21Z" - latency: 1.094482ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:47:21Z" - latency: 1.171762ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:46:21Z" - latency: 1.009375ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:45:21Z" - latency: 1.055492ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:44:21Z" - latency: 1.713632ms message: 'network-check-target-ip-10-0-143-3: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-3-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-3.ec2.internal uid: 4ca8f42c-689a-4a51-945b-c3306dd86860 resourceVersion: "55557" uid: e1f7ce08-9243-42e0-a666-1e72f15e4e50 spec: sourcePod: network-check-source-869dcfcdcd-kgbcp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T02:23:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:21Z" - latency: 1.836343ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:53:21Z" - latency: 786.75µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:21Z" - latency: 1.934426ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:52:21Z" - latency: 1.255213ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:21Z" - latency: 1.830726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:51:21Z" - latency: 1.29366ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:50:21Z" - latency: 1.790305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:50:21Z" - latency: 805.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:49:21Z" - latency: 1.948552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:49:21Z" kind: List metadata: resourceVersion: ""