apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "44254"
    uid: 8f1b29ee-3523-47b7-b43a-85647314c160
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.386153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 1.051854ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 779.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 882.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:48Z"
    - latency: 1.063689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:48Z"
    - latency: 821.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:48Z"
    - latency: 1.345632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:48Z"
    - latency: 1.197664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:48Z"
    - latency: 1.183751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:48Z"
    - latency: 852.073µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "46348"
    uid: d906b462-4c20-438a-9748-9d50f918a3a4
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:48Z"
      message: 'load-balancer-api-external: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.366859ms
      message: 'load-balancer-api-external: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:17:48Z"
    - latency: 9.041376ms
      message: 'load-balancer-api-external: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:17:48Z"
    - latency: 4.428168ms
      message: 'load-balancer-api-external: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:16:48Z"
    - latency: 9.107788ms
      message: 'load-balancer-api-external: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:16:48Z"
    - latency: 4.511309ms
      message: 'load-balancer-api-external: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 9.115579ms
      message: 'load-balancer-api-external: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 4.747371ms
      message: 'load-balancer-api-external: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 10.250856ms
      message: 'load-balancer-api-external: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 4.477599ms
      message: 'load-balancer-api-external: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 8.411179ms
      message: 'load-balancer-api-external: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:13:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "46349"
    uid: 717f6c05-5cee-4a66-8efc-17b07fa2346d
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:48Z"
      message: 'load-balancer-api-internal: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.391578ms
      message: 'load-balancer-api-internal: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:17:48Z"
    - latency: 9.086275ms
      message: 'load-balancer-api-internal: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:17:48Z"
    - latency: 4.446381ms
      message: 'load-balancer-api-internal: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:16:48Z"
    - latency: 9.183809ms
      message: 'load-balancer-api-internal: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:16:48Z"
    - latency: 5.058513ms
      message: 'load-balancer-api-internal: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 9.07841ms
      message: 'load-balancer-api-internal: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 4.725062ms
      message: 'load-balancer-api-internal: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 10.185974ms
      message: 'load-balancer-api-internal: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 4.461123ms
      message: 'load-balancer-api-internal: tcp connection to a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 8.454805ms
      message: 'load-balancer-api-internal: resolved host name a70908b860c91467db7eab88afd377d4-fd06e2f9d65da9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:13:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-network-check-target-ip-10-0-134-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "44251"
    uid: 3d742e43-b5a3-4829-b45d-ea7c50d23a5f
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:48Z"
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.089666ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 2.371002ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 927.974µs
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 1.423281ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:48Z"
    - latency: 859.938µs
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:48Z"
    - latency: 1.119407ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:48Z"
    - latency: 1.532642ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:48Z"
    - latency: 1.658435ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:48Z"
    - latency: 1.213868ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:48Z"
    - latency: 1.186167ms
      message: 'network-check-target-ip-10-0-134-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-network-check-target-ip-10-0-134-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "44253"
    uid: b0370903-93c3-4983-9d84-0517830dcc45
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:48Z"
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.623016ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 2.2546ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 2.312306ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 2.297663ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:48Z"
    - latency: 2.196191ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:48Z"
    - latency: 2.200341ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:48Z"
    - latency: 2.145608ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:48Z"
    - latency: 1.836458ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:48Z"
    - latency: 2.19515ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:48Z"
    - latency: 2.134554ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-network-check-target-ip-10-0-138-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "44252"
    uid: 820f0994-cb08-42d2-8788-6937b069dea2
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:48Z"
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.311778ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 1.93169ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 1.760094ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 1.81863ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:48Z"
    - latency: 1.671753ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:48Z"
    - latency: 1.649713ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:48Z"
    - latency: 1.73332ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:48Z"
    - latency: 1.846978ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:48Z"
    - latency: 1.655143ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:48Z"
    - latency: 1.566459ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-171.ec2.internal
      uid: e466ee90-8fc5-4f65-8d86-d78973734ae7
    resourceVersion: "46347"
    uid: c2146216-9446-4555-93dd-93925e9bd1ff
  spec:
    sourcePod: network-check-source-dbd9cf844-ztr8q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.836µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:17:48Z"
    - latency: 1.941527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:17:48Z"
    - latency: 932.869µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:16:48Z"
    - latency: 1.79756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:16:48Z"
    - latency: 860.814µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 2.274565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:15:48Z"
    - latency: 872.36µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 2.463622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:14:48Z"
    - latency: 1.221479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:48Z"
    - latency: 1.733617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:13:48Z"
kind: List
metadata:
  resourceVersion: ""