apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "53780"
    uid: 4b7d544e-5b6e-485f-ac66-840cf31232d9
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:30:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.227µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 820.762µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 816.011µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 894.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:48:37Z"
    - latency: 917.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:47:37Z"
    - latency: 1.077645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:46:37Z"
    - latency: 1.065917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:37Z"
    - latency: 909.986µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:37Z"
    - latency: 861.734µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:37Z"
    - latency: 781.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "55474"
    uid: 371da390-a284-4350-b259-0806527bfd45
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:29:37Z"
      message: 'load-balancer-api-external: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.383538ms
      message: 'load-balancer-api-external: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:53:37Z"
    - latency: 12.005138ms
      message: 'load-balancer-api-external: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:53:37Z"
    - latency: 4.600202ms
      message: 'load-balancer-api-external: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:52:37Z"
    - latency: 7.242114ms
      message: 'load-balancer-api-external: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:52:37Z"
    - latency: 4.45977ms
      message: 'load-balancer-api-external: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 7.609892ms
      message: 'load-balancer-api-external: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 4.107864ms
      message: 'load-balancer-api-external: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 7.07069ms
      message: 'load-balancer-api-external: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 5.536364ms
      message: 'load-balancer-api-external: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 6.77127ms
      message: 'load-balancer-api-external: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:49:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "55475"
    uid: 3a167fb6-98e3-48cc-8b3a-3a035e730c12
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:29:37Z"
      message: 'load-balancer-api-internal: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.048884ms
      message: 'load-balancer-api-internal: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:53:37Z"
    - latency: 12.039107ms
      message: 'load-balancer-api-internal: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:53:37Z"
    - latency: 4.610178ms
      message: 'load-balancer-api-internal: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:52:37Z"
    - latency: 7.168707ms
      message: 'load-balancer-api-internal: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:52:37Z"
    - latency: 4.361151ms
      message: 'load-balancer-api-internal: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 7.637699ms
      message: 'load-balancer-api-internal: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 6.047854ms
      message: 'load-balancer-api-internal: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 7.050764ms
      message: 'load-balancer-api-internal: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 3.481407ms
      message: 'load-balancer-api-internal: tcp connection to a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 6.819466ms
      message: 'load-balancer-api-internal: resolved host name a4e96a98b99904205bed12483ed36ff8-befebd73a5d740ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:49:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-network-check-target-ip-10-0-128-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "53778"
    uid: f859ecd8-b646-4018-b97e-476df4efb234
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:30:37Z"
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.089206ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 2.12232ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 2.247451ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 2.292008ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:48:37Z"
    - latency: 2.1196ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:47:37Z"
    - latency: 2.629801ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:46:37Z"
    - latency: 2.179116ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:37Z"
    - latency: 2.183445ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:37Z"
    - latency: 2.212665ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:37Z"
    - latency: 2.42922ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-network-check-target-ip-10-0-135-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "53779"
    uid: 61414d00-bcd4-4aba-a716-6aa8961b2e1a
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:30:37Z"
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.160744ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 2.221592ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 2.024428ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 2.235401ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:48:37Z"
    - latency: 2.048624ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:47:37Z"
    - latency: 2.050796ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:46:37Z"
    - latency: 2.141764ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:37Z"
    - latency: 1.837208ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:37Z"
    - latency: 1.889728ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:37Z"
    - latency: 2.076352ms
      message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-network-check-target-ip-10-0-137-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "53777"
    uid: cd5cebb4-3540-460f-959a-54ae2241539c
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:30:37Z"
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.396µs
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 1.273313ms
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 1.492245ms
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 1.025891ms
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:48:37Z"
    - latency: 1.117622ms
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:47:37Z"
    - latency: 909.285µs
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:46:37Z"
    - latency: 1.00214ms
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:37Z"
    - latency: 1.304928ms
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:37Z"
    - latency: 966.961µs
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:37Z"
    - latency: 917.579µs
      message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-146.ec2.internal
      uid: 3a7d40eb-c13a-4ff2-a7c5-d2667b71a313
    resourceVersion: "55472"
    uid: 361ae734-eef3-4b8e-8fc4-fdc729c5e73a
  spec:
    sourcePod: network-check-source-6f8b768455-nqftg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:29:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.267µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:53:37Z"
    - latency: 1.983373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:53:37Z"
    - latency: 918.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:52:37Z"
    - latency: 2.303611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:52:37Z"
    - latency: 1.237771ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 2.020972ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:51:37Z"
    - latency: 1.081526ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 2.338754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:50:37Z"
    - latency: 822.323µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:49:37Z"
    - latency: 2.260711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:49:37Z"
kind: List
metadata:
  resourceVersion: ""