apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "53359" uid: 40eeea90-5ed6-45e7-ab2b-c3c15ed0e4c7 spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T17:50:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 1.020858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 1.083769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 1.010123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 1.045368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:35Z" - latency: 1.048442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:35Z" - latency: 861.889µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:35Z" - latency: 815.171µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:35Z" - latency: 807.657µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:10:35Z" - latency: 830.866µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "54252" uid: 6baa32f2-41f9-4f7e-ab6a-54ef16c4f76e spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T17:49:35Z" message: 'load-balancer-api-external: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.98501ms message: 'load-balancer-api-external: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:35Z" - latency: 7.807061ms message: 'load-balancer-api-external: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:19:35Z" - latency: 5.132388ms message: 'load-balancer-api-external: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 9.016173ms message: 'load-balancer-api-external: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:18:35Z" - latency: 4.265282ms message: 'load-balancer-api-external: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 6.607538ms message: 'load-balancer-api-external: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:17:35Z" - latency: 4.277911ms message: 'load-balancer-api-external: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 6.801366ms message: 'load-balancer-api-external: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:16:35Z" - latency: 4.759302ms message: 'load-balancer-api-external: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 6.625603ms message: 'load-balancer-api-external: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:15:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "54251" uid: 82113de4-5bb5-44e0-9aba-8f41b1052f9a spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T17:49:35Z" message: 'load-balancer-api-internal: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.859525ms message: 'load-balancer-api-internal: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:35Z" - latency: 7.893034ms message: 'load-balancer-api-internal: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:19:35Z" - latency: 5.145685ms message: 'load-balancer-api-internal: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 9.084602ms message: 'load-balancer-api-internal: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:18:35Z" - latency: 4.472454ms message: 'load-balancer-api-internal: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 6.670011ms message: 'load-balancer-api-internal: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:17:35Z" - latency: 5.021584ms message: 'load-balancer-api-internal: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 6.752552ms message: 'load-balancer-api-internal: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:16:35Z" - latency: 4.506219ms message: 'load-balancer-api-internal: tcp connection to a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 6.610875ms message: 'load-balancer-api-internal: resolved host name a5ea12f05ea974ad08c8b88f2df1d48e-3a4563a9119ec077.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:15:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-129-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "53357" uid: 9141d4a0-14a4-45b0-a365-c7f84756b10f spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:50:35Z" message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.183667ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 806.378µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 821.221µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 1.175227ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 1.445265ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:35Z" - latency: 1.228838ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:35Z" - latency: 706.444µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:35Z" - latency: 851.515µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:35Z" - latency: 890.468µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:10:35Z" - latency: 994.867µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-139-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "53356" uid: 0224d523-7899-49f8-a7c4-4eccbd758f22 spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:50:35Z" message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.81729ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 1.736563ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 1.834573ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 2.177264ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 1.560639ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:35Z" - latency: 1.799672ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:35Z" - latency: 1.963279ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:35Z" - latency: 1.689748ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:35Z" - latency: 1.563775ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:10:35Z" - latency: 1.819735ms message: 'network-check-target-ip-10-0-139-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-143-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "53358" uid: 93d25ecf-bac4-49a5-8b34-d144f338a42c spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:50:35Z" message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.054364ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 2.284887ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 2.19489ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 2.435076ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 2.225187ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:35Z" - latency: 2.221057ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:35Z" - latency: 2.195681ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:35Z" - latency: 2.002388ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:35Z" - latency: 2.465425ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:10:35Z" - latency: 2.099464ms message: 'network-check-target-ip-10-0-143-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:43:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: a6f3ae3d-9caf-4b6d-a5cc-4db72dc79c7f resourceVersion: "54250" uid: 2e99be42-ad88-4378-9b7f-247c34804683 spec: sourcePod: network-check-source-989f8b8dc-8ddzc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T17:49:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 835.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:35Z" - latency: 1.703597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:19:35Z" - latency: 820.655µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:35Z" - latency: 1.884155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:18:35Z" - latency: 1.052675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:35Z" - latency: 1.596083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:17:35Z" - latency: 896.928µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:35Z" - latency: 1.770306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:16:35Z" - latency: 823.922µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:35Z" - latency: 1.72352ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:15:35Z" kind: List metadata: resourceVersion: ""