apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "25797"
    uid: 575f6107-a076-47e5-82d7-b3fb864756f5
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:29:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.40961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:50:49Z"
    - latency: 997.706µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:49:49Z"
    - latency: 1.100917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:48:49Z"
    - latency: 1.093625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:47:49Z"
    - latency: 1.229009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 918.814µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 1.276162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 865.539µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 823.79µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 972.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "23381"
    uid: 32c39046-99e4-4cd4-a583-40b080903aed
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:28:49Z"
      message: 'load-balancer-api-external: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.88933ms
      message: 'load-balancer-api-external: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 6.559223ms
      message: 'load-balancer-api-external: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 3.382329ms
      message: 'load-balancer-api-external: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 7.473479ms
      message: 'load-balancer-api-external: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 5.479932ms
      message: 'load-balancer-api-external: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 7.03557ms
      message: 'load-balancer-api-external: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 4.48333ms
      message: 'load-balancer-api-external: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 6.975561ms
      message: 'load-balancer-api-external: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 5.409688ms
      message: 'load-balancer-api-external: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 8.42439ms
      message: 'load-balancer-api-external: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "23380"
    uid: aded40cb-4e26-4b82-827f-32b76cb2ee0a
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:28:49Z"
      message: 'load-balancer-api-internal: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.068411ms
      message: 'load-balancer-api-internal: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 6.750456ms
      message: 'load-balancer-api-internal: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 5.309494ms
      message: 'load-balancer-api-internal: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 7.588399ms
      message: 'load-balancer-api-internal: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 5.027468ms
      message: 'load-balancer-api-internal: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 7.017444ms
      message: 'load-balancer-api-internal: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 5.285853ms
      message: 'load-balancer-api-internal: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 7.093594ms
      message: 'load-balancer-api-internal: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 5.90694ms
      message: 'load-balancer-api-internal: tcp connection to ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 8.473085ms
      message: 'load-balancer-api-internal: resolved host name ac0ce2cbc99b64922b2c28e41d8e5b5b-8d1797e74ecc9869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-132-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "25794"
    uid: 08567cd9-585d-4b48-b508-2e3a87ad0b5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:29:49Z"
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148601ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:50:49Z"
    - latency: 862.802µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:49:49Z"
    - latency: 897.631µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:48:49Z"
    - latency: 888.73µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:47:49Z"
    - latency: 869.532µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 951.116µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 937.787µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 924.3µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 777.172µs
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 1.024971ms
      message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-132-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "25795"
    uid: b2c07a1e-1810-4987-ab68-b070f4c3fb79
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:29:49Z"
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.036575ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:50:49Z"
    - latency: 1.963047ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:49:49Z"
    - latency: 1.831127ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:48:49Z"
    - latency: 1.792628ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:47:49Z"
    - latency: 2.156151ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 1.917345ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 1.799811ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 1.799048ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 1.776084ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 5.247125ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-133-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "25796"
    uid: 574dbd2f-db0d-4d69-81b0-69bb7d0bbb68
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:29:49Z"
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.764435ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:50:49Z"
    - latency: 1.821588ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:49:49Z"
    - latency: 1.79617ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:48:49Z"
    - latency: 1.712458ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:47:49Z"
    - latency: 2.203976ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 1.663273ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 1.723659ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 1.974927ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 1.681184ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 1.643071ms
      message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:22:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-134.ec2.internal
      uid: edb68a86-fb4d-476e-ab6e-1449fefb3b61
    resourceVersion: "23379"
    uid: 77bb0117-b9f0-4b22-afae-6757381ef9ab
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6zsk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:28:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.907µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 1.823001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:46:49Z"
    - latency: 843.949µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 1.752065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:49Z"
    - latency: 770.822µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 1.968022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:49Z"
    - latency: 790.146µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 1.71497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:49Z"
    - latency: 908.213µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:49Z"
    - latency: 1.79556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:49Z"
kind: List
metadata:
  resourceVersion: ""