apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "123716"
    uid: 6daf670a-ea26-4a94-86ae-0f2612037724
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:43:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:03Z"
    - latency: 1.566544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:03Z"
    - latency: 1.030449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:03Z"
    - latency: 1.341005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:03Z"
    - latency: 1.27538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 1.070705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 920.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 1.183428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 1.168808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 1.745986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "117069"
    uid: d0ac8f00-e791-419b-9387-2c050a642dd9
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:03Z"
      message: 'load-balancer-api-external: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.197006ms
      message: 'load-balancer-api-external: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 7.322049ms
      message: 'load-balancer-api-external: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 55.92816ms
      message: 'load-balancer-api-external: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 7.068413ms
      message: 'load-balancer-api-external: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 57.708126ms
      message: 'load-balancer-api-external: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 6.504637ms
      message: 'load-balancer-api-external: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 53.638559ms
      message: 'load-balancer-api-external: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 7.131747ms
      message: 'load-balancer-api-external: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 57.830368ms
      message: 'load-balancer-api-external: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 7.174843ms
      message: 'load-balancer-api-external: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "117068"
    uid: 37a108dd-6e4f-4678-8e00-810add45a1bc
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:03Z"
      message: 'load-balancer-api-internal: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.188401ms
      message: 'load-balancer-api-internal: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 7.344481ms
      message: 'load-balancer-api-internal: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 55.41969ms
      message: 'load-balancer-api-internal: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 7.108214ms
      message: 'load-balancer-api-internal: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 56.655725ms
      message: 'load-balancer-api-internal: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 6.535915ms
      message: 'load-balancer-api-internal: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 53.681715ms
      message: 'load-balancer-api-internal: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 7.172922ms
      message: 'load-balancer-api-internal: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 57.863386ms
      message: 'load-balancer-api-internal: tcp connection to a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 7.211185ms
      message: 'load-balancer-api-internal: resolved host name a4d303792d30e478da0cee90b09d474b-fa61d523e62daa65.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-ip-10-0-133-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "123714"
    uid: b89d1064-4b1f-4573-b004-253d570df2c0
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:43:03Z"
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.781319ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:03Z"
    - latency: 2.435132ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:03Z"
    - latency: 2.234269ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:03Z"
    - latency: 2.079663ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:03Z"
    - latency: 2.601666ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 2.884142ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 2.668255ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 2.669085ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 2.674289ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 2.623293ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-ip-10-0-133-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "123711"
    uid: 4706f72a-8e96-41c3-a4fb-0b04bbdaca1a
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:43:03Z"
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.942313ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:03Z"
    - latency: 1.884046ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:03Z"
    - latency: 2.287303ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:03Z"
    - latency: 1.851463ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:03Z"
    - latency: 2.515077ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 2.215528ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 2.054555ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 2.255018ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 2.520921ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 2.109728ms
      message: 'network-check-target-ip-10-0-133-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-ip-10-0-134-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "123710"
    uid: 9610c31d-a087-4a14-aa48-64a5f55dc4db
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:43:03Z"
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.264025ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:46:03Z"
    - latency: 1.220005ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:45:03Z"
    - latency: 1.371629ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:44:03Z"
    - latency: 1.471575ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:43:03Z"
    - latency: 1.663137ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 1.290342ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 913.412µs
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 1.032959ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 1.243118ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 1.87071ms
      message: 'network-check-target-ip-10-0-134-46: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:36:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-46-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-46.us-west-1.compute.internal
      uid: 69293c9c-e40d-4497-9363-c7c67bdc1c7c
    resourceVersion: "117065"
    uid: ed7c6134-62c6-40e2-bde0-a96f0be05d49
  spec:
    sourcePod: network-check-source-6f78d59f99-4969l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 2.221871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:42:03Z"
    - latency: 1.663853ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 2.258905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:41:03Z"
    - latency: 1.369186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 1.881592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:40:03Z"
    - latency: 1.668761ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 2.091599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:03Z"
    - latency: 867.164µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:03Z"
    - latency: 2.032556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:03Z"
kind: List
metadata:
  resourceVersion: ""