apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "44197"
    uid: b5706b86-9e4b-453a-8621-7d17acf87a89
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:03:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 728.774µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:01Z"
    - latency: 1.021759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:01Z"
    - latency: 878.34µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:01Z"
    - latency: 914.996µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 1.40382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 1.142483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 883.181µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 941.811µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 1.012928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:51:01Z"
    - latency: 889.992µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:50:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "42554"
    uid: 656ec973-bc2d-4e0d-997b-c1c10d416c2d
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:02:01Z"
      message: 'load-balancer-api-external: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.196744ms
      message: 'load-balancer-api-external: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 7.743749ms
      message: 'load-balancer-api-external: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 5.037524ms
      message: 'load-balancer-api-external: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 8.250276ms
      message: 'load-balancer-api-external: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 4.848647ms
      message: 'load-balancer-api-external: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 7.89745ms
      message: 'load-balancer-api-external: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 5.422238ms
      message: 'load-balancer-api-external: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 7.610103ms
      message: 'load-balancer-api-external: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 5.252039ms
      message: 'load-balancer-api-external: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 8.12889ms
      message: 'load-balancer-api-external: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:52:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "42553"
    uid: dfb19047-b0ae-47b0-8975-5c27f678559c
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:02:01Z"
      message: 'load-balancer-api-internal: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.867161ms
      message: 'load-balancer-api-internal: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 7.710986ms
      message: 'load-balancer-api-internal: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 5.026369ms
      message: 'load-balancer-api-internal: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 8.301518ms
      message: 'load-balancer-api-internal: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 4.810464ms
      message: 'load-balancer-api-internal: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 7.811524ms
      message: 'load-balancer-api-internal: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 5.396583ms
      message: 'load-balancer-api-internal: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 7.644489ms
      message: 'load-balancer-api-internal: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 5.599204ms
      message: 'load-balancer-api-internal: tcp connection to ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 8.165063ms
      message: 'load-balancer-api-internal: resolved host name ad1c507b09c584f02b1245cd9e005280-268c10050d6a30fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:52:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-129-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "44195"
    uid: f87f20d2-0cd9-44fc-ba8d-82c28c59d3c7
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:03:01Z"
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.069659ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:01Z"
    - latency: 2.229917ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:01Z"
    - latency: 2.062382ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:01Z"
    - latency: 2.144418ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 2.16729ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 2.366911ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 2.336136ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 2.141934ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 2.015526ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:51:01Z"
    - latency: 2.438123ms
      message: 'network-check-target-ip-10-0-129-156: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:50:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-131-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "44196"
    uid: 0531b908-fda0-43d9-9c84-341252554379
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:03:01Z"
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.421809ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:01Z"
    - latency: 2.267369ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:01Z"
    - latency: 2.090435ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:01Z"
    - latency: 2.163708ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 2.163353ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 2.383345ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 1.964507ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 2.087072ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 1.871946ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:51:01Z"
    - latency: 2.153307ms
      message: 'network-check-target-ip-10-0-131-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:50:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-132-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "44194"
    uid: e4526987-e1d7-4fe8-865f-8ce919343c6c
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:03:01Z"
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 731.701µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:01Z"
    - latency: 834.75µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:01Z"
    - latency: 902.913µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:01Z"
    - latency: 779.366µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 1.438388ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 709.23µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 868.519µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 1.121952ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 886.508µs
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:51:01Z"
    - latency: 1.517126ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:50:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:56:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 19c16894-e970-40bb-b0b4-1c6bdbb71e88
    resourceVersion: "42552"
    uid: a281e97d-771e-4a9c-9479-631b1f274bfd
  spec:
    sourcePod: network-check-source-56d84b9f44-n87gp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:02:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 723.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 1.753465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:56:01Z"
    - latency: 771.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 1.706103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:55:01Z"
    - latency: 763.106µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 2.012239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:54:01Z"
    - latency: 1.026838ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 1.611199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:53:01Z"
    - latency: 1.284987ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:01Z"
    - latency: 1.88334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:52:01Z"
kind: List
metadata:
  resourceVersion: ""