apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:43:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "190947"
    uid: 52d416e3-9619-47bb-9bf9-07cd580b844e
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:51:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.637089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 4.881491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 1.180121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:00Z"
    - latency: 4.509269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:51:00Z"
    - latency: 1.793339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:50:00Z"
    - latency: 1.375924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:49:00Z"
    - latency: 2.618979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:48:00Z"
    - latency: 1.717778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:00Z"
    - latency: 1.100869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:00Z"
    - latency: 4.796637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:43:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "195603"
    uid: 03b664d0-bda1-4cd1-a537-2913d36ae8a2
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:50:00Z"
      message: 'load-balancer-api-external: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.471661ms
      message: 'load-balancer-api-external: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:56:00Z"
    - latency: 6.907858ms
      message: 'load-balancer-api-external: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:56:00Z"
    - latency: 15.790574ms
      message: 'load-balancer-api-external: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:55:00Z"
    - latency: 6.84267ms
      message: 'load-balancer-api-external: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:55:00Z"
    - latency: 17.560312ms
      message: 'load-balancer-api-external: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 8.246409ms
      message: 'load-balancer-api-external: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 17.292778ms
      message: 'load-balancer-api-external: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 17.109234ms
      message: 'load-balancer-api-external: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 19.384187ms
      message: 'load-balancer-api-external: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:00Z"
    - latency: 6.804967ms
      message: 'load-balancer-api-external: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:43:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "195602"
    uid: 4189c057-376c-4763-ae0a-6b58aaf7f734
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:50:00Z"
      message: 'load-balancer-api-internal: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.534097ms
      message: 'load-balancer-api-internal: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:56:00Z"
    - latency: 6.857963ms
      message: 'load-balancer-api-internal: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:56:00Z"
    - latency: 16.449219ms
      message: 'load-balancer-api-internal: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:55:00Z"
    - latency: 6.87195ms
      message: 'load-balancer-api-internal: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:55:00Z"
    - latency: 15.993441ms
      message: 'load-balancer-api-internal: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 8.202704ms
      message: 'load-balancer-api-internal: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 17.352907ms
      message: 'load-balancer-api-internal: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 14.829335ms
      message: 'load-balancer-api-internal: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 17.638186ms
      message: 'load-balancer-api-internal: tcp connection to a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:00Z"
    - latency: 6.754697ms
      message: 'load-balancer-api-internal: resolved host name a36f601cf99ef4cc8b333ba9fe846065-5099f407105d99e3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:43:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-134-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "190943"
    uid: c1134abc-030f-4a65-8bbb-1fabf075a85f
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:51:00Z"
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.129303ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 5.83508ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 2.646364ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:00Z"
    - latency: 8.256112ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:51:00Z"
    - latency: 2.785997ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:50:00Z"
    - latency: 2.578465ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:49:00Z"
    - latency: 3.186768ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:48:00Z"
    - latency: 2.525509ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:00Z"
    - latency: 2.793377ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:00Z"
    - latency: 17.608155ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:43:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-135-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "190942"
    uid: 5ee60f14-0a0f-4169-86b5-04daae1b9cb8
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:51:00Z"
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.256µs
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 5.574729ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 1.071245ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:00Z"
    - latency: 10.256472ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:51:00Z"
    - latency: 1.508152ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:50:00Z"
    - latency: 1.026456ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:49:00Z"
    - latency: 2.909303ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:48:00Z"
    - latency: 1.633275ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:00Z"
    - latency: 1.074021ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:00Z"
    - latency: 5.564338ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:44:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-ip-10-0-143-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "190985"
    uid: 9355ed4d-39b0-40f0-95df-926121ae5066
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:51:02Z"
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.429625ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:02Z"
    - latency: 2.573484ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:02Z"
    - latency: 2.989654ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:02Z"
    - latency: 10.06447ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:51:02Z"
    - latency: 797.884µs
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:50:02Z"
    - latency: 3.164017ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:49:02Z"
    - latency: 877.881µs
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:48:02Z"
    - latency: 2.484357ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:02Z"
    - latency: 3.21646ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:02Z"
    - latency: 2.77533ms
      message: 'network-check-target-ip-10-0-143-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:43:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-80-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-80.ec2.internal
      uid: 92fa013e-8b17-49f5-91d1-25a68adcaffc
    resourceVersion: "195601"
    uid: 017b0c88-e014-4e72-a4ce-4b202b74f167
  spec:
    sourcePod: network-check-source-6f78d59f99-kw5c9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:50:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.096092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:56:00Z"
    - latency: 1.731125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:56:00Z"
    - latency: 2.269789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:55:00Z"
    - latency: 1.931966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:55:00Z"
    - latency: 1.190525ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 3.064151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:54:00Z"
    - latency: 2.331105ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 5.796812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:53:00Z"
    - latency: 1.170155ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:52:00Z"
    - latency: 2.142407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:52:00Z"
kind: List
metadata:
  resourceVersion: ""