apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "55228"
    uid: dcc8143a-2c94-42a6-a1de-5a28d1656ad7
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:51:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.427µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 1.423543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 1.069707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 1.149161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:10Z"
    - latency: 1.268024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:15:10Z"
    - latency: 1.195341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:14:10Z"
    - latency: 1.184119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:13:10Z"
    - latency: 1.111724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:12:10Z"
    - latency: 1.164633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:11:10Z"
    - latency: 792.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:10:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "56153"
    uid: 70642e1d-a0dc-4be4-af0d-2ce9de7b6f8f
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:50:11Z"
      message: 'load-balancer-api-external: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.338499ms
      message: 'load-balancer-api-external: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:20:11Z"
    - latency: 7.142908ms
      message: 'load-balancer-api-external: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:20:10Z"
    - latency: 3.97977ms
      message: 'load-balancer-api-external: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:11Z"
    - latency: 6.993012ms
      message: 'load-balancer-api-external: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 3.737942ms
      message: 'load-balancer-api-external: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:11Z"
    - latency: 6.736919ms
      message: 'load-balancer-api-external: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 5.190332ms
      message: 'load-balancer-api-external: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:11Z"
    - latency: 7.984375ms
      message: 'load-balancer-api-external: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 4.124758ms
      message: 'load-balancer-api-external: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:11Z"
    - latency: 6.860062ms
      message: 'load-balancer-api-external: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:16:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "56154"
    uid: 43ada1e7-a49b-45cb-8b2d-637ae47ffd91
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:50:11Z"
      message: 'load-balancer-api-internal: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.364028ms
      message: 'load-balancer-api-internal: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:20:11Z"
    - latency: 7.195555ms
      message: 'load-balancer-api-internal: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:20:10Z"
    - latency: 3.883047ms
      message: 'load-balancer-api-internal: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:11Z"
    - latency: 6.92736ms
      message: 'load-balancer-api-internal: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 3.702002ms
      message: 'load-balancer-api-internal: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:11Z"
    - latency: 6.753807ms
      message: 'load-balancer-api-internal: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 5.176867ms
      message: 'load-balancer-api-internal: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:11Z"
    - latency: 7.934474ms
      message: 'load-balancer-api-internal: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 4.123777ms
      message: 'load-balancer-api-internal: tcp connection to a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:11Z"
    - latency: 6.969554ms
      message: 'load-balancer-api-internal: resolved host name a8f1d0ed52ec340688bb2cba40bd4ab6-c56c05059c9e08f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:16:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-network-check-target-ip-10-0-130-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "55227"
    uid: 58403f40-c9c8-41f5-b215-09c625f13393
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:51:11Z"
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.375114ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 2.287422ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 2.4284ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 3.004957ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:10Z"
    - latency: 2.288638ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:15:10Z"
    - latency: 2.353639ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:14:10Z"
    - latency: 2.304335ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:13:10Z"
    - latency: 1.983192ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:12:10Z"
    - latency: 2.191608ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:11:10Z"
    - latency: 2.397084ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:10:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-network-check-target-ip-10-0-131-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "55225"
    uid: 97c86785-7388-4947-9aca-130b85bb2f2a
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:51:10Z"
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009394ms
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 1.07478ms
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 1.01513ms
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 901.484µs
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:10Z"
    - latency: 995.299µs
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:15:10Z"
    - latency: 890.516µs
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:14:10Z"
    - latency: 1.396786ms
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:13:10Z"
    - latency: 1.15911ms
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:12:10Z"
    - latency: 889.732µs
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:11:10Z"
    - latency: 1.295824ms
      message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:10:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-network-check-target-ip-10-0-137-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "55226"
    uid: 4ba3029b-0701-4dc7-9800-83a07a0c779b
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:51:11Z"
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.978252ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 1.678876ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 2.311291ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 2.476331ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:10Z"
    - latency: 2.147251ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:15:10Z"
    - latency: 2.032873ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:14:10Z"
    - latency: 1.790534ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:13:10Z"
    - latency: 2.366522ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:12:10Z"
    - latency: 1.80162ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:11:10Z"
    - latency: 2.053449ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:10:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T13:44:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-215.ec2.internal
      uid: 7627268d-c6ee-494f-92be-59631b713e9e
    resourceVersion: "56152"
    uid: ff3bc146-970a-44c3-87d1-fa497a06347b
  spec:
    sourcePod: network-check-source-869dcfcdcd-fqnvh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T13:50:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.34µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:20:10Z"
    - latency: 1.83812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:20:10Z"
    - latency: 1.170138ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 1.815641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:19:10Z"
    - latency: 1.087587ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 1.812891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:18:10Z"
    - latency: 991.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:17:11Z"
    - latency: 2.351389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:17:10Z"
    - latency: 861.005µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T14:16:10Z"
    - latency: 1.825053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T14:16:10Z"
kind: List
metadata:
  resourceVersion: ""