apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "21595" uid: 125d335b-cfc3-4a8c-9432-92d8e9e750ac spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T18:15:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.111997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:24Z" - latency: 1.041873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:28:24Z" - latency: 1.612513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:24Z" - latency: 1.098584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 1.147094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 1.516278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 933.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 980.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 1.186049ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:24Z" - latency: 1.062267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "20186" uid: c6e5eef2-65e1-4f5f-9ad5-8b097356bc9c spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:14:24Z" message: 'load-balancer-api-external: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.566429ms message: 'load-balancer-api-external: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 9.640856ms message: 'load-balancer-api-external: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:26:24Z" - latency: 5.450169ms message: 'load-balancer-api-external: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 9.038421ms message: 'load-balancer-api-external: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:25:24Z" - latency: 4.81389ms message: 'load-balancer-api-external: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 9.041083ms message: 'load-balancer-api-external: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:24Z" - latency: 4.600894ms message: 'load-balancer-api-external: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 10.068523ms message: 'load-balancer-api-external: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:24Z" - latency: 6.75052ms message: 'load-balancer-api-external: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 9.22752ms message: 'load-balancer-api-external: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "20185" uid: e2882841-e0c5-48c2-99b1-9313dda3c106 spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:14:24Z" message: 'load-balancer-api-internal: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.554392ms message: 'load-balancer-api-internal: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 9.611692ms message: 'load-balancer-api-internal: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:26:24Z" - latency: 4.995911ms message: 'load-balancer-api-internal: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 9.076358ms message: 'load-balancer-api-internal: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:25:24Z" - latency: 4.820854ms message: 'load-balancer-api-internal: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 9.026578ms message: 'load-balancer-api-internal: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:24Z" - latency: 4.6106ms message: 'load-balancer-api-internal: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 10.023503ms message: 'load-balancer-api-internal: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:24Z" - latency: 5.041216ms message: 'load-balancer-api-internal: tcp connection to aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 9.272027ms message: 'load-balancer-api-internal: resolved host name aec76c848ae544ad99c1e4993a391017-410c4d3af06d9a5d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-network-check-target-ip-10-0-129-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "21594" uid: 2ecd2255-bd68-4a12-9e21-949351205931 spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:15:24Z" message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383973ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:24Z" - latency: 2.336999ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:28:24Z" - latency: 2.391872ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:24Z" - latency: 2.342026ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 2.528907ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 2.246837ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 2.228273ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 2.206988ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 2.270643ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:24Z" - latency: 2.275246ms message: 'network-check-target-ip-10-0-129-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-network-check-target-ip-10-0-142-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "21593" uid: 38b3b880-fa4d-41c3-b294-a5b02a93f23f spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:15:24Z" message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.27797ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:24Z" - latency: 2.220359ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:28:24Z" - latency: 2.01655ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:24Z" - latency: 2.259911ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 2.279071ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 2.242941ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 2.299974ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 2.144943ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 2.43369ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:24Z" - latency: 2.248279ms message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-network-check-target-ip-10-0-143-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "21592" uid: 1589a2f7-7fc9-403f-b6f8-ef764479b1ef spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:15:24Z" message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.432993ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:24Z" - latency: 1.253363ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:28:24Z" - latency: 991.196µs message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:24Z" - latency: 1.277671ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 1.051036ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 960.662µs message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 1.0744ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 960.8µs message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 1.009809ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:24Z" - latency: 1.009239ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:08:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-68-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-68.ec2.internal uid: 291e1fa1-c337-4aaa-8f39-f642640eaf50 resourceVersion: "20184" uid: e640ec3b-a3ee-4209-b291-deb5e834ff39 spec: sourcePod: network-check-source-869dcfcdcd-mmn59 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T18:14:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.086µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:24Z" - latency: 1.775659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:26:24Z" - latency: 963.745µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:24Z" - latency: 1.693799ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:25:24Z" - latency: 935.406µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:24Z" - latency: 1.792785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:24Z" - latency: 949.363µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:24Z" - latency: 2.744365ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:24Z" - latency: 961.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:24Z" - latency: 1.905953ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:24Z" kind: List metadata: resourceVersion: ""