apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64296"
    uid: 273cb952-2887-4965-8ca4-dfb3e8726211
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 925.264µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 1.156573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 833.989µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 935.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:20Z"
    - latency: 1.021028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:20Z"
    - latency: 1.090893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:20Z"
    - latency: 1.15798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:37:20Z"
    - latency: 1.317075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:36:20Z"
    - latency: 1.291514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64937"
    uid: e30c6174-37c0-49f7-a820-cc8d4e9086e2
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:15:20Z"
      message: 'load-balancer-api-external: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.667633ms
      message: 'load-balancer-api-external: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:20Z"
    - latency: 8.695995ms
      message: 'load-balancer-api-external: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:45:20Z"
    - latency: 6.258587ms
      message: 'load-balancer-api-external: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 8.804164ms
      message: 'load-balancer-api-external: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 4.595305ms
      message: 'load-balancer-api-external: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 7.835513ms
      message: 'load-balancer-api-external: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 4.980162ms
      message: 'load-balancer-api-external: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 10.156258ms
      message: 'load-balancer-api-external: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 7.234842ms
      message: 'load-balancer-api-external: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 8.953825ms
      message: 'load-balancer-api-external: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:41:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64938"
    uid: ca6f62c5-796d-49e9-ba5f-b0b682a117cb
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:15:20Z"
      message: 'load-balancer-api-internal: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.672312ms
      message: 'load-balancer-api-internal: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:20Z"
    - latency: 8.625626ms
      message: 'load-balancer-api-internal: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:45:20Z"
    - latency: 6.544011ms
      message: 'load-balancer-api-internal: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 8.849357ms
      message: 'load-balancer-api-internal: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 4.65528ms
      message: 'load-balancer-api-internal: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 7.820431ms
      message: 'load-balancer-api-internal: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 4.977273ms
      message: 'load-balancer-api-internal: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 10.124507ms
      message: 'load-balancer-api-internal: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 7.272717ms
      message: 'load-balancer-api-internal: tcp connection to a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 8.913059ms
      message: 'load-balancer-api-internal: resolved host name a2b89f3df576c40229a4e99950687ee2-0e02d3b4ed87b95e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:41:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-network-check-target-ip-10-0-131-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64295"
    uid: e71dd8d4-1294-432b-b90d-8c6c968e2c95
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:20Z"
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.328004ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 2.503864ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 2.376426ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 2.59288ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 2.313737ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:20Z"
    - latency: 2.249568ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:20Z"
    - latency: 2.562647ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:20Z"
    - latency: 2.715666ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:37:20Z"
    - latency: 2.584655ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:36:20Z"
    - latency: 2.884559ms
      message: 'network-check-target-ip-10-0-131-146: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-network-check-target-ip-10-0-136-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64294"
    uid: 9900e222-bf8e-4f3b-b640-84169b3aadd8
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:20Z"
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.625604ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 1.827267ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 2.367835ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 2.506259ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 2.532602ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:20Z"
    - latency: 2.290516ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:20Z"
    - latency: 2.685008ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:20Z"
    - latency: 2.486687ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:37:20Z"
    - latency: 2.371593ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:36:20Z"
    - latency: 2.584962ms
      message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-network-check-target-ip-10-0-137-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64293"
    uid: dd37d4bf-d12e-47c2-b203-8882c5053b2b
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:16:20Z"
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032979ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 939.573µs
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 975.75µs
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 936.633µs
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 1.006211ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:20Z"
    - latency: 952.731µs
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:20Z"
    - latency: 1.066404ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:20Z"
    - latency: 1.061112ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:37:20Z"
    - latency: 1.231238ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:36:20Z"
    - latency: 979.523µs
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:09:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-53-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-53.ec2.internal
      uid: 4fdaf594-b849-4ac7-b4bf-182419da112d
    resourceVersion: "64936"
    uid: 20de8a53-0a1e-4a40-80c5-fd11812c7018
  spec:
    sourcePod: network-check-source-6f8b768455-94gvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:15:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:20Z"
    - latency: 1.782331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:45:20Z"
    - latency: 821.741µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 1.651347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:44:20Z"
    - latency: 854.142µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 1.765864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:43:20Z"
    - latency: 950.677µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 2.344059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:42:20Z"
    - latency: 1.052689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:20Z"
    - latency: 2.22536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:41:20Z"
kind: List
metadata:
  resourceVersion: ""