apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "47791"
    uid: 6e361d28-2548-45dd-940c-f067d9bf5516
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:09:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 1.469275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 1.243536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 1.156109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:27:25Z"
    - latency: 848.209µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:26:25Z"
    - latency: 1.107976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:25:25Z"
    - latency: 933.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:24:25Z"
    - latency: 1.231534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:23:25Z"
    - latency: 881.981µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:22:25Z"
    - latency: 1.127126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "50123"
    uid: 3a0b958b-4f90-48fb-bab2-9d9f0e4fbb48
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:08:25Z"
      message: 'load-balancer-api-external: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.364689ms
      message: 'load-balancer-api-external: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:32:25Z"
    - latency: 9.133807ms
      message: 'load-balancer-api-external: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:32:25Z"
    - latency: 5.457977ms
      message: 'load-balancer-api-external: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:31:25Z"
    - latency: 11.673676ms
      message: 'load-balancer-api-external: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:31:25Z"
    - latency: 4.85701ms
      message: 'load-balancer-api-external: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 6.611845ms
      message: 'load-balancer-api-external: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 8.869081ms
      message: 'load-balancer-api-external: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 6.440121ms
      message: 'load-balancer-api-external: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 7.136763ms
      message: 'load-balancer-api-external: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 5.975753ms
      message: 'load-balancer-api-external: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:28:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "50122"
    uid: fc406f59-f909-4ce7-be36-dfa613948005
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:08:25Z"
      message: 'load-balancer-api-internal: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.424453ms
      message: 'load-balancer-api-internal: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:32:25Z"
    - latency: 9.124792ms
      message: 'load-balancer-api-internal: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:32:25Z"
    - latency: 5.485043ms
      message: 'load-balancer-api-internal: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:31:25Z"
    - latency: 11.637505ms
      message: 'load-balancer-api-internal: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:31:25Z"
    - latency: 4.879942ms
      message: 'load-balancer-api-internal: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 6.55191ms
      message: 'load-balancer-api-internal: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 8.962167ms
      message: 'load-balancer-api-internal: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 6.471015ms
      message: 'load-balancer-api-internal: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 6.627755ms
      message: 'load-balancer-api-internal: tcp connection to a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 5.837778ms
      message: 'load-balancer-api-internal: resolved host name a374646986cc2440e8ac7c51adfc844d-ee143e9dc9b93126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:28:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-network-check-target-ip-10-0-128-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "47788"
    uid: ab30a2fc-d05f-4a3c-9504-c5cd955b0a41
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:09:25Z"
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.899571ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 2.00752ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 1.937043ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 1.918471ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:27:25Z"
    - latency: 2.009645ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:26:25Z"
    - latency: 2.084267ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:25:25Z"
    - latency: 1.801587ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:24:25Z"
    - latency: 1.92791ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:23:25Z"
    - latency: 1.981935ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:22:25Z"
    - latency: 2.335259ms
      message: 'network-check-target-ip-10-0-128-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-network-check-target-ip-10-0-128-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "47790"
    uid: 3e1aa3a0-aa51-44c8-a03d-77538e2c8450
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:09:25Z"
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.285366ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 2.175843ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 2.357345ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 2.272835ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:27:25Z"
    - latency: 2.401368ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:26:25Z"
    - latency: 2.294629ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:25:25Z"
    - latency: 1.819528ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:24:25Z"
    - latency: 2.334904ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:23:25Z"
    - latency: 2.297578ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:22:25Z"
    - latency: 2.339278ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-network-check-target-ip-10-0-136-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "47789"
    uid: 96d0f495-b2eb-4f76-bf56-ddf48067abad
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:09:25Z"
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.511µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 860.166µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 891.789µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 907.465µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:27:25Z"
    - latency: 970.044µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:26:25Z"
    - latency: 867.987µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:25:25Z"
    - latency: 876.478µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:24:25Z"
    - latency: 862.802µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:23:25Z"
    - latency: 916.647µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:22:25Z"
    - latency: 996.918µs
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-155.ec2.internal
      uid: 9ef37a2a-cf40-46d1-bf57-2e36f479afef
    resourceVersion: "50121"
    uid: 7d363677-eedf-4071-82b6-29647170eacc
  spec:
    sourcePod: network-check-source-989f8b8dc-9rgzs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:08:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 786.749µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:32:25Z"
    - latency: 1.752985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:32:25Z"
    - latency: 1.193233ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:31:25Z"
    - latency: 1.821136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:31:25Z"
    - latency: 919.724µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 1.870592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:30:25Z"
    - latency: 837.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 1.726856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:29:25Z"
    - latency: 890.69µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:28:25Z"
    - latency: 1.789354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:28:25Z"
kind: List
metadata:
  resourceVersion: ""