apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61153"
    uid: f6a2246c-0281-4ee6-bfbd-2d37fb7389ec
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:24:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 1.415841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 1.206909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 874.964µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 1.617835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 1.219953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:25Z"
    - latency: 1.210401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:25Z"
    - latency: 1.180752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:25Z"
    - latency: 1.13865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:51:25Z"
    - latency: 1.002721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:50:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61154"
    uid: 2b0c8377-007f-4cde-94b8-6f07c1e499cf
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:23:25Z"
      message: 'load-balancer-api-external: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.21221ms
      message: 'load-balancer-api-external: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 7.281095ms
      message: 'load-balancer-api-external: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 3.200402ms
      message: 'load-balancer-api-external: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 7.614652ms
      message: 'load-balancer-api-external: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 5.495548ms
      message: 'load-balancer-api-external: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 7.637113ms
      message: 'load-balancer-api-external: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 7.225636ms
      message: 'load-balancer-api-external: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 10.55125ms
      message: 'load-balancer-api-external: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 9.681197ms
      message: 'load-balancer-api-external: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 7.660433ms
      message: 'load-balancer-api-external: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61155"
    uid: 4b6a665c-8555-42e8-ae49-5d66c2b2de62
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:23:25Z"
      message: 'load-balancer-api-internal: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.343918ms
      message: 'load-balancer-api-internal: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 7.304224ms
      message: 'load-balancer-api-internal: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 3.209757ms
      message: 'load-balancer-api-internal: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 7.583375ms
      message: 'load-balancer-api-internal: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 5.593856ms
      message: 'load-balancer-api-internal: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 7.546869ms
      message: 'load-balancer-api-internal: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 5.277575ms
      message: 'load-balancer-api-internal: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 10.435812ms
      message: 'load-balancer-api-internal: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 4.071068ms
      message: 'load-balancer-api-internal: tcp connection to afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 7.69267ms
      message: 'load-balancer-api-internal: resolved host name afc37b6eb00b64ea58083f4519219d40-c953c2375422f945.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-ip-10-0-132-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61150"
    uid: 044c457d-632a-454a-941a-810ecf5b15eb
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:24:25Z"
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.936012ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 2.549793ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 2.734025ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 1.972972ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 2.212575ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 2.69188ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:25Z"
    - latency: 2.41335ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:25Z"
    - latency: 2.014165ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:25Z"
    - latency: 1.817191ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:51:25Z"
    - latency: 2.325887ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:50:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-ip-10-0-134-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61152"
    uid: 16b8dc8e-1726-425e-a433-eac593827843
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:24:25Z"
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.559672ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 1.962596ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 2.113643ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 1.589234ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 1.928805ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 2.192185ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:25Z"
    - latency: 2.040171ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:25Z"
    - latency: 1.799803ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:25Z"
    - latency: 1.918707ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:51:25Z"
    - latency: 1.849163ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:50:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-ip-10-0-139-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61149"
    uid: 78dadeb9-969d-42b3-b5df-132c68f24e44
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:24:25Z"
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.653µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 884.167µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 1.357474ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 1.128177ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 1.865401ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 1.763471ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:25Z"
    - latency: 915.439µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:25Z"
    - latency: 1.015279ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:25Z"
    - latency: 945.687µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:51:25Z"
    - latency: 897.067µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:50:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 534833ed-7300-428f-9158-e3a99a72e1aa
    resourceVersion: "61151"
    uid: 91eb5491-8884-4f24-aac2-3320c946cf18
  spec:
    sourcePod: network-check-source-869dcfcdcd-r7mnd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:23:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.14563ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 1.976438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:59:25Z"
    - latency: 833.537µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 1.94233ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:58:25Z"
    - latency: 1.201915ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 2.193269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:57:25Z"
    - latency: 769.31µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 2.444708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:56:25Z"
    - latency: 853.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:25Z"
    - latency: 2.134931ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:55:25Z"
kind: List
metadata:
  resourceVersion: ""