apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "20265"
    uid: 74436988-4911-4f13-b26f-54baceffbcfa
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:18:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.337948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 831.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 987.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:23Z"
    - latency: 883.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:23Z"
    - latency: 790.793µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:23Z"
    - latency: 1.012914ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:23Z"
    - latency: 978.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:23Z"
    - latency: 1.660803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:23Z"
    - latency: 1.724744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:23Z"
    - latency: 816.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "21912"
    uid: 9178a1e3-6af9-499f-9f73-c0ed3e35cba8
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:17:23Z"
      message: 'load-balancer-api-external: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.140912ms
      message: 'load-balancer-api-external: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:35:23Z"
    - latency: 7.554999ms
      message: 'load-balancer-api-external: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:35:23Z"
    - latency: 5.103403ms
      message: 'load-balancer-api-external: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:23Z"
    - latency: 7.220584ms
      message: 'load-balancer-api-external: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:23Z"
    - latency: 4.114107ms
      message: 'load-balancer-api-external: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:23Z"
    - latency: 7.360496ms
      message: 'load-balancer-api-external: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:23Z"
    - latency: 5.118437ms
      message: 'load-balancer-api-external: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 8.385626ms
      message: 'load-balancer-api-external: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 3.653422ms
      message: 'load-balancer-api-external: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 7.324151ms
      message: 'load-balancer-api-external: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "21913"
    uid: e16fffd0-2c10-49e5-b600-7347db322eda
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:17:23Z"
      message: 'load-balancer-api-internal: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.8554ms
      message: 'load-balancer-api-internal: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:35:23Z"
    - latency: 7.459635ms
      message: 'load-balancer-api-internal: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:35:23Z"
    - latency: 5.130258ms
      message: 'load-balancer-api-internal: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:23Z"
    - latency: 7.177409ms
      message: 'load-balancer-api-internal: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:23Z"
    - latency: 5.784299ms
      message: 'load-balancer-api-internal: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:23Z"
    - latency: 7.27213ms
      message: 'load-balancer-api-internal: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:23Z"
    - latency: 5.088327ms
      message: 'load-balancer-api-internal: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 8.322007ms
      message: 'load-balancer-api-internal: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 3.608435ms
      message: 'load-balancer-api-internal: tcp connection to a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 7.21866ms
      message: 'load-balancer-api-internal: resolved host name a60d776ae1da84129b527978acc8ecb5-797b79c7ac228657.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-network-check-target-ip-10-0-131-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "20264"
    uid: 37248060-c690-41ed-8efe-48a83e9f24f4
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:18:23Z"
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.392354ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 4.077629ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 2.559013ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:23Z"
    - latency: 2.505688ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:23Z"
    - latency: 1.741963ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:23Z"
    - latency: 2.352985ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:23Z"
    - latency: 2.544378ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:23Z"
    - latency: 2.34946ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:23Z"
    - latency: 2.368949ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:23Z"
    - latency: 2.214708ms
      message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-network-check-target-ip-10-0-138-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "20263"
    uid: ec1dd267-634d-44d7-9a65-d89db8a7de02
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:18:23Z"
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422402ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 2.153733ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 2.336896ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:23Z"
    - latency: 2.071649ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:23Z"
    - latency: 2.227378ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:23Z"
    - latency: 2.178587ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:23Z"
    - latency: 2.459365ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:23Z"
    - latency: 3.032643ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:23Z"
    - latency: 2.282602ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:23Z"
    - latency: 2.186937ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-network-check-target-ip-10-0-138-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "20262"
    uid: 3209079c-7974-4962-98fe-838228141f0d
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:18:23Z"
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.597042ms
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 904.327µs
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 838.624µs
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:30:23Z"
    - latency: 912.326µs
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:29:23Z"
    - latency: 1.226982ms
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:28:23Z"
    - latency: 1.119493ms
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:27:23Z"
    - latency: 1.145675ms
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:26:23Z"
    - latency: 890.653µs
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:25:23Z"
    - latency: 950.206µs
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:24:23Z"
    - latency: 870.823µs
      message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:23:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:11:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-206-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-206.ec2.internal
      uid: 69e6a61f-24e5-437d-8153-17d1920e61c8
    resourceVersion: "21911"
    uid: 8bdc634c-0f23-4369-81a2-514089f93e5a
  spec:
    sourcePod: network-check-source-685456655f-pvmpb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T10:17:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.285218ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:35:23Z"
    - latency: 1.541519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:35:23Z"
    - latency: 1.559815ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:34:23Z"
    - latency: 1.985943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:34:23Z"
    - latency: 1.689792ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:33:23Z"
    - latency: 1.802929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:33:23Z"
    - latency: 1.179782ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 1.820826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:32:23Z"
    - latency: 2.204917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T10:31:23Z"
    - latency: 1.776597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T10:31:23Z"
kind: List
metadata:
  resourceVersion: ""