apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "58151"
    uid: 6e728690-8af1-4274-8490-7e2fb2f0ecde
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:38:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.229081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 987.35µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 1.293094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 1.170878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:37Z"
    - latency: 965.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:37Z"
    - latency: 1.465109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:37Z"
    - latency: 1.159613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:53:37Z"
    - latency: 1.199366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:52:37Z"
    - latency: 1.316492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:51:37Z"
    - latency: 984.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:50:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "59711"
    uid: bb480a35-1742-41e2-8e35-974984105ca0
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:37:37Z"
      message: 'load-balancer-api-external: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.466887ms
      message: 'load-balancer-api-external: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:37Z"
    - latency: 8.1051ms
      message: 'load-balancer-api-external: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:37Z"
    - latency: 3.911704ms
      message: 'load-balancer-api-external: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:37Z"
    - latency: 12.46598ms
      message: 'load-balancer-api-external: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:00:37Z"
    - latency: 4.7346ms
      message: 'load-balancer-api-external: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 9.932947ms
      message: 'load-balancer-api-external: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 4.851764ms
      message: 'load-balancer-api-external: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 14.096567ms
      message: 'load-balancer-api-external: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 4.053232ms
      message: 'load-balancer-api-external: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 7.239072ms
      message: 'load-balancer-api-external: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "59710"
    uid: 5ff02c9a-bf2e-4c13-bb38-c9f6278bdd99
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:37:37Z"
      message: 'load-balancer-api-internal: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.9624ms
      message: 'load-balancer-api-internal: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:37Z"
    - latency: 8.197866ms
      message: 'load-balancer-api-internal: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:37Z"
    - latency: 3.720217ms
      message: 'load-balancer-api-internal: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:37Z"
    - latency: 12.486734ms
      message: 'load-balancer-api-internal: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:00:37Z"
    - latency: 4.195539ms
      message: 'load-balancer-api-internal: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 9.973309ms
      message: 'load-balancer-api-internal: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 4.900623ms
      message: 'load-balancer-api-internal: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 14.223364ms
      message: 'load-balancer-api-internal: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 4.051601ms
      message: 'load-balancer-api-internal: tcp connection to a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 7.304356ms
      message: 'load-balancer-api-internal: resolved host name a10cc426ec7064416947f557cadb5a0a-6d93ae7a91c4286e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-128-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "58149"
    uid: af1237c2-abd9-4a80-96fb-7ca9be7f0be0
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:38:37Z"
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.39693ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 2.292297ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 2.547992ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 2.481262ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:37Z"
    - latency: 2.441214ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:37Z"
    - latency: 2.410966ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:37Z"
    - latency: 2.358689ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:53:37Z"
    - latency: 2.444693ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:52:37Z"
    - latency: 2.884009ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:51:37Z"
    - latency: 2.50628ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:50:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-130-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "58148"
    uid: aa3aaa90-ff8b-41d4-aea0-af3ba4328615
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:38:37Z"
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.409µs
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 903.772µs
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 1.502688ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 1.073155ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:37Z"
    - latency: 1.060339ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:37Z"
    - latency: 1.672871ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:37Z"
    - latency: 979.841µs
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:53:37Z"
    - latency: 965.388µs
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:52:37Z"
    - latency: 1.47051ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:51:37Z"
    - latency: 1.008296ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:50:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-141-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "58150"
    uid: 20776034-d3ac-48fe-9f2e-e986b2224abf
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:38:37Z"
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.937433ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 2.483617ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 2.627448ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 2.767987ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:37Z"
    - latency: 2.287074ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:37Z"
    - latency: 2.751153ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:37Z"
    - latency: 2.400951ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:53:37Z"
    - latency: 2.448265ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:52:37Z"
    - latency: 2.781125ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:51:37Z"
    - latency: 2.920208ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:50:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:31:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 4d963f93-77e9-4b74-ab45-294aa7ad796a
    resourceVersion: "59709"
    uid: 3047625c-4261-4165-9f9c-e0fcb918e941
  spec:
    sourcePod: network-check-source-685456655f-98lqw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:37:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.411µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:37Z"
    - latency: 1.883397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:37Z"
    - latency: 971.077µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:37Z"
    - latency: 1.63176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:00:37Z"
    - latency: 855.456µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 2.197567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:59:37Z"
    - latency: 871.838µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 1.790188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:58:37Z"
    - latency: 875.877µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:37Z"
    - latency: 1.814305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:57:37Z"
kind: List
metadata:
  resourceVersion: ""