apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61194"
    uid: 841361bb-16f9-4af5-afb0-2933b550d614
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:32:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.185015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 1.284338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 994.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 1.710344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 1.20113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:56:29Z"
    - latency: 1.357556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:55:29Z"
    - latency: 1.040897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:29Z"
    - latency: 1.335781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:29Z"
    - latency: 1.004227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:29Z"
    - latency: 989.804µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61725"
    uid: 6eb31dc5-a1a0-4a61-b217-e394856c8381
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:29Z"
      message: 'load-balancer-api-external: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.535874ms
      message: 'load-balancer-api-external: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:01:29Z"
    - latency: 8.540894ms
      message: 'load-balancer-api-external: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:01:29Z"
    - latency: 4.956917ms
      message: 'load-balancer-api-external: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 7.858893ms
      message: 'load-balancer-api-external: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 5.791426ms
      message: 'load-balancer-api-external: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 6.797021ms
      message: 'load-balancer-api-external: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 5.49135ms
      message: 'load-balancer-api-external: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 10.925417ms
      message: 'load-balancer-api-external: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 5.646723ms
      message: 'load-balancer-api-external: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 9.506922ms
      message: 'load-balancer-api-external: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61726"
    uid: 331ecf76-1ea6-4bc5-a9f8-d5d1dbc20dd9
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:29Z"
      message: 'load-balancer-api-internal: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.698814ms
      message: 'load-balancer-api-internal: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:01:29Z"
    - latency: 8.574999ms
      message: 'load-balancer-api-internal: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:01:29Z"
    - latency: 5.601033ms
      message: 'load-balancer-api-internal: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 7.906385ms
      message: 'load-balancer-api-internal: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 5.70804ms
      message: 'load-balancer-api-internal: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 6.85317ms
      message: 'load-balancer-api-internal: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 5.480202ms
      message: 'load-balancer-api-internal: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 10.957929ms
      message: 'load-balancer-api-internal: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 5.340513ms
      message: 'load-balancer-api-internal: tcp connection to a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 9.619456ms
      message: 'load-balancer-api-internal: resolved host name a8b4608bcf37d45dcb1fd7045a1820ff-658ef2f9d5cf41a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-131-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61192"
    uid: b6d44e4c-7bbd-4cae-84d7-9cdcdab6a79b
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:32:29Z"
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.257732ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 2.083517ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 2.278285ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 3.173544ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 3.213232ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:56:29Z"
    - latency: 3.122375ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:55:29Z"
    - latency: 2.224742ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:29Z"
    - latency: 2.696456ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:29Z"
    - latency: 2.872895ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:29Z"
    - latency: 2.714723ms
      message: 'network-check-target-ip-10-0-131-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-133-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61193"
    uid: 86ffcc67-bf09-4bb6-b4a3-e78abd1f9307
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:32:29Z"
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.475948ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 2.464591ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 2.308345ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 2.600816ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 2.34696ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:56:29Z"
    - latency: 2.333355ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:55:29Z"
    - latency: 2.308751ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:29Z"
    - latency: 2.296216ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:29Z"
    - latency: 2.744575ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:29Z"
    - latency: 2.198496ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-142-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61191"
    uid: df70ba67-785a-40f5-8072-790461a70487
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:32:29Z"
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023598ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 990.964µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 1.445129ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 1.808047ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 1.756069ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:56:29Z"
    - latency: 923.784µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:55:29Z"
    - latency: 1.045967ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:29Z"
    - latency: 978.153µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:29Z"
    - latency: 1.100025ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:29Z"
    - latency: 1.517051ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:25:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 5252eca7-5834-48ff-973f-c3fe7ff24d3f
    resourceVersion: "61724"
    uid: a305ba00-8620-46e8-9728-0591846d36a6
  spec:
    sourcePod: network-check-source-6f8b768455-mtj8n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.303476ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:01:29Z"
    - latency: 1.93645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:01:29Z"
    - latency: 1.25147ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 2.054889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:00:29Z"
    - latency: 1.076293ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 2.006491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:59:29Z"
    - latency: 1.434011ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 1.723421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:58:29Z"
    - latency: 1.476547ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:57:29Z"
    - latency: 1.863884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:57:29Z"
kind: List
metadata:
  resourceVersion: ""