apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61193"
    uid: c02da670-821b-4727-bf54-161e7823f642
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:25:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 987.966µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 948.926µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 1.313537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 1.428859ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 819.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:34Z"
    - latency: 911.785µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:54:34Z"
    - latency: 968.835µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:53:34Z"
    - latency: 832.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:52:34Z"
    - latency: 998.566µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61194"
    uid: 8dad7749-f5c3-4068-a23d-ef5967ab96c0
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:24:34Z"
      message: 'load-balancer-api-external: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.427017ms
      message: 'load-balancer-api-external: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 11.88466ms
      message: 'load-balancer-api-external: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 4.326374ms
      message: 'load-balancer-api-external: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 7.008614ms
      message: 'load-balancer-api-external: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 5.487621ms
      message: 'load-balancer-api-external: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 7.377773ms
      message: 'load-balancer-api-external: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 3.92504ms
      message: 'load-balancer-api-external: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 7.91503ms
      message: 'load-balancer-api-external: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 5.632952ms
      message: 'load-balancer-api-external: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 6.825377ms
      message: 'load-balancer-api-external: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61195"
    uid: 5df6dc13-6a74-4fa7-9be4-9a660d980df2
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:24:34Z"
      message: 'load-balancer-api-internal: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.903369ms
      message: 'load-balancer-api-internal: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 11.828299ms
      message: 'load-balancer-api-internal: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 4.794596ms
      message: 'load-balancer-api-internal: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 6.87003ms
      message: 'load-balancer-api-internal: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 4.076583ms
      message: 'load-balancer-api-internal: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 7.313546ms
      message: 'load-balancer-api-internal: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 3.927182ms
      message: 'load-balancer-api-internal: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 7.834456ms
      message: 'load-balancer-api-internal: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 5.646892ms
      message: 'load-balancer-api-internal: tcp connection to ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 6.77063ms
      message: 'load-balancer-api-internal: resolved host name ac01218ef27e244c18f38803bd56eead-a452abaf3cb1e950.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-128-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61192"
    uid: 3a2f65d5-ee7d-4d81-bfdd-32d6372331bd
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:25:34Z"
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.159304ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 2.076815ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 1.911171ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 2.128086ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 1.926484ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 2.298342ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:34Z"
    - latency: 2.104812ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:54:34Z"
    - latency: 1.903006ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:53:34Z"
    - latency: 1.952223ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:52:34Z"
    - latency: 2.117374ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-135-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61189"
    uid: 56d41899-f6db-47ee-ae3e-0eb315e1d75b
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:25:34Z"
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.876063ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 2.096038ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 1.799675ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 2.026725ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 2.071954ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 2.06639ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:34Z"
    - latency: 1.896947ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:54:34Z"
    - latency: 1.793404ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:53:34Z"
    - latency: 1.701896ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:52:34Z"
    - latency: 2.054395ms
      message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-143-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61190"
    uid: 6f9bdc52-0c8e-41f6-8d8f-e466b830bdb9
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:25:34Z"
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.691856ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 912.881µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 922.998µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 1.639582ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 1.004983ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 1.780724ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:55:34Z"
    - latency: 1.009738ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:54:34Z"
    - latency: 874.443µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:53:34Z"
    - latency: 1.358308ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:52:34Z"
    - latency: 1.619788ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:18:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 63a2b25f-b610-4d90-8986-b8aec00f2eea
    resourceVersion: "61191"
    uid: 72a57056-e5d8-44a7-ba8c-c4cdb25bb7f5
  spec:
    sourcePod: network-check-source-869dcfcdcd-n4c68
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:24:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 2.018263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T21:00:34Z"
    - latency: 978.625µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 1.78783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:59:34Z"
    - latency: 905.562µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 1.68436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:58:34Z"
    - latency: 993.1µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 2.133283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:57:34Z"
    - latency: 1.425217ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:56:34Z"
    - latency: 1.801812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:56:34Z"
kind: List
metadata:
  resourceVersion: ""