apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "65340"
    uid: 8d7f4714-34a1-4552-ae7c-91a59041f016
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:03:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.448197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:45:47Z"
    - latency: 1.036599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 872.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 883.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 811.479µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 966.202µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 960.113µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:39:47Z"
    - latency: 1.044125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:38:47Z"
    - latency: 966.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:37:47Z"
    - latency: 1.243123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:36:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "64354"
    uid: 86fcd391-1645-4bde-ba24-25f4b895c066
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:02:47Z"
      message: 'load-balancer-api-external: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.949967ms
      message: 'load-balancer-api-external: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 9.387678ms
      message: 'load-balancer-api-external: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 4.671545ms
      message: 'load-balancer-api-external: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 8.86284ms
      message: 'load-balancer-api-external: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 5.711598ms
      message: 'load-balancer-api-external: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 9.425835ms
      message: 'load-balancer-api-external: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 3.769705ms
      message: 'load-balancer-api-external: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 9.039649ms
      message: 'load-balancer-api-external: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 3.605272ms
      message: 'load-balancer-api-external: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 8.843002ms
      message: 'load-balancer-api-external: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:40:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "64353"
    uid: cd53d991-2ac6-4577-a93e-b910316fd6b9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:02:47Z"
      message: 'load-balancer-api-internal: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.94426ms
      message: 'load-balancer-api-internal: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 9.411375ms
      message: 'load-balancer-api-internal: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 4.727661ms
      message: 'load-balancer-api-internal: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 8.890127ms
      message: 'load-balancer-api-internal: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 5.693283ms
      message: 'load-balancer-api-internal: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 9.42872ms
      message: 'load-balancer-api-internal: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 4.739346ms
      message: 'load-balancer-api-internal: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 9.106699ms
      message: 'load-balancer-api-internal: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 3.708157ms
      message: 'load-balancer-api-internal: tcp connection to a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 8.906402ms
      message: 'load-balancer-api-internal: resolved host name a26b38c9b2c4040e7aceded6d7559406-7996c9531ec4530b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:40:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-network-check-target-ip-10-0-131-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "65339"
    uid: 658c257c-195f-444d-93fa-b339ea81cd98
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:03:47Z"
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.574268ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:45:47Z"
    - latency: 2.141698ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 2.564698ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 2.356685ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 2.253032ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 2.142138ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 2.171648ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:39:47Z"
    - latency: 2.213119ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:38:47Z"
    - latency: 2.449434ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:37:47Z"
    - latency: 2.266797ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:36:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-network-check-target-ip-10-0-143-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "65337"
    uid: 4d20367a-fb4b-4572-92e1-cf6e35827279
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:03:47Z"
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.688µs
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:45:47Z"
    - latency: 1.19689ms
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 908.028µs
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 942.798µs
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 1.574905ms
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 908.96µs
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 1.051912ms
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:39:47Z"
    - latency: 988.429µs
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:38:47Z"
    - latency: 899.258µs
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:37:47Z"
    - latency: 1.372518ms
      message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:36:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-network-check-target-ip-10-0-143-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "65338"
    uid: b1fef8a5-7e5c-45fc-a294-b0a19ddc8770
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:03:47Z"
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.511786ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:45:47Z"
    - latency: 2.147204ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 2.291914ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 2.525859ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 2.883602ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 2.570383ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 2.284398ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:39:47Z"
    - latency: 2.588427ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:38:47Z"
    - latency: 2.399091ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:37:47Z"
    - latency: 2.577085ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:36:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:56:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-12.ec2.internal
      uid: 8ff76199-976e-4fc9-9b06-576f8f0cfd0c
    resourceVersion: "64352"
    uid: 174b12c2-01ed-496b-87ab-6794c15bb7dc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-46cc2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T11:02:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.062435ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 2.080105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:44:47Z"
    - latency: 929.909µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 1.774962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:43:47Z"
    - latency: 920.459µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 1.62991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:42:47Z"
    - latency: 1.123808ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 2.18887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:41:47Z"
    - latency: 954.575µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T11:40:47Z"
    - latency: 1.68298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T11:40:47Z"
kind: List
metadata:
  resourceVersion: ""