apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "147246"
    uid: ff740efc-d5f2-4608-bf20-74eaef77a7e8
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.076186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 990.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 1.763203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:56:33Z"
    - latency: 1.84734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:55:33Z"
    - latency: 12.844834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:54:33Z"
    - latency: 4.787398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:53:33Z"
    - latency: 18.814895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:52:33Z"
    - latency: 1.045355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:51:33Z"
    - latency: 1.349413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:50:33Z"
    - latency: 1.644284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:49:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "154608"
    uid: cb9414b7-2a18-4648-9fec-df1a0a597095
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:01:33Z"
      message: 'load-balancer-api-external: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.130821ms
      message: 'load-balancer-api-external: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T10:01:33Z"
    - latency: 8.403355ms
      message: 'load-balancer-api-external: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T10:01:33Z"
    - latency: 23.361558ms
      message: 'load-balancer-api-external: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T10:00:33Z"
    - latency: 6.870338ms
      message: 'load-balancer-api-external: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T10:00:33Z"
    - latency: 15.609443ms
      message: 'load-balancer-api-external: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:59:33Z"
    - latency: 9.925257ms
      message: 'load-balancer-api-external: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:59:33Z"
    - latency: 18.08317ms
      message: 'load-balancer-api-external: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 7.43223ms
      message: 'load-balancer-api-external: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 14.301854ms
      message: 'load-balancer-api-external: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 7.61267ms
      message: 'load-balancer-api-external: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:57:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "154609"
    uid: 8dfe068b-c895-48b1-849d-73840b311a68
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:01:33Z"
      message: 'load-balancer-api-internal: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.17598ms
      message: 'load-balancer-api-internal: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T10:01:33Z"
    - latency: 8.434998ms
      message: 'load-balancer-api-internal: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T10:01:33Z"
    - latency: 19.429288ms
      message: 'load-balancer-api-internal: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T10:00:33Z"
    - latency: 6.915762ms
      message: 'load-balancer-api-internal: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T10:00:33Z"
    - latency: 15.968305ms
      message: 'load-balancer-api-internal: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:59:33Z"
    - latency: 10.10475ms
      message: 'load-balancer-api-internal: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:59:33Z"
    - latency: 18.043649ms
      message: 'load-balancer-api-internal: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 7.482477ms
      message: 'load-balancer-api-internal: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 17.193018ms
      message: 'load-balancer-api-internal: tcp connection to a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 7.625545ms
      message: 'load-balancer-api-internal: resolved host name a2e3c4f6e4c8f4ff4af42f3163b93747-d8006c47a3524e25.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:57:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-network-check-target-ip-10-0-129-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "147242"
    uid: e6fb7f28-56e3-4f31-becc-9620dbc78d5f
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:33Z"
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108842ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 1.067376ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 2.073052ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:56:33Z"
    - latency: 1.338956ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:55:33Z"
    - latency: 13.622826ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:54:33Z"
    - latency: 5.876135ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:53:33Z"
    - latency: 18.705996ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:52:33Z"
    - latency: 2.397407ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:51:33Z"
    - latency: 4.374559ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:50:33Z"
    - latency: 1.888012ms
      message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:49:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-network-check-target-ip-10-0-135-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "147243"
    uid: 87b6cb1c-8c9c-44f5-bd96-7aa9efe67cb9
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:33Z"
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.522139ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 2.831737ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 2.836126ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:56:33Z"
    - latency: 2.603969ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:55:33Z"
    - latency: 7.848123ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:54:33Z"
    - latency: 4.573351ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:53:33Z"
    - latency: 18.72115ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:52:33Z"
    - latency: 2.820631ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:51:33Z"
    - latency: 7.422044ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:50:33Z"
    - latency: 3.42619ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:49:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-network-check-target-ip-10-0-143-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "147245"
    uid: 87ebaacf-a0bc-4a6e-a2f2-4ef46d6cbedd
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:02:33Z"
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.487768ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 2.6935ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 2.883902ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:56:33Z"
    - latency: 3.216813ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:55:33Z"
    - latency: 9.823497ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:54:33Z"
    - latency: 4.21773ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:53:33Z"
    - latency: 41.781944ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:52:33Z"
    - latency: 2.988785ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:51:33Z"
    - latency: 4.228756ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:50:33Z"
    - latency: 3.967085ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:49:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T08:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-105.ec2.internal
      uid: 777a5baa-a169-4ad9-a018-b26310f7c01e
    resourceVersion: "154607"
    uid: c6750bce-3aac-403f-80f1-d92a722251a4
  spec:
    sourcePod: network-check-source-6f78d59f99-477hl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T09:01:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T10:01:33Z"
    - latency: 1.814663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T10:01:33Z"
    - latency: 1.008021ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T10:00:33Z"
    - latency: 1.988942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T10:00:33Z"
    - latency: 1.041314ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:59:33Z"
    - latency: 3.779565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:59:33Z"
    - latency: 1.121721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 2.145095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:58:33Z"
    - latency: 1.144566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T09:57:33Z"
    - latency: 2.596434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T09:57:33Z"
kind: List
metadata:
  resourceVersion: ""