apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "54350"
    uid: 7ca2bf33-e192-47ea-b352-9d9ff51f25a0
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:08:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.27041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 970.133µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 1.452388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 1.202042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:51Z"
    - latency: 1.070926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:25:51Z"
    - latency: 1.004308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:24:51Z"
    - latency: 971.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:23:51Z"
    - latency: 997.133µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:22:51Z"
    - latency: 860.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:21:51Z"
    - latency: 873.256µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "56087"
    uid: 40b8abb6-dcdd-4aab-b080-2d0642cc719e
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:07:51Z"
      message: 'load-balancer-api-external: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.361786ms
      message: 'load-balancer-api-external: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:51Z"
    - latency: 8.115526ms
      message: 'load-balancer-api-external: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:31:51Z"
    - latency: 5.441383ms
      message: 'load-balancer-api-external: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:51Z"
    - latency: 9.467288ms
      message: 'load-balancer-api-external: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:30:51Z"
    - latency: 7.030222ms
      message: 'load-balancer-api-external: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 8.701685ms
      message: 'load-balancer-api-external: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 4.64918ms
      message: 'load-balancer-api-external: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 7.914874ms
      message: 'load-balancer-api-external: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 4.036614ms
      message: 'load-balancer-api-external: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 9.585914ms
      message: 'load-balancer-api-external: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "56088"
    uid: 31415961-c183-472f-a8ff-d0413f500dd1
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:07:51Z"
      message: 'load-balancer-api-internal: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.330324ms
      message: 'load-balancer-api-internal: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:51Z"
    - latency: 8.233104ms
      message: 'load-balancer-api-internal: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:31:51Z"
    - latency: 4.421963ms
      message: 'load-balancer-api-internal: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:51Z"
    - latency: 9.575922ms
      message: 'load-balancer-api-internal: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:30:51Z"
    - latency: 9.435769ms
      message: 'load-balancer-api-internal: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 8.804808ms
      message: 'load-balancer-api-internal: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 4.102506ms
      message: 'load-balancer-api-internal: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 7.888781ms
      message: 'load-balancer-api-internal: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 3.985642ms
      message: 'load-balancer-api-internal: tcp connection to aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 9.675192ms
      message: 'load-balancer-api-internal: resolved host name aea52c6f41d6a4de3988eab08d45dd5a-17243d1278ba3b1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-network-check-target-ip-10-0-131-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "54349"
    uid: c1a08b4d-baac-493d-adc2-b8956eee9bf8
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:08:51Z"
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.629273ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 2.283193ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 2.488337ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 3.041507ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:51Z"
    - latency: 2.198513ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:25:51Z"
    - latency: 2.605899ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:24:51Z"
    - latency: 2.330286ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:23:51Z"
    - latency: 2.033166ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:22:51Z"
    - latency: 2.250477ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:21:51Z"
    - latency: 2.552031ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-network-check-target-ip-10-0-132-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "54347"
    uid: 625ec875-3359-4358-b322-81490565c9a5
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:08:51Z"
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.44543ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 897.177µs
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 1.121336ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 1.007975ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:51Z"
    - latency: 1.112685ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:25:51Z"
    - latency: 1.07922ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:24:51Z"
    - latency: 914.921µs
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:23:51Z"
    - latency: 1.014754ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:22:51Z"
    - latency: 1.198161ms
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:21:51Z"
    - latency: 872.706µs
      message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-network-check-target-ip-10-0-142-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "54348"
    uid: e7618709-138c-489a-8c91-ebb3f2370608
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:08:51Z"
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.369982ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 2.312991ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 2.414564ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 2.374252ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:51Z"
    - latency: 2.434165ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:25:51Z"
    - latency: 2.468556ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:24:51Z"
    - latency: 2.319368ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:23:51Z"
    - latency: 2.232548ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:22:51Z"
    - latency: 2.223924ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:21:51Z"
    - latency: 2.304631ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-162.ec2.internal
      uid: b09fad77-5692-4a91-8315-cf42aabc1acb
    resourceVersion: "56086"
    uid: 7fcff42d-4d1b-4422-a4b0-c6ffe04c64bb
  spec:
    sourcePod: network-check-source-685456655f-8r5dv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:07:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 735.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:51Z"
    - latency: 1.741523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:31:51Z"
    - latency: 942.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:51Z"
    - latency: 2.081076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:30:51Z"
    - latency: 908.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 1.874435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:29:51Z"
    - latency: 843.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 2.218634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:28:51Z"
    - latency: 763.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:51Z"
    - latency: 1.874846ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:27:51Z"
kind: List
metadata:
  resourceVersion: ""