apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "52804"
    uid: 49130ff3-6751-445c-a837-4cbabbbe3c5e
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:06:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.211977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 917.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 1.052103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 992.219µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 1.031496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:30:17Z"
    - latency: 1.040028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:29:17Z"
    - latency: 1.050913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:28:17Z"
    - latency: 1.026287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:27:17Z"
    - latency: 1.027124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:26:17Z"
    - latency: 1.157389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:25:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "53572"
    uid: c1ae2272-b6e0-4d16-b0a8-f0661d5fe248
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:05:17Z"
      message: 'load-balancer-api-external: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.907797ms
      message: 'load-balancer-api-external: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:17Z"
    - latency: 8.265334ms
      message: 'load-balancer-api-external: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:35:17Z"
    - latency: 5.754314ms
      message: 'load-balancer-api-external: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 10.185191ms
      message: 'load-balancer-api-external: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 4.718002ms
      message: 'load-balancer-api-external: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 8.536486ms
      message: 'load-balancer-api-external: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 4.665937ms
      message: 'load-balancer-api-external: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 8.791916ms
      message: 'load-balancer-api-external: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 6.18122ms
      message: 'load-balancer-api-external: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 7.393109ms
      message: 'load-balancer-api-external: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:31:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "53571"
    uid: 6d96187e-e91c-4db5-a7a2-159aa7682275
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:05:17Z"
      message: 'load-balancer-api-internal: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.924093ms
      message: 'load-balancer-api-internal: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:17Z"
    - latency: 8.174531ms
      message: 'load-balancer-api-internal: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:35:17Z"
    - latency: 5.772187ms
      message: 'load-balancer-api-internal: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 10.132902ms
      message: 'load-balancer-api-internal: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 3.642877ms
      message: 'load-balancer-api-internal: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 8.557977ms
      message: 'load-balancer-api-internal: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 4.705436ms
      message: 'load-balancer-api-internal: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 8.724028ms
      message: 'load-balancer-api-internal: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 3.887044ms
      message: 'load-balancer-api-internal: tcp connection to a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 7.362867ms
      message: 'load-balancer-api-internal: resolved host name a2f7cde5fc209454b913bdba735c48f8-90b18b12fa270f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:31:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-ip-10-0-130-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "52803"
    uid: cef41961-ea26-41ca-a3fe-4a92ec748407
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:06:17Z"
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.122684ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 2.006708ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 2.407084ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 1.96944ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 2.513891ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:30:17Z"
    - latency: 2.251444ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:29:17Z"
    - latency: 2.115478ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:28:17Z"
    - latency: 2.041953ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:27:17Z"
    - latency: 1.966119ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:26:17Z"
    - latency: 1.714129ms
      message: 'network-check-target-ip-10-0-130-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:25:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-ip-10-0-138-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "52802"
    uid: 9d68d804-1f68-4b04-992e-3acd64c6766b
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:06:17Z"
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.234086ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 2.612918ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 2.432992ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 2.07406ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 2.312203ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:30:17Z"
    - latency: 2.415013ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:29:17Z"
    - latency: 2.208839ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:28:17Z"
    - latency: 1.939754ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:27:17Z"
    - latency: 2.025977ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:26:17Z"
    - latency: 2.360251ms
      message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:25:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-ip-10-0-139-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "52801"
    uid: 84cd52aa-5efa-4c38-bff3-4963608ac8fa
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:06:17Z"
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.024µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 818.427µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 812.664µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 1.152755ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 963.155µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:30:17Z"
    - latency: 1.331143ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:29:17Z"
    - latency: 1.310459ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:28:17Z"
    - latency: 1.45873ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:27:17Z"
    - latency: 1.464906ms
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:26:17Z"
    - latency: 975.111µs
      message: 'network-check-target-ip-10-0-139-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:25:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-154.ec2.internal
      uid: db995e75-4959-4f58-a7ba-084f34a5b918
    resourceVersion: "53570"
    uid: 26766ac2-bae1-48f6-a42b-8d92be5876d2
  spec:
    sourcePod: network-check-source-989f8b8dc-n4qsl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:05:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.347549ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:17Z"
    - latency: 1.801483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:35:17Z"
    - latency: 975.481µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 2.270337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:34:17Z"
    - latency: 1.052993ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 1.780739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:33:17Z"
    - latency: 915.594µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 1.748299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:32:17Z"
    - latency: 968.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:31:17Z"
    - latency: 1.830329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:31:17Z"
kind: List
metadata:
  resourceVersion: ""