apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "77348"
    uid: c1f85e34-a18d-48b2-b97a-5073e124a68a
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:13:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.206369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 1.237204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:55Z"
    - latency: 1.107271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:55Z"
    - latency: 1.002921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:55Z"
    - latency: 936.926µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:55Z"
    - latency: 1.151594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:55Z"
    - latency: 922.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:55Z"
    - latency: 972.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:55Z"
    - latency: 967.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:55Z"
    - latency: 1.333753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "81173"
    uid: 1457b0f7-79ba-43b4-b84e-be92e558e735
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:12:55Z"
      message: 'load-balancer-api-external: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.200013ms
      message: 'load-balancer-api-external: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:06:55Z"
    - latency: 8.299303ms
      message: 'load-balancer-api-external: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:06:55Z"
    - latency: 3.936674ms
      message: 'load-balancer-api-external: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:05:55Z"
    - latency: 9.451786ms
      message: 'load-balancer-api-external: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:05:55Z"
    - latency: 7.237496ms
      message: 'load-balancer-api-external: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:04:55Z"
    - latency: 7.19054ms
      message: 'load-balancer-api-external: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:04:55Z"
    - latency: 3.496867ms
      message: 'load-balancer-api-external: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:03:55Z"
    - latency: 8.003927ms
      message: 'load-balancer-api-external: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:03:55Z"
    - latency: 3.562822ms
      message: 'load-balancer-api-external: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 6.918039ms
      message: 'load-balancer-api-external: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:02:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "81172"
    uid: 215d6448-d9b8-40b9-a471-f35feedc8689
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:12:55Z"
      message: 'load-balancer-api-internal: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.505531ms
      message: 'load-balancer-api-internal: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:06:55Z"
    - latency: 8.320317ms
      message: 'load-balancer-api-internal: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:06:55Z"
    - latency: 3.844327ms
      message: 'load-balancer-api-internal: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:05:55Z"
    - latency: 9.416777ms
      message: 'load-balancer-api-internal: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:05:55Z"
    - latency: 8.192547ms
      message: 'load-balancer-api-internal: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:04:55Z"
    - latency: 7.235245ms
      message: 'load-balancer-api-internal: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:04:55Z"
    - latency: 3.418285ms
      message: 'load-balancer-api-internal: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:03:55Z"
    - latency: 8.19354ms
      message: 'load-balancer-api-internal: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:03:55Z"
    - latency: 4.474636ms
      message: 'load-balancer-api-internal: tcp connection to a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 6.979081ms
      message: 'load-balancer-api-internal: resolved host name a4c2de0a576904e7a9837acdfc528f1d-b1beddd5a2fe6a90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:02:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-129-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "77345"
    uid: 83688a2a-d32f-4165-977f-18119903843a
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:13:55Z"
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.608448ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 1.350293ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:55Z"
    - latency: 893.196µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:55Z"
    - latency: 962.88µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:55Z"
    - latency: 969.446µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:55Z"
    - latency: 1.016884ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:55Z"
    - latency: 941.876µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:55Z"
    - latency: 983.142µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:55Z"
    - latency: 1.107548ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:55Z"
    - latency: 1.605789ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-130-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "77346"
    uid: fcb2303d-49a9-4da1-b373-8cf8e41dfa85
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:13:55Z"
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.474039ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 2.695509ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:55Z"
    - latency: 2.615366ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:55Z"
    - latency: 6.20058ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:55Z"
    - latency: 2.419183ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:55Z"
    - latency: 2.474303ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:55Z"
    - latency: 2.42191ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:55Z"
    - latency: 2.352661ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:55Z"
    - latency: 2.903725ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:55Z"
    - latency: 2.499109ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-139-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "77347"
    uid: 4b714ef3-8868-4b4d-acbc-921771ab3e33
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:13:55Z"
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.522421ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 2.445756ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:01:55Z"
    - latency: 3.03836ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:00:55Z"
    - latency: 5.930706ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:59:55Z"
    - latency: 2.422731ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:58:55Z"
    - latency: 2.409102ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:57:55Z"
    - latency: 2.398025ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:56:55Z"
    - latency: 2.361504ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:55:55Z"
    - latency: 2.808999ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:54:55Z"
    - latency: 2.242347ms
      message: 'network-check-target-ip-10-0-139-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T04:53:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T04:06:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: d5b828ae-f34b-49f1-bab3-a63663cdc7d4
    resourceVersion: "81171"
    uid: e4b20649-0138-4ec3-b5b6-5c804afad64e
  spec:
    sourcePod: network-check-source-7d88cb55d8-sx7z8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T04:12:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.444419ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:06:55Z"
    - latency: 1.855424ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:06:55Z"
    - latency: 901.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:05:55Z"
    - latency: 2.137657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:05:55Z"
    - latency: 966.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:04:55Z"
    - latency: 1.932401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:04:55Z"
    - latency: 1.099423ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:03:55Z"
    - latency: 1.869796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:03:55Z"
    - latency: 1.04773ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T05:02:55Z"
    - latency: 1.794083ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T05:02:55Z"
kind: List
metadata:
  resourceVersion: ""