apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "19415" uid: 01cc4695-ca43-416c-8bc3-fd7cad404bd9 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:45:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.074411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:16Z" - latency: 835.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:16Z" - latency: 1.233071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 827.031µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 1.761563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 1.305477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 788.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 1.051819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:16Z" - latency: 1.05745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:16Z" - latency: 1.44007ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "18484" uid: 649d22f2-ea56-4974-8c37-567e9052d748 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:44:16Z" message: 'load-balancer-api-external: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.478678ms message: 'load-balancer-api-external: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 7.615771ms message: 'load-balancer-api-external: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:50:16Z" - latency: 5.03293ms message: 'load-balancer-api-external: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 8.663813ms message: 'load-balancer-api-external: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:49:16Z" - latency: 4.802477ms message: 'load-balancer-api-external: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 8.133584ms message: 'load-balancer-api-external: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:48:16Z" - latency: 4.690657ms message: 'load-balancer-api-external: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 8.62585ms message: 'load-balancer-api-external: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:47:16Z" - latency: 4.494146ms message: 'load-balancer-api-external: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 7.582364ms message: 'load-balancer-api-external: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:46:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "18485" uid: 0671805b-395e-465c-9513-4ccaf4705ec4 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:44:16Z" message: 'load-balancer-api-internal: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.462676ms message: 'load-balancer-api-internal: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 7.599804ms message: 'load-balancer-api-internal: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:50:16Z" - latency: 5.014299ms message: 'load-balancer-api-internal: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 8.593677ms message: 'load-balancer-api-internal: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:49:16Z" - latency: 4.846574ms message: 'load-balancer-api-internal: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 8.04114ms message: 'load-balancer-api-internal: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:48:16Z" - latency: 3.790972ms message: 'load-balancer-api-internal: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 8.698448ms message: 'load-balancer-api-internal: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:47:16Z" - latency: 3.882527ms message: 'load-balancer-api-internal: tcp connection to a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 7.71183ms message: 'load-balancer-api-internal: resolved host name a57a5cde5b83e48e096d1c4fc7950e16-53d8219c0239a4df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:46:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-ip-10-0-129-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "19412" uid: f332b811-e130-4dbc-a279-1df02bc1f540 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:45:16Z" message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.138µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:16Z" - latency: 723.754µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:16Z" - latency: 886.812µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 1.168225ms message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 1.184621ms message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 968.112µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 1.572202ms message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 1.302876ms message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:16Z" - latency: 943.385µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:16Z" - latency: 784.077µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-ip-10-0-140-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "19413" uid: 4cb4ddc0-f307-47c1-9864-0100f9861e26 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:45:16Z" message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.190228ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:16Z" - latency: 1.973108ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:16Z" - latency: 2.014934ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 2.137587ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 1.982456ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 2.184193ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 2.210104ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 2.362108ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:16Z" - latency: 1.890588ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:16Z" - latency: 2.317334ms message: 'network-check-target-ip-10-0-140-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-ip-10-0-142-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "19414" uid: 937f45f4-bdc5-43e7-878a-9d72679ce755 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:45:16Z" message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.117977ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:16Z" - latency: 2.22109ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:16Z" - latency: 2.18769ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 2.009647ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 2.18992ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 2.160656ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 2.302625ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 2.274755ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:16Z" - latency: 2.307551ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:16Z" - latency: 2.221143ms message: 'network-check-target-ip-10-0-142-225: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:38:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 00cc161f-a7fe-42c3-839f-4fe23887705c resourceVersion: "18483" uid: a714a27a-40a2-4a80-9a8f-10819f54a0e7 spec: sourcePod: network-check-source-7b678d77c7-lfln6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:44:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.568µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:16Z" - latency: 2.007086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:50:16Z" - latency: 931.672µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:16Z" - latency: 1.995128ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:49:16Z" - latency: 886.77µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:16Z" - latency: 1.990517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:48:16Z" - latency: 813.522µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:16Z" - latency: 1.859809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:47:16Z" - latency: 960.97µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:16Z" - latency: 1.823431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:46:16Z" kind: List metadata: resourceVersion: ""