apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "48682"
    uid: be12b9d9-7347-4938-b442-21fb78e75810
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:31:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.209273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 872.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 876.766µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 1.004469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 942.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:55:41Z"
    - latency: 954.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:54:41Z"
    - latency: 1.135996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:53:41Z"
    - latency: 931.055µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:52:41Z"
    - latency: 978.578µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:51:41Z"
    - latency: 1.008375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:50:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "49877"
    uid: 7da7e2be-6874-4449-95c8-233ef6608bca
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:30:41Z"
      message: 'load-balancer-api-external: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.760875ms
      message: 'load-balancer-api-external: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:41Z"
    - latency: 8.097939ms
      message: 'load-balancer-api-external: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:00:41Z"
    - latency: 4.437561ms
      message: 'load-balancer-api-external: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 9.317278ms
      message: 'load-balancer-api-external: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 7.56877ms
      message: 'load-balancer-api-external: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 8.046845ms
      message: 'load-balancer-api-external: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 5.009622ms
      message: 'load-balancer-api-external: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 8.14126ms
      message: 'load-balancer-api-external: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 5.01837ms
      message: 'load-balancer-api-external: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 7.922423ms
      message: 'load-balancer-api-external: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:56:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "49879"
    uid: c0004018-b29d-48dc-8573-25c1bf52a150
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:30:41Z"
      message: 'load-balancer-api-internal: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.749579ms
      message: 'load-balancer-api-internal: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:41Z"
    - latency: 8.153471ms
      message: 'load-balancer-api-internal: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:00:41Z"
    - latency: 4.442176ms
      message: 'load-balancer-api-internal: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 9.262775ms
      message: 'load-balancer-api-internal: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 4.517804ms
      message: 'load-balancer-api-internal: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 8.108314ms
      message: 'load-balancer-api-internal: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 5.006916ms
      message: 'load-balancer-api-internal: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 8.205389ms
      message: 'load-balancer-api-internal: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 3.655671ms
      message: 'load-balancer-api-internal: tcp connection to a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 7.962481ms
      message: 'load-balancer-api-internal: resolved host name a061dfef9dbbe46b8ae70c0bda2ff6ad-d5b1080ff5266035.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:56:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-ip-10-0-131-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "48680"
    uid: f5df6f65-56e9-4c88-96f8-221774df2924
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:31:41Z"
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.030749ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 2.551235ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 2.348802ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 2.264937ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 2.254478ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:55:41Z"
    - latency: 2.403595ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:54:41Z"
    - latency: 2.584854ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:53:41Z"
    - latency: 2.702731ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:52:41Z"
    - latency: 2.423186ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:51:41Z"
    - latency: 2.34489ms
      message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:50:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-ip-10-0-140-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "48681"
    uid: 8528ad41-597e-4433-b50b-afe8766973ce
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:31:41Z"
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.941507ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 2.547507ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 2.154595ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 2.444885ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 2.241922ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:55:41Z"
    - latency: 2.65606ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:54:41Z"
    - latency: 2.662726ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:53:41Z"
    - latency: 2.699302ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:52:41Z"
    - latency: 2.87023ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:51:41Z"
    - latency: 2.163094ms
      message: 'network-check-target-ip-10-0-140-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:50:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-ip-10-0-142-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "48679"
    uid: 716b96ff-2f9c-4ed0-9710-3cbacee54994
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:31:41Z"
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007319ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 1.461264ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 1.307542ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 940.46µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 914.814µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:55:41Z"
    - latency: 959.649µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:54:41Z"
    - latency: 874.894µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:53:41Z"
    - latency: 1.024196ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:52:41Z"
    - latency: 840.963µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:51:41Z"
    - latency: 836.577µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:50:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 9b49e512-0f37-487b-888e-39feab5f6585
    resourceVersion: "49876"
    uid: 389341e2-8b67-436a-a9c1-58768428a698
  spec:
    sourcePod: network-check-source-dbd9cf844-wkhwr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:30:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092594ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:00:41Z"
    - latency: 1.806119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:00:41Z"
    - latency: 979.945µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 2.132546ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:59:41Z"
    - latency: 818.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 1.679458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:58:41Z"
    - latency: 981.443µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 1.575874ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:57:41Z"
    - latency: 847.707µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T16:56:41Z"
    - latency: 1.619343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T16:56:41Z"
kind: List
metadata:
  resourceVersion: ""