apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "58730"
    uid: acb57bb5-6334-4386-b74a-fc7b230b922e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.122257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:42:03Z"
    - latency: 889.223µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:41:03Z"
    - latency: 1.140912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:03Z"
    - latency: 970.851µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:03Z"
    - latency: 1.1004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:03Z"
    - latency: 1.138338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:03Z"
    - latency: 866.979µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:03Z"
    - latency: 949.542µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:03Z"
    - latency: 1.091193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:03Z"
    - latency: 1.078368ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "63497"
    uid: ee2dcd72-535c-44dd-b515-e1458a25792e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:59:03Z"
      message: 'load-balancer-api-external: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.232004ms
      message: 'load-balancer-api-external: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:47:03Z"
    - latency: 8.057231ms
      message: 'load-balancer-api-external: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:47:03Z"
    - latency: 6.211182ms
      message: 'load-balancer-api-external: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:46:03Z"
    - latency: 14.600811ms
      message: 'load-balancer-api-external: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:46:03Z"
    - latency: 5.492411ms
      message: 'load-balancer-api-external: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:45:03Z"
    - latency: 6.640623ms
      message: 'load-balancer-api-external: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:45:03Z"
    - latency: 3.666709ms
      message: 'load-balancer-api-external: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:44:03Z"
    - latency: 6.098175ms
      message: 'load-balancer-api-external: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:44:03Z"
    - latency: 4.565328ms
      message: 'load-balancer-api-external: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:43:03Z"
    - latency: 7.97008ms
      message: 'load-balancer-api-external: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:43:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "63496"
    uid: 18576eed-820b-488d-87fb-b1100c975422
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:59:03Z"
      message: 'load-balancer-api-internal: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.955375ms
      message: 'load-balancer-api-internal: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:47:03Z"
    - latency: 7.980554ms
      message: 'load-balancer-api-internal: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:47:03Z"
    - latency: 5.373204ms
      message: 'load-balancer-api-internal: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:46:03Z"
    - latency: 15.900202ms
      message: 'load-balancer-api-internal: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:46:03Z"
    - latency: 5.482961ms
      message: 'load-balancer-api-internal: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:45:03Z"
    - latency: 6.666806ms
      message: 'load-balancer-api-internal: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:45:03Z"
    - latency: 4.476847ms
      message: 'load-balancer-api-internal: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:44:03Z"
    - latency: 6.044483ms
      message: 'load-balancer-api-internal: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:44:03Z"
    - latency: 4.551562ms
      message: 'load-balancer-api-internal: tcp connection to a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:43:03Z"
    - latency: 8.003668ms
      message: 'load-balancer-api-internal: resolved host name a36f5da4646984f5386175b94133daa6-f91f535aa75d8200.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:43:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-ip-10-0-135-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "58728"
    uid: b344f34f-058a-43e2-8bef-b93b9a0ceb9d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:03Z"
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.878417ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:42:03Z"
    - latency: 1.754622ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:41:03Z"
    - latency: 2.104883ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:03Z"
    - latency: 2.109834ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:03Z"
    - latency: 1.980207ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:03Z"
    - latency: 1.98108ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:03Z"
    - latency: 1.811956ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:03Z"
    - latency: 1.87968ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:03Z"
    - latency: 2.011503ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:03Z"
    - latency: 2.081752ms
      message: 'network-check-target-ip-10-0-135-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-ip-10-0-136-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "58729"
    uid: 5680d01e-2e48-4ead-9966-669f372909ab
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:03Z"
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391622ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:42:03Z"
    - latency: 2.34367ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:41:03Z"
    - latency: 2.556186ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:03Z"
    - latency: 2.300684ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:03Z"
    - latency: 3.175469ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:03Z"
    - latency: 2.385876ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:03Z"
    - latency: 2.446566ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:03Z"
    - latency: 2.388378ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:03Z"
    - latency: 2.399011ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:03Z"
    - latency: 2.35023ms
      message: 'network-check-target-ip-10-0-136-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-ip-10-0-143-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "58727"
    uid: 0d8554c5-a67d-4846-b4b8-60e90784eb0e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:03Z"
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.853µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:42:03Z"
    - latency: 955.985µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:41:03Z"
    - latency: 956.133µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:03Z"
    - latency: 1.274358ms
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:03Z"
    - latency: 838.8µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:03Z"
    - latency: 855.805µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:03Z"
    - latency: 980.069µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:03Z"
    - latency: 990.21µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:03Z"
    - latency: 864.406µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:03Z"
    - latency: 895.308µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: efd5ec24-922e-473e-a680-7915be1fdde8
    resourceVersion: "63495"
    uid: cc0b51f9-ad34-417b-8589-e708159ca4a1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zc2c6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:59:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.664µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:47:03Z"
    - latency: 1.859959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:47:03Z"
    - latency: 746.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:46:03Z"
    - latency: 9.294798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:46:03Z"
    - latency: 1.010027ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:45:03Z"
    - latency: 1.599705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:45:03Z"
    - latency: 1.079111ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:44:03Z"
    - latency: 1.861401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:44:03Z"
    - latency: 768.597µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:43:03Z"
    - latency: 1.67409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:43:03Z"
kind: List
metadata:
  resourceVersion: ""