apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64530"
    uid: 30db73d3-e351-47da-ae01-e99fc79394a8
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:02:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.230601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 1.055841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 1.044868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 1.422784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 984.052µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 2.031443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:32:26Z"
    - latency: 729.807µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:31:26Z"
    - latency: 1.016207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:30:26Z"
    - latency: 1.192202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:29:26Z"
    - latency: 844.908µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64531"
    uid: 8e368901-90b9-4c47-9dc5-2f972b4f8808
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:01:26Z"
      message: 'load-balancer-api-external: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.312868ms
      message: 'load-balancer-api-external: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 14.31012ms
      message: 'load-balancer-api-external: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 6.644407ms
      message: 'load-balancer-api-external: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 9.389466ms
      message: 'load-balancer-api-external: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 5.160073ms
      message: 'load-balancer-api-external: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 9.383066ms
      message: 'load-balancer-api-external: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 4.917815ms
      message: 'load-balancer-api-external: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 7.913445ms
      message: 'load-balancer-api-external: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 6.211452ms
      message: 'load-balancer-api-external: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 9.185297ms
      message: 'load-balancer-api-external: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64532"
    uid: bca68a91-ec81-4b3a-9c5e-89a14a1775ae
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:01:26Z"
      message: 'load-balancer-api-internal: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.514183ms
      message: 'load-balancer-api-internal: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 14.40031ms
      message: 'load-balancer-api-internal: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 4.124619ms
      message: 'load-balancer-api-internal: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 9.228157ms
      message: 'load-balancer-api-internal: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 5.408224ms
      message: 'load-balancer-api-internal: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 9.202161ms
      message: 'load-balancer-api-internal: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 4.934705ms
      message: 'load-balancer-api-internal: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 8.049596ms
      message: 'load-balancer-api-internal: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 5.227382ms
      message: 'load-balancer-api-internal: tcp connection to aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 9.423648ms
      message: 'load-balancer-api-internal: resolved host name aa0c5ce4607434be0a013db87ba0f22a-cc7f18d9cd87e20b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-network-check-target-ip-10-0-132-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64528"
    uid: f6aee97b-1d57-4326-bbf8-589e30369561
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:02:26Z"
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.128862ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 2.151604ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 1.878419ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 2.533178ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 2.146318ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 2.067637ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:32:26Z"
    - latency: 1.847993ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:31:26Z"
    - latency: 2.154416ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:30:26Z"
    - latency: 2.08586ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:29:26Z"
    - latency: 2.195149ms
      message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-network-check-target-ip-10-0-143-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64527"
    uid: a147b394-8a7e-4106-8d71-b1701fe2c68d
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:02:26Z"
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.772903ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 2.432867ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 2.49179ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 2.737447ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 2.330452ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 2.352057ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:32:26Z"
    - latency: 2.152055ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:31:26Z"
    - latency: 2.610081ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:30:26Z"
    - latency: 2.276483ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:29:26Z"
    - latency: 2.257966ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-network-check-target-ip-10-0-143-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64526"
    uid: 5b4e6ac0-2fdb-4661-81e9-e4f701836f42
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:02:26Z"
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.645171ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 1.666337ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 1.671451ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 1.823034ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 1.359848ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 1.224904ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:32:26Z"
    - latency: 1.237031ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:31:26Z"
    - latency: 1.379126ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:30:26Z"
    - latency: 1.551933ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:29:26Z"
    - latency: 1.546036ms
      message: 'network-check-target-ip-10-0-143-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-78.ec2.internal
      uid: ed2b2b19-3b26-49fc-aec1-868868cba152
    resourceVersion: "64529"
    uid: ed58413f-c56d-44e7-9b30-294698f256ef
  spec:
    sourcePod: network-check-source-7d88cb55d8-6g78k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T23:01:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.524868ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 2.367133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:37:26Z"
    - latency: 769.909µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 2.577786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:36:26Z"
    - latency: 1.085041ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 2.619205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:35:26Z"
    - latency: 951.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 2.078444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:34:26Z"
    - latency: 1.305112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:33:26Z"
    - latency: 1.97858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:33:26Z"
kind: List
metadata:
  resourceVersion: ""