apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60287"
    uid: 43d9e3b5-d0a1-4e23-99ba-be40aaff22c0
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:20:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.731µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 914.511µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 855.783µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 1.14838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 1.305093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 895.79µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:50:51Z"
    - latency: 1.368192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:49:51Z"
    - latency: 1.062192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:48:51Z"
    - latency: 1.136553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:47:51Z"
    - latency: 786.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:46:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60289"
    uid: 3f73891c-fca4-4a81-be95-1533aabccbbf
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:19:51Z"
      message: 'load-balancer-api-external: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.416928ms
      message: 'load-balancer-api-external: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 6.752278ms
      message: 'load-balancer-api-external: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 5.57591ms
      message: 'load-balancer-api-external: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 8.499219ms
      message: 'load-balancer-api-external: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 5.058749ms
      message: 'load-balancer-api-external: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 8.191909ms
      message: 'load-balancer-api-external: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 5.836183ms
      message: 'load-balancer-api-external: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 6.251376ms
      message: 'load-balancer-api-external: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 3.445933ms
      message: 'load-balancer-api-external: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 6.919737ms
      message: 'load-balancer-api-external: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:51:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60288"
    uid: de2fc0ec-a135-45ed-8e10-368fe45ee09d
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:19:51Z"
      message: 'load-balancer-api-internal: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.361907ms
      message: 'load-balancer-api-internal: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 6.80663ms
      message: 'load-balancer-api-internal: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 5.581649ms
      message: 'load-balancer-api-internal: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 8.411843ms
      message: 'load-balancer-api-internal: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 5.077955ms
      message: 'load-balancer-api-internal: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 8.249563ms
      message: 'load-balancer-api-internal: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 5.884886ms
      message: 'load-balancer-api-internal: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 6.281323ms
      message: 'load-balancer-api-internal: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 3.432937ms
      message: 'load-balancer-api-internal: tcp connection to ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 7.061296ms
      message: 'load-balancer-api-internal: resolved host name ad12911c64d1f403197a4773e3616a9c-c159f5b5625fbdbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:51:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-network-check-target-ip-10-0-134-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60285"
    uid: c587431c-df45-4a61-bf6d-5bc10458cefd
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:20:51Z"
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.490948ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 2.312182ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 2.504803ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 2.299102ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 2.013186ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 2.343419ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:50:51Z"
    - latency: 2.698901ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:49:51Z"
    - latency: 2.126913ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:48:51Z"
    - latency: 2.375583ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:47:51Z"
    - latency: 1.830504ms
      message: 'network-check-target-ip-10-0-134-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:46:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-network-check-target-ip-10-0-135-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60283"
    uid: e240fb53-b871-420b-b951-4c36159bc20a
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:20:51Z"
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.12902ms
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 866.327µs
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 850.481µs
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 814.606µs
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 1.245239ms
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 1.132868ms
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:50:51Z"
    - latency: 1.059381ms
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:49:51Z"
    - latency: 858.098µs
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:48:51Z"
    - latency: 1.214333ms
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:47:51Z"
    - latency: 917.34µs
      message: 'network-check-target-ip-10-0-135-47: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:46:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-network-check-target-ip-10-0-141-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60284"
    uid: 15e324ce-a920-4263-bae0-ea09f11e9766
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:20:51Z"
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990907ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 1.934998ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 2.181194ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 2.013563ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 1.988986ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 2.057547ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:50:51Z"
    - latency: 2.10591ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:49:51Z"
    - latency: 2.175401ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:48:51Z"
    - latency: 2.115449ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:47:51Z"
    - latency: 1.742323ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:46:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T22:13:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-47-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-47.ec2.internal
      uid: 37197574-c4a6-4b4e-bd9e-f1a67d6c5b02
    resourceVersion: "60286"
    uid: bac504f3-891b-4bac-bcda-98d993588530
  spec:
    sourcePod: network-check-source-869dcfcdcd-c9nrk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:19:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 1.885858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:55:51Z"
    - latency: 1.084207ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 2.764546ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:54:51Z"
    - latency: 1.228035ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 1.874797ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:53:51Z"
    - latency: 877.459µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 1.608664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:52:51Z"
    - latency: 789.442µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:51:51Z"
    - latency: 2.026858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:51:51Z"
kind: List
metadata:
  resourceVersion: ""