apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "55038"
    uid: 4cef6ee0-403f-478e-814d-c94c254af948
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:09:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.333046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 1.501726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 848.679µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 1.140059ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 1.341273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:44Z"
    - latency: 1.151671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:44Z"
    - latency: 1.223053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:44Z"
    - latency: 1.674464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:44Z"
    - latency: 1.110865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:44Z"
    - latency: 917.273µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "56066"
    uid: a7f83378-9543-41ed-962b-a9d6e73ab5c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:08:44Z"
      message: 'load-balancer-api-external: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.396035ms
      message: 'load-balancer-api-external: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:44Z"
    - latency: 7.139474ms
      message: 'load-balancer-api-external: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:38:44Z"
    - latency: 5.336496ms
      message: 'load-balancer-api-external: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 7.908031ms
      message: 'load-balancer-api-external: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 4.937683ms
      message: 'load-balancer-api-external: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 7.095729ms
      message: 'load-balancer-api-external: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 4.482854ms
      message: 'load-balancer-api-external: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 6.744933ms
      message: 'load-balancer-api-external: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 6.129193ms
      message: 'load-balancer-api-external: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 7.41283ms
      message: 'load-balancer-api-external: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:34:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "56067"
    uid: f0a318f6-b0ed-4e82-99c5-8cae6694f5b2
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:08:44Z"
      message: 'load-balancer-api-internal: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.048167ms
      message: 'load-balancer-api-internal: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:44Z"
    - latency: 7.088881ms
      message: 'load-balancer-api-internal: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:38:44Z"
    - latency: 4.952243ms
      message: 'load-balancer-api-internal: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 7.943712ms
      message: 'load-balancer-api-internal: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 4.464432ms
      message: 'load-balancer-api-internal: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 7.058849ms
      message: 'load-balancer-api-internal: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 5.518262ms
      message: 'load-balancer-api-internal: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 6.662905ms
      message: 'load-balancer-api-internal: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 6.150432ms
      message: 'load-balancer-api-internal: tcp connection to a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 7.361583ms
      message: 'load-balancer-api-internal: resolved host name a26c210fde493491bb1f6c3b2daabcca-1a980e2198533d67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:34:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-ip-10-0-128-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "55035"
    uid: 67c73e19-a553-40fd-a930-5c386ef4c08f
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:09:44Z"
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.010475ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 1.511011ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 903.958µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 1.246937ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 1.128196ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:44Z"
    - latency: 1.087758ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:44Z"
    - latency: 1.461604ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:44Z"
    - latency: 866.845µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:44Z"
    - latency: 970.566µs
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:44Z"
    - latency: 1.102837ms
      message: 'network-check-target-ip-10-0-128-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-ip-10-0-137-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "55036"
    uid: dfc61439-779a-4fcf-b27e-d08f5ce2fe27
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:09:44Z"
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.103218ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 2.120658ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 1.762293ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 2.02249ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 2.029783ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:44Z"
    - latency: 1.89404ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:44Z"
    - latency: 2.448562ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:44Z"
    - latency: 2.729395ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:44Z"
    - latency: 1.890812ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:44Z"
    - latency: 2.211943ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-ip-10-0-140-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "55037"
    uid: 2ea8648c-d2fd-4ca2-a934-b94b05a24934
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:09:44Z"
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.273146ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 2.129807ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 1.807059ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 1.804341ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 2.234038ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:44Z"
    - latency: 1.844243ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:44Z"
    - latency: 2.509571ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:44Z"
    - latency: 2.163101ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:44Z"
    - latency: 2.158431ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:44Z"
    - latency: 2.027722ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:02:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-157-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-157.ec2.internal
      uid: 6fc391ac-2b90-49ed-a86f-5218c8e6ffba
    resourceVersion: "56065"
    uid: c9b55d7f-b684-4bfe-ad40-f6ab66b8363e
  spec:
    sourcePod: network-check-source-869dcfcdcd-rvwcb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:08:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:44Z"
    - latency: 1.749526ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:38:44Z"
    - latency: 1.402489ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 1.777676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:37:44Z"
    - latency: 844.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 1.836896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:36:44Z"
    - latency: 953.956µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 1.745268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:35:44Z"
    - latency: 889.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:44Z"
    - latency: 2.051257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:34:44Z"
kind: List
metadata:
  resourceVersion: ""