apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "93525"
    uid: 45204d74-4200-4844-86cf-f2c324cb70ea
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 1.057085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 984.064µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 1.562149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 1.010949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:19Z"
    - latency: 1.168589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:19Z"
    - latency: 1.005062ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:19Z"
    - latency: 1.135206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:19Z"
    - latency: 1.826778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:19Z"
    - latency: 1.000645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "94280"
    uid: 69639d01-54cf-4873-bb19-fea5feabd197
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:52:19Z"
      message: 'load-balancer-api-external: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.808846ms
      message: 'load-balancer-api-external: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:04:19Z"
    - latency: 7.341639ms
      message: 'load-balancer-api-external: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:04:19Z"
    - latency: 6.25335ms
      message: 'load-balancer-api-external: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 7.639916ms
      message: 'load-balancer-api-external: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 5.267719ms
      message: 'load-balancer-api-external: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 7.685044ms
      message: 'load-balancer-api-external: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 5.023628ms
      message: 'load-balancer-api-external: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 7.684121ms
      message: 'load-balancer-api-external: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 5.201227ms
      message: 'load-balancer-api-external: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 6.310941ms
      message: 'load-balancer-api-external: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "94279"
    uid: c58dabb5-276a-4a74-b9f3-3a951ee29a78
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:52:19Z"
      message: 'load-balancer-api-internal: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.712778ms
      message: 'load-balancer-api-internal: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:04:19Z"
    - latency: 7.451545ms
      message: 'load-balancer-api-internal: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:04:19Z"
    - latency: 5.36879ms
      message: 'load-balancer-api-internal: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 7.58626ms
      message: 'load-balancer-api-internal: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 4.413924ms
      message: 'load-balancer-api-internal: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 7.655545ms
      message: 'load-balancer-api-internal: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 5.039687ms
      message: 'load-balancer-api-internal: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 7.759188ms
      message: 'load-balancer-api-internal: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 5.791578ms
      message: 'load-balancer-api-internal: tcp connection to a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 6.362712ms
      message: 'load-balancer-api-internal: resolved host name a66ba347e23af42c2955a32327bb586f-44f6b5aadc1a34e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-network-check-target-ip-10-0-129-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "93522"
    uid: b249cd05-839f-4629-92d8-c939a94e46e4
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:19Z"
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28613ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 920.956µs
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 1.163548ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 947.247µs
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 1.063617ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:19Z"
    - latency: 1.35964ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:19Z"
    - latency: 1.01385ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:19Z"
    - latency: 993.666µs
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:19Z"
    - latency: 1.129218ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:19Z"
    - latency: 1.077141ms
      message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-network-check-target-ip-10-0-139-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "93523"
    uid: 5222ff13-c131-44d1-968a-2b37b429a85a
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:19Z"
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.103761ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 2.58963ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 2.350205ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 2.21037ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 2.312339ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:19Z"
    - latency: 2.40496ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:19Z"
    - latency: 2.58605ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:19Z"
    - latency: 2.85744ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:19Z"
    - latency: 2.698783ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:19Z"
    - latency: 2.552528ms
      message: 'network-check-target-ip-10-0-139-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-network-check-target-ip-10-0-143-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "93524"
    uid: 562b7080-8a95-4100-8ef4-0242e2b5aad0
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:19Z"
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.550761ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 2.564319ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 2.609678ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 2.168072ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 2.438943ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:59:19Z"
    - latency: 2.444054ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:58:19Z"
    - latency: 2.638029ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:57:19Z"
    - latency: 2.70203ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:56:19Z"
    - latency: 2.820225ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:55:19Z"
    - latency: 2.621853ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:54:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:46:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-194-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-194.ec2.internal
      uid: bd888930-f193-48f3-bdcd-2657c48b20de
    resourceVersion: "94277"
    uid: 65339761-8435-4693-bccf-12794bd12d9c
  spec:
    sourcePod: network-check-source-6f8b768455-czbqf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:52:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091481ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:04:19Z"
    - latency: 2.402546ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:04:19Z"
    - latency: 1.428986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 1.934349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:03:19Z"
    - latency: 1.102897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 1.600961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:02:19Z"
    - latency: 1.10609ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 2.485371ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:01:19Z"
    - latency: 1.254078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:00:19Z"
    - latency: 1.796981ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:00:19Z"
kind: List
metadata:
  resourceVersion: ""