apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "55481"
    uid: 8b3a448f-b776-475e-af19-9209e079c602
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:02:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.178054ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 960.898µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 931.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 1.134526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:20:07Z"
    - latency: 1.423362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:07Z"
    - latency: 839.676µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:07Z"
    - latency: 4.026677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:07Z"
    - latency: 919.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:07Z"
    - latency: 3.132353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:07Z"
    - latency: 1.874307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "56852"
    uid: 1ad7aae4-c2a7-4670-a9eb-47e68d3e0b01
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:01:07Z"
      message: 'load-balancer-api-external: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.01309ms
      message: 'load-balancer-api-external: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:25:07Z"
    - latency: 8.042813ms
      message: 'load-balancer-api-external: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:25:07Z"
    - latency: 3.64191ms
      message: 'load-balancer-api-external: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:24:07Z"
    - latency: 6.212758ms
      message: 'load-balancer-api-external: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:24:07Z"
    - latency: 5.442035ms
      message: 'load-balancer-api-external: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 6.94752ms
      message: 'load-balancer-api-external: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 5.161635ms
      message: 'load-balancer-api-external: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 7.357803ms
      message: 'load-balancer-api-external: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 4.442664ms
      message: 'load-balancer-api-external: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 6.524784ms
      message: 'load-balancer-api-external: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:21:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "56853"
    uid: 9d6b13bc-bf99-45e3-abcd-0a10a18f9c8a
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:01:07Z"
      message: 'load-balancer-api-internal: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.763587ms
      message: 'load-balancer-api-internal: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:25:07Z"
    - latency: 8.006648ms
      message: 'load-balancer-api-internal: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:25:07Z"
    - latency: 6.103997ms
      message: 'load-balancer-api-internal: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:24:07Z"
    - latency: 6.137078ms
      message: 'load-balancer-api-internal: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:24:07Z"
    - latency: 5.507712ms
      message: 'load-balancer-api-internal: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 6.916156ms
      message: 'load-balancer-api-internal: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 3.990655ms
      message: 'load-balancer-api-internal: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 7.357818ms
      message: 'load-balancer-api-internal: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 3.599917ms
      message: 'load-balancer-api-internal: tcp connection to ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 6.55251ms
      message: 'load-balancer-api-internal: resolved host name ac186cea8255c4c129ee875270ba36e1-3f35011f9110f956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:21:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-network-check-target-ip-10-0-128-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "55479"
    uid: f4fcef08-a39f-4cda-b7eb-a10ce9628354
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:02:07Z"
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275443ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 2.200408ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 2.374005ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 2.486671ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:20:07Z"
    - latency: 2.489438ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:07Z"
    - latency: 2.385ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:07Z"
    - latency: 6.764012ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:07Z"
    - latency: 2.981647ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:07Z"
    - latency: 4.128857ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:07Z"
    - latency: 1.987363ms
      message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-network-check-target-ip-10-0-135-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "55478"
    uid: a4e0b3c0-8b43-4964-a34f-038b86911961
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:02:07Z"
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05893ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 1.468664ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 881.593µs
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 1.349508ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:20:07Z"
    - latency: 986.678µs
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:07Z"
    - latency: 909.509µs
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:07Z"
    - latency: 3.959614ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:07Z"
    - latency: 885.016µs
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:07Z"
    - latency: 1.681695ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:07Z"
    - latency: 1.006034ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-network-check-target-ip-10-0-138-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "55480"
    uid: e16e7e02-b3e0-4cf2-8f1c-540bbdc8ba1b
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:02:07Z"
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.462362ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 2.481881ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 2.478473ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 2.539703ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:20:07Z"
    - latency: 2.329401ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:07Z"
    - latency: 2.40341ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:07Z"
    - latency: 3.339079ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:07Z"
    - latency: 2.358783ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:07Z"
    - latency: 3.751313ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:07Z"
    - latency: 2.448953ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:55:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-173-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-173.ec2.internal
      uid: f4c9210f-97b5-4f83-851e-96c1828ef4d9
    resourceVersion: "56851"
    uid: 5b975e59-3019-4506-8b7d-57c559622ef3
  spec:
    sourcePod: network-check-source-685456655f-48cfz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:01:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.116354ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:25:07Z"
    - latency: 1.950203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:25:07Z"
    - latency: 992.842µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:24:07Z"
    - latency: 1.793232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:24:07Z"
    - latency: 1.156544ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 1.786983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:23:07Z"
    - latency: 1.144069ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 1.563611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:22:07Z"
    - latency: 851.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:21:07Z"
    - latency: 1.727665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:21:07Z"
kind: List
metadata:
  resourceVersion: ""