apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "43964"
    uid: 5d83951d-4267-42d7-9587-440da3782619
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:57:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.135052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 1.036477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 1.059483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 1.004358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:15:59Z"
    - latency: 926.166µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:14:59Z"
    - latency: 1.014885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:13:59Z"
    - latency: 1.328303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:12:59Z"
    - latency: 1.171269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:11:59Z"
    - latency: 1.093101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:10:59Z"
    - latency: 897.782µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "46275"
    uid: 12b71f26-159f-4bab-9564-e3414a2c61bf
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:56:59Z"
      message: 'load-balancer-api-external: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.305816ms
      message: 'load-balancer-api-external: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:20:59Z"
    - latency: 16.711242ms
      message: 'load-balancer-api-external: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:20:59Z"
    - latency: 6.377763ms
      message: 'load-balancer-api-external: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:19:59Z"
    - latency: 10.568826ms
      message: 'load-balancer-api-external: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:19:59Z"
    - latency: 4.733642ms
      message: 'load-balancer-api-external: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 13.406118ms
      message: 'load-balancer-api-external: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 5.052767ms
      message: 'load-balancer-api-external: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 8.859739ms
      message: 'load-balancer-api-external: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 5.103501ms
      message: 'load-balancer-api-external: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 8.012466ms
      message: 'load-balancer-api-external: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:16:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "46276"
    uid: 3dcc271f-044e-4e09-91a2-f6f1cc9cc45c
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:56:59Z"
      message: 'load-balancer-api-internal: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.264549ms
      message: 'load-balancer-api-internal: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:20:59Z"
    - latency: 16.742452ms
      message: 'load-balancer-api-internal: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:20:59Z"
    - latency: 6.424471ms
      message: 'load-balancer-api-internal: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:19:59Z"
    - latency: 10.670027ms
      message: 'load-balancer-api-internal: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:19:59Z"
    - latency: 6.108061ms
      message: 'load-balancer-api-internal: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 13.450327ms
      message: 'load-balancer-api-internal: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 10.612697ms
      message: 'load-balancer-api-internal: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 8.937461ms
      message: 'load-balancer-api-internal: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 5.118199ms
      message: 'load-balancer-api-internal: tcp connection to afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 8.156945ms
      message: 'load-balancer-api-internal: resolved host name afd71dc2a592147afb9227604ca73b78-08e643a1b5f8caf3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:16:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-network-check-target-ip-10-0-130-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "43962"
    uid: 11b235e0-80dc-4679-b595-c9fbba52401a
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:57:59Z"
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.418659ms
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 940.447µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 924.991µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 933.413µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:15:59Z"
    - latency: 1.195177ms
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:14:59Z"
    - latency: 1.494114ms
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:13:59Z"
    - latency: 952.435µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:12:59Z"
    - latency: 869.599µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:11:59Z"
    - latency: 937.363µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:10:59Z"
    - latency: 901.524µs
      message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-network-check-target-ip-10-0-131-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "43963"
    uid: 4bd7a17d-46c9-4c31-84bf-861089e2e644
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:57:59Z"
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459787ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 2.303557ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 2.244713ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 2.555721ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:15:59Z"
    - latency: 2.156064ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:14:59Z"
    - latency: 2.410716ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:13:59Z"
    - latency: 2.448406ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:12:59Z"
    - latency: 2.160766ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:11:59Z"
    - latency: 2.036061ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:10:59Z"
    - latency: 2.072919ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-network-check-target-ip-10-0-135-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "43961"
    uid: 53db3d74-2aaa-40d3-8140-68e49c022ae3
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:57:59Z"
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.313377ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 2.440905ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 2.168259ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 2.243374ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:15:59Z"
    - latency: 2.250455ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:14:59Z"
    - latency: 2.34827ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:13:59Z"
    - latency: 2.507102ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:12:59Z"
    - latency: 2.061904ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:11:59Z"
    - latency: 2.465694ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:10:59Z"
    - latency: 2.474044ms
      message: 'network-check-target-ip-10-0-135-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:09:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-245-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-245.ec2.internal
      uid: 953909e6-51db-4e48-a6a3-a97b3e79bf99
    resourceVersion: "46274"
    uid: 90f107a9-f824-4812-a23d-ed06fafe4ac7
  spec:
    sourcePod: network-check-source-dbd9cf844-lnhkh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:56:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.102µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:20:59Z"
    - latency: 1.810561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:20:59Z"
    - latency: 970.046µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:19:59Z"
    - latency: 1.549911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:19:59Z"
    - latency: 908.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 2.427161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:18:59Z"
    - latency: 891.678µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 1.749616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:17:59Z"
    - latency: 1.040688ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:16:59Z"
    - latency: 1.797644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:16:59Z"
kind: List
metadata:
  resourceVersion: ""