apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33577"
    uid: 1417ba42-a8ec-4463-b0c8-79677d9df72a
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:59:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 1.019404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 1.161163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 1.046714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 853.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 1.352734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:37Z"
    - latency: 1.010023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:37Z"
    - latency: 1.000823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:37Z"
    - latency: 1.080325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:37Z"
    - latency: 1.187444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33579"
    uid: e90f405e-54ce-4118-8099-567b7b4f31a9
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:37Z"
      message: 'load-balancer-api-external: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.605046ms
      message: 'load-balancer-api-external: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 8.781987ms
      message: 'load-balancer-api-external: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 4.651647ms
      message: 'load-balancer-api-external: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 8.347051ms
      message: 'load-balancer-api-external: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 4.757613ms
      message: 'load-balancer-api-external: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 9.508821ms
      message: 'load-balancer-api-external: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 4.975928ms
      message: 'load-balancer-api-external: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 9.634903ms
      message: 'load-balancer-api-external: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 5.10714ms
      message: 'load-balancer-api-external: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 9.895864ms
      message: 'load-balancer-api-external: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33578"
    uid: c59beb9a-76d7-4cd0-8cdd-25aa1b1552ff
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:37Z"
      message: 'load-balancer-api-internal: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.624928ms
      message: 'load-balancer-api-internal: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 8.550603ms
      message: 'load-balancer-api-internal: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 4.631466ms
      message: 'load-balancer-api-internal: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 8.401401ms
      message: 'load-balancer-api-internal: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 5.239328ms
      message: 'load-balancer-api-internal: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 9.411786ms
      message: 'load-balancer-api-internal: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 4.941332ms
      message: 'load-balancer-api-internal: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 9.386864ms
      message: 'load-balancer-api-internal: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 5.117215ms
      message: 'load-balancer-api-internal: tcp connection to a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 9.849154ms
      message: 'load-balancer-api-internal: resolved host name a62a3eee138534bd09131a1941c4ba56-83966b0a033fe34e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-130-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33573"
    uid: caaf1003-8acc-4053-8716-345ce48df44e
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:59:37Z"
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 789.19µs
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 707.03µs
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 881.43µs
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 852.758µs
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 1.278328ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 972.163µs
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:37Z"
    - latency: 1.017772ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:37Z"
    - latency: 905.626µs
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:37Z"
    - latency: 1.495941ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:37Z"
    - latency: 1.079225ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-137-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33574"
    uid: 26ddb5e1-cb1f-4016-ad7b-b3fb046e361b
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:59:37Z"
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938989ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 2.131726ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 2.029246ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 1.62996ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 1.907193ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 1.844772ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:37Z"
    - latency: 1.632598ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:37Z"
    - latency: 1.958298ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:37Z"
    - latency: 1.86549ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:37Z"
    - latency: 1.864068ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-139-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33575"
    uid: 33799720-cccc-4ce4-a22d-d98bc873443f
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:59:37Z"
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.282875ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 2.53306ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 2.374073ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 1.933517ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 2.324056ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 2.382265ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:37Z"
    - latency: 2.259226ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:37Z"
    - latency: 2.410831ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:37Z"
    - latency: 2.362376ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:37Z"
    - latency: 2.385425ms
      message: 'network-check-target-ip-10-0-139-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:52:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-134.ec2.internal
      uid: b7bd632c-2d58-4d7c-bffd-d80780ce0f7e
    resourceVersion: "33576"
    uid: 2d870fcc-e972-4a1b-8180-b63e04d28cec
  spec:
    sourcePod: network-check-source-6f8b768455-422rl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 949.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 1.783619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:37Z"
    - latency: 917.339µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 1.670988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:37Z"
    - latency: 1.072362ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 1.995012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:37Z"
    - latency: 773.551µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 1.789161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:37Z"
    - latency: 821.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:37Z"
    - latency: 1.897079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:37Z"
kind: List
metadata:
  resourceVersion: ""