apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52895"
    uid: c84d9786-7164-4ea6-960b-118cb6347479
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.126231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 1.26235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 1.172395ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 1.604973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 1.590093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 998.511µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:02Z"
    - latency: 1.149515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:02Z"
    - latency: 1.047944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:02Z"
    - latency: 1.091332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:28:02Z"
    - latency: 1.078832ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52897"
    uid: 7cd3420c-148f-4b0c-ab55-a71938083356
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:02Z"
      message: 'load-balancer-api-external: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.42705ms
      message: 'load-balancer-api-external: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 9.480324ms
      message: 'load-balancer-api-external: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 6.938798ms
      message: 'load-balancer-api-external: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 9.123778ms
      message: 'load-balancer-api-external: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 4.529485ms
      message: 'load-balancer-api-external: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 7.765185ms
      message: 'load-balancer-api-external: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 5.242977ms
      message: 'load-balancer-api-external: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 8.225802ms
      message: 'load-balancer-api-external: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 6.864199ms
      message: 'load-balancer-api-external: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 8.90899ms
      message: 'load-balancer-api-external: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52898"
    uid: 5809a4b5-fc3e-4ac6-9661-437ca8ea9399
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:02Z"
      message: 'load-balancer-api-internal: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.445673ms
      message: 'load-balancer-api-internal: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 9.52703ms
      message: 'load-balancer-api-internal: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 7.211066ms
      message: 'load-balancer-api-internal: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 9.054909ms
      message: 'load-balancer-api-internal: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 4.521899ms
      message: 'load-balancer-api-internal: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 7.823614ms
      message: 'load-balancer-api-internal: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 5.239517ms
      message: 'load-balancer-api-internal: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 8.277775ms
      message: 'load-balancer-api-internal: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 6.904845ms
      message: 'load-balancer-api-internal: tcp connection to ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 9.02357ms
      message: 'load-balancer-api-internal: resolved host name ac64437e41cec4cd9a03ec572c527f29-454a7748e9de666d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-network-check-target-ip-10-0-134-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52892"
    uid: e04e138b-3c42-45dd-81f0-b7e3039bb135
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:02Z"
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382111ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 2.243478ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 2.21831ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 2.407332ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 2.172536ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 2.185676ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:02Z"
    - latency: 2.252851ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:02Z"
    - latency: 2.430647ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:02Z"
    - latency: 2.253354ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:28:02Z"
    - latency: 1.846381ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-network-check-target-ip-10-0-138-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52893"
    uid: 804a4134-bb1d-410d-ae35-0828539f970c
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:02Z"
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.147702ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 2.159419ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 2.242708ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 2.367817ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 2.16883ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 2.320345ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:02Z"
    - latency: 2.009991ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:02Z"
    - latency: 2.378721ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:02Z"
    - latency: 2.167208ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:28:02Z"
    - latency: 2.44889ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-network-check-target-ip-10-0-139-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52891"
    uid: eb5833c1-d0ab-41a0-b743-91d91f0717bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:02Z"
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.777µs
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 859.877µs
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 942.988µs
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 1.725541ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 746.367µs
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 998.972µs
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:31:02Z"
    - latency: 1.253965ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:30:02Z"
    - latency: 1.357702ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:29:02Z"
    - latency: 1.44525ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:28:02Z"
    - latency: 811.975µs
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:12:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-15-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-15.ec2.internal
      uid: 27ff229c-16f7-4666-b4f8-eede14b30c9d
    resourceVersion: "52894"
    uid: 121ec781-c4ed-4625-931f-886cf38b9204
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkq8d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.208µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 2.355218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:36:02Z"
    - latency: 1.123301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 2.162338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:35:02Z"
    - latency: 981.71µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 1.738708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:34:02Z"
    - latency: 903.901µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 1.502321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:33:02Z"
    - latency: 1.308088ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:32:02Z"
    - latency: 2.004574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:32:02Z"
kind: List
metadata:
  resourceVersion: ""