apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "48702"
    uid: 28d690d8-a46f-4dc0-b908-45362f1f5bba
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.111133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 814.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 972.737µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 985.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:10Z"
    - latency: 1.09466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:10Z"
    - latency: 895.61µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:10Z"
    - latency: 833.156µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:10Z"
    - latency: 841.979µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:10Z"
    - latency: 919.71µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:10Z"
    - latency: 1.164121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "49933"
    uid: ae932b3e-2959-43ff-9697-13f4954083b9
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:10:10Z"
      message: 'load-balancer-api-external: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.496784ms
      message: 'load-balancer-api-external: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:34:10Z"
    - latency: 7.115276ms
      message: 'load-balancer-api-external: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:34:10Z"
    - latency: 5.090606ms
      message: 'load-balancer-api-external: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:33:10Z"
    - latency: 6.705528ms
      message: 'load-balancer-api-external: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:33:10Z"
    - latency: 3.347274ms
      message: 'load-balancer-api-external: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 6.988108ms
      message: 'load-balancer-api-external: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 8.202657ms
      message: 'load-balancer-api-external: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 7.140179ms
      message: 'load-balancer-api-external: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 5.755827ms
      message: 'load-balancer-api-external: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 7.15147ms
      message: 'load-balancer-api-external: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "49934"
    uid: 17342815-e5ec-442a-baa9-1cc22540de3f
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:10:10Z"
      message: 'load-balancer-api-internal: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.322065ms
      message: 'load-balancer-api-internal: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:34:10Z"
    - latency: 7.14672ms
      message: 'load-balancer-api-internal: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:34:10Z"
    - latency: 4.310397ms
      message: 'load-balancer-api-internal: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:33:10Z"
    - latency: 6.777188ms
      message: 'load-balancer-api-internal: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:33:10Z"
    - latency: 4.203565ms
      message: 'load-balancer-api-internal: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 7.052246ms
      message: 'load-balancer-api-internal: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 8.189616ms
      message: 'load-balancer-api-internal: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 7.227036ms
      message: 'load-balancer-api-internal: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 4.217336ms
      message: 'load-balancer-api-internal: tcp connection to af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 7.208672ms
      message: 'load-balancer-api-internal: resolved host name af06a7420d3144cd9ba9cdb03ad9ba9e-b2b361fbb8d6f446.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-ip-10-0-128-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "48701"
    uid: 88ebce8b-f44c-4b6a-b19a-37b6e39c4d83
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:10Z"
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.194849ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 1.980671ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 2.355509ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 2.38858ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:10Z"
    - latency: 2.056107ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:10Z"
    - latency: 2.33856ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:10Z"
    - latency: 2.256404ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:10Z"
    - latency: 2.502989ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:10Z"
    - latency: 2.217964ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:10Z"
    - latency: 2.357204ms
      message: 'network-check-target-ip-10-0-128-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-ip-10-0-142-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "48700"
    uid: 8935c8ae-7d28-4cbc-8d77-35110f136d34
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:10Z"
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.893744ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 1.984757ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 1.821672ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 1.92866ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:10Z"
    - latency: 2.055936ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:10Z"
    - latency: 1.828988ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:10Z"
    - latency: 2.198427ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:10Z"
    - latency: 1.952199ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:10Z"
    - latency: 1.989326ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:10Z"
    - latency: 2.26882ms
      message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-ip-10-0-142-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "48699"
    uid: cee89bf6-b413-47db-8faa-93f5e69f35d9
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:11:10Z"
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.384µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 913.605µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 1.145158ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 912.692µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:29:10Z"
    - latency: 877.309µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:28:10Z"
    - latency: 1.124879ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:10Z"
    - latency: 1.061114ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:10Z"
    - latency: 1.077119ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:10Z"
    - latency: 1.158183ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:10Z"
    - latency: 1.391743ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:04:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 2de223e3-fe56-4ed4-a858-c1331a94897a
    resourceVersion: "49931"
    uid: cb6aa481-c460-4421-a86c-d15383d874ce
  spec:
    sourcePod: network-check-source-685456655f-pjqqn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:10:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.443µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:34:10Z"
    - latency: 1.858343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:34:10Z"
    - latency: 874.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:33:10Z"
    - latency: 1.69132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:33:10Z"
    - latency: 807.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 1.765665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:32:10Z"
    - latency: 736.61µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 2.238227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:31:10Z"
    - latency: 846.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:30:10Z"
    - latency: 1.94462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:30:10Z"
kind: List
metadata:
  resourceVersion: ""