apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "62443"
    uid: 7e0dd164-079f-4e60-a99b-adf5a30f56a6
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:25:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:46Z"
    - latency: 823.523µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:46Z"
    - latency: 1.099042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:46Z"
    - latency: 881.071µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:46Z"
    - latency: 752.367µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:49:46Z"
    - latency: 1.34423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 1.169059ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 956.108µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 751.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 1.061618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "58125"
    uid: a317e62f-d9af-42fb-bb9c-04ee8df7b710
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:24:46Z"
      message: 'load-balancer-api-external: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.132582ms
      message: 'load-balancer-api-external: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 6.502305ms
      message: 'load-balancer-api-external: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 5.035513ms
      message: 'load-balancer-api-external: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 7.413815ms
      message: 'load-balancer-api-external: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 5.03798ms
      message: 'load-balancer-api-external: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 5.886014ms
      message: 'load-balancer-api-external: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 4.304401ms
      message: 'load-balancer-api-external: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 7.88904ms
      message: 'load-balancer-api-external: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 4.911547ms
      message: 'load-balancer-api-external: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
    - latency: 6.924667ms
      message: 'load-balancer-api-external: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "58126"
    uid: de2ac62a-a74d-47ef-9a8b-433ae5f0ff7a
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:24:46Z"
      message: 'load-balancer-api-internal: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.142673ms
      message: 'load-balancer-api-internal: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 6.465271ms
      message: 'load-balancer-api-internal: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 5.376835ms
      message: 'load-balancer-api-internal: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 7.379666ms
      message: 'load-balancer-api-internal: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 4.996165ms
      message: 'load-balancer-api-internal: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 5.834387ms
      message: 'load-balancer-api-internal: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 5.345147ms
      message: 'load-balancer-api-internal: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 7.870141ms
      message: 'load-balancer-api-internal: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 4.912839ms
      message: 'load-balancer-api-internal: tcp connection to abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
    - latency: 6.900962ms
      message: 'load-balancer-api-internal: resolved host name abcd8353af80841d1a33e51fb8862189-e0e7fe7d835208f3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-ip-10-0-131-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "62442"
    uid: d2fc8576-086a-4600-85e5-e0d9ac5f5272
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:25:46Z"
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.609055ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:46Z"
    - latency: 2.198252ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:46Z"
    - latency: 2.157979ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:46Z"
    - latency: 2.195257ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:46Z"
    - latency: 1.90512ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:49:46Z"
    - latency: 2.158268ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 2.181195ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 1.998543ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 2.368997ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 2.277339ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-ip-10-0-135-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "62444"
    uid: e8fd142b-e363-4302-8f8d-3f7cfb25b98c
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:25:46Z"
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066301ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:46Z"
    - latency: 1.973068ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:46Z"
    - latency: 1.842368ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:46Z"
    - latency: 1.898362ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:46Z"
    - latency: 1.697988ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:49:46Z"
    - latency: 1.833813ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 1.934887ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 1.53121ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 2.067014ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 1.922173ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-ip-10-0-140-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "62441"
    uid: 2c3139bb-d3c6-4395-90b2-438a3d047581
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:25:46Z"
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.297476ms
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:46Z"
    - latency: 1.306972ms
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:46Z"
    - latency: 795.007µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:46Z"
    - latency: 1.047543ms
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:46Z"
    - latency: 797.635µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:49:46Z"
    - latency: 1.00606ms
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 887.135µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 741µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 983.516µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 786.937µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:18:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 1f2d8f8f-6991-4a4b-b81c-83df4d638f28
    resourceVersion: "58124"
    uid: 4eeb60f2-98e2-43d5-92cd-f88445653fab
  spec:
    sourcePod: network-check-source-6f8b768455-nqz29
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:24:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024077ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 1.963001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:48:46Z"
    - latency: 863.994µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 1.660897ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:47:46Z"
    - latency: 1.121684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 1.474179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:46:46Z"
    - latency: 878.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 2.202878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:45:46Z"
    - latency: 796.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:44:46Z"
    - latency: 1.906342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:44:46Z"
kind: List
metadata:
  resourceVersion: ""