apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "68490"
    uid: 5c91f7cc-e516-4ac0-9411-774a1c4331a9
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:41:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.35848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 1.463058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 1.051249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 1.103791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 983.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:05:19Z"
    - latency: 1.529184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:04:19Z"
    - latency: 1.129087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:03:19Z"
    - latency: 1.01426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:02:19Z"
    - latency: 1.169494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:01:19Z"
    - latency: 1.128335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "69578"
    uid: 2582a311-a9f2-4c63-a641-e7c976f85124
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:40:19Z"
      message: 'load-balancer-api-external: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.934742ms
      message: 'load-balancer-api-external: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:10:19Z"
    - latency: 8.467665ms
      message: 'load-balancer-api-external: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:10:19Z"
    - latency: 4.385049ms
      message: 'load-balancer-api-external: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 8.98751ms
      message: 'load-balancer-api-external: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 3.695367ms
      message: 'load-balancer-api-external: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 9.302887ms
      message: 'load-balancer-api-external: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 5.626837ms
      message: 'load-balancer-api-external: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 8.940924ms
      message: 'load-balancer-api-external: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 5.270759ms
      message: 'load-balancer-api-external: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 8.104005ms
      message: 'load-balancer-api-external: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:06:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "69577"
    uid: 57408772-0a37-4d50-b7e6-8b4d130ae990
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:40:19Z"
      message: 'load-balancer-api-internal: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.273655ms
      message: 'load-balancer-api-internal: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:10:19Z"
    - latency: 8.378915ms
      message: 'load-balancer-api-internal: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:10:19Z"
    - latency: 4.380004ms
      message: 'load-balancer-api-internal: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 8.902239ms
      message: 'load-balancer-api-internal: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 5.637631ms
      message: 'load-balancer-api-internal: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 9.157553ms
      message: 'load-balancer-api-internal: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 5.455898ms
      message: 'load-balancer-api-internal: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 8.871503ms
      message: 'load-balancer-api-internal: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 5.259687ms
      message: 'load-balancer-api-internal: tcp connection to a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 8.141745ms
      message: 'load-balancer-api-internal: resolved host name a67328a6179a2424383a74e251d35627-d282906355a371f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:06:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-137-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "68489"
    uid: cb3d208f-d76e-48ac-bc46-e2991f68dd6e
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:41:19Z"
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.527439ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 2.524427ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 2.372546ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 2.465287ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 2.359369ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:05:19Z"
    - latency: 2.67265ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:04:19Z"
    - latency: 2.264607ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:03:19Z"
    - latency: 2.418373ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:02:19Z"
    - latency: 2.490463ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:01:19Z"
    - latency: 2.148273ms
      message: 'network-check-target-ip-10-0-137-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-141-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "68487"
    uid: 57054c6f-de50-47a7-b7d6-6976cf5b941e
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:41:19Z"
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027444ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 1.361966ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 968.942µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 1.395689ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 938.431µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:05:19Z"
    - latency: 964.942µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:04:19Z"
    - latency: 1.077784ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:03:19Z"
    - latency: 1.026234ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:02:19Z"
    - latency: 965.598µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:01:19Z"
    - latency: 1.002354ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-142-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "68488"
    uid: 049793ce-2010-4839-a103-215d859c4225
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:41:19Z"
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330631ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 2.40006ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 2.83464ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 2.583089ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 2.190605ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:05:19Z"
    - latency: 2.588678ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:04:19Z"
    - latency: 2.630549ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:03:19Z"
    - latency: 2.202012ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:02:19Z"
    - latency: 2.355612ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:01:19Z"
    - latency: 2.251621ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: 04b9e03e-ed72-4d67-8f32-af69f7db7946
    resourceVersion: "69576"
    uid: c566474a-52e0-4f53-a419-02ed4d3dcc18
  spec:
    sourcePod: network-check-source-6f8b768455-pf6th
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:40:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.014µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:10:19Z"
    - latency: 1.738852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:10:19Z"
    - latency: 851.487µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 1.834335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:09:19Z"
    - latency: 1.041205ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 1.809735ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:08:19Z"
    - latency: 1.163013ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 1.889144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:07:19Z"
    - latency: 1.023239ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:06:19Z"
    - latency: 1.883876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:06:19Z"
kind: List
metadata:
  resourceVersion: ""