apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "48481" uid: d55db0d6-562b-40ba-9941-a94466a09f11 spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T18:28:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 783.676µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 917.304µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 1.006736ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 1.109837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:46:23Z" - latency: 1.00711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:45:23Z" - latency: 981.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:44:23Z" - latency: 1.071225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:43:23Z" - latency: 1.196408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:42:23Z" - latency: 760.184µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:41:23Z" - latency: 931.019µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:40:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "51296" uid: 909b16ff-f2a8-4a9c-9975-288e325ff424 spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T18:27:23Z" message: 'load-balancer-api-external: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.020541ms message: 'load-balancer-api-external: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 8.277554ms message: 'load-balancer-api-external: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:51:23Z" - latency: 3.935989ms message: 'load-balancer-api-external: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 8.248922ms message: 'load-balancer-api-external: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:50:23Z" - latency: 5.427793ms message: 'load-balancer-api-external: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 8.282906ms message: 'load-balancer-api-external: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:49:23Z" - latency: 5.44297ms message: 'load-balancer-api-external: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 8.79537ms message: 'load-balancer-api-external: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:48:23Z" - latency: 3.694228ms message: 'load-balancer-api-external: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 7.704103ms message: 'load-balancer-api-external: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "51297" uid: 15436b13-bb60-4474-b400-b168bb7b8915 spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T18:27:23Z" message: 'load-balancer-api-internal: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.009607ms message: 'load-balancer-api-internal: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 8.329883ms message: 'load-balancer-api-internal: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:51:23Z" - latency: 3.843527ms message: 'load-balancer-api-internal: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 8.31454ms message: 'load-balancer-api-internal: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:50:23Z" - latency: 5.117568ms message: 'load-balancer-api-internal: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 8.398839ms message: 'load-balancer-api-internal: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:49:23Z" - latency: 4.231457ms message: 'load-balancer-api-internal: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 8.847633ms message: 'load-balancer-api-internal: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:48:23Z" - latency: 6.123765ms message: 'load-balancer-api-internal: tcp connection to a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 7.802072ms message: 'load-balancer-api-internal: resolved host name a1922e4d2b4ff49a595f639d86a4ba3a-6243e6386330e69f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-ip-10-0-132-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "48480" uid: 01cb553a-01ce-4e78-981d-b22a66d82510 spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-12T18:28:23Z" message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.877263ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 1.896637ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 1.876984ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 1.708698ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:46:23Z" - latency: 2.191312ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:45:23Z" - latency: 1.919729ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:44:23Z" - latency: 1.917856ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:43:23Z" - latency: 1.960746ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:42:23Z" - latency: 1.756966ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:41:23Z" - latency: 1.952145ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:40:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-ip-10-0-141-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "48478" uid: 7154fab3-4568-430e-a82b-c4adeaae6504 spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T18:28:23Z" message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 751.785µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 724.552µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 800.317µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 1.247019ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:46:23Z" - latency: 830.311µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:45:23Z" - latency: 834.161µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:44:23Z" - latency: 1.375497ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:43:23Z" - latency: 957.056µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:42:23Z" - latency: 1.343837ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:41:23Z" - latency: 854.765µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:40:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-ip-10-0-141-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "48479" uid: 7d7f33d6-2d53-4059-a6aa-33f53bde518b spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T18:28:23Z" message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.058319ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 2.230564ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 2.260326ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 2.264975ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:46:23Z" - latency: 1.899666ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:45:23Z" - latency: 2.263864ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:44:23Z" - latency: 2.408488ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:43:23Z" - latency: 2.102591ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:42:23Z" - latency: 2.324193ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:41:23Z" - latency: 1.949544ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:40:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:21:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: bdd374fc-b42b-4837-b665-43bca3a621a7 resourceVersion: "51295" uid: ead61709-a44d-41ba-995c-3a3c04ef4a01 spec: sourcePod: network-check-source-869dcfcdcd-2r98h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T18:27:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 755.493µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 2.018478ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:51:23Z" - latency: 768.032µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 1.706468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:50:23Z" - latency: 1.198094ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 1.584497ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:49:23Z" - latency: 760.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 2.330215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:48:23Z" - latency: 799.554µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - latency: 1.619731ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:47:23Z" kind: List metadata: resourceVersion: ""