apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "65548"
    uid: b5f33791-a8a1-4480-b9d1-1039a311241a
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:28:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 1.182038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 933.491µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 1.006222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:28:47Z"
    - latency: 834.77µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:27:47Z"
    - latency: 987.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:26:47Z"
    - latency: 898.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:25:47Z"
    - latency: 916.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:24:47Z"
    - latency: 924.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:23:47Z"
    - latency: 1.076269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:22:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "66824"
    uid: 67e92f38-5332-4861-936a-a1c24048966e
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27:47Z"
      message: 'load-balancer-api-external: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.532535ms
      message: 'load-balancer-api-external: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:33:47Z"
    - latency: 8.549246ms
      message: 'load-balancer-api-external: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:33:47Z"
    - latency: 3.757543ms
      message: 'load-balancer-api-external: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:32:47Z"
    - latency: 8.462541ms
      message: 'load-balancer-api-external: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:32:47Z"
    - latency: 4.704893ms
      message: 'load-balancer-api-external: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 9.135513ms
      message: 'load-balancer-api-external: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 5.872731ms
      message: 'load-balancer-api-external: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 7.808663ms
      message: 'load-balancer-api-external: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 5.472015ms
      message: 'load-balancer-api-external: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 8.511833ms
      message: 'load-balancer-api-external: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:29:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "66823"
    uid: c2f12a0c-4bb5-450e-88d6-d635ab5821e4
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27:47Z"
      message: 'load-balancer-api-internal: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.586606ms
      message: 'load-balancer-api-internal: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:33:47Z"
    - latency: 8.49204ms
      message: 'load-balancer-api-internal: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:33:47Z"
    - latency: 3.736299ms
      message: 'load-balancer-api-internal: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:32:47Z"
    - latency: 8.574373ms
      message: 'load-balancer-api-internal: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:32:47Z"
    - latency: 4.746737ms
      message: 'load-balancer-api-internal: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 9.067377ms
      message: 'load-balancer-api-internal: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 5.88166ms
      message: 'load-balancer-api-internal: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 7.890335ms
      message: 'load-balancer-api-internal: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 5.465497ms
      message: 'load-balancer-api-internal: tcp connection to a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 8.458483ms
      message: 'load-balancer-api-internal: resolved host name a9f7cb0a5f08c474795d7ba9bb90abf9-0fcf96bd6b80ba72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:29:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-network-check-target-ip-10-0-131-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "65547"
    uid: c8743001-562d-49de-83cd-2ab8f4409eda
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:28:47Z"
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.942066ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 2.25154ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 2.31943ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 1.997968ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:28:47Z"
    - latency: 2.247392ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:27:47Z"
    - latency: 2.496902ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:26:47Z"
    - latency: 2.325429ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:25:47Z"
    - latency: 2.29701ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:24:47Z"
    - latency: 2.259489ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:23:47Z"
    - latency: 2.238938ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:22:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-network-check-target-ip-10-0-141-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "65545"
    uid: 711175f3-46b9-41f9-8a5b-bf3ce305f07a
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:28:47Z"
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.343571ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 994.858µs
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 895.333µs
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 1.049312ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:28:47Z"
    - latency: 940.481µs
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:27:47Z"
    - latency: 1.082033ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:26:47Z"
    - latency: 1.118965ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:25:47Z"
    - latency: 1.250067ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:24:47Z"
    - latency: 1.111242ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:23:47Z"
    - latency: 923.49µs
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:22:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-network-check-target-ip-10-0-143-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "65546"
    uid: 67d39c89-7bcd-4319-a386-bf528696f428
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:28:47Z"
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264054ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 2.357608ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 2.100946ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 2.031984ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:28:47Z"
    - latency: 2.001187ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:27:47Z"
    - latency: 2.121562ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:26:47Z"
    - latency: 2.373183ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:25:47Z"
    - latency: 2.378456ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:24:47Z"
    - latency: 2.382538ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:23:47Z"
    - latency: 2.415736ms
      message: 'network-check-target-ip-10-0-143-22: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:22:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:21:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-41.ec2.internal
      uid: 77896cea-0310-49b8-8caf-08bedeb15b5e
    resourceVersion: "66822"
    uid: 83b6631c-f171-4a2e-aac4-a77d3a21e3cd
  spec:
    sourcePod: network-check-source-8894fc9bd-vffwj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.083µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:33:47Z"
    - latency: 1.840816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:33:47Z"
    - latency: 989.059µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:32:47Z"
    - latency: 1.652993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:32:47Z"
    - latency: 855.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 1.696741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:31:47Z"
    - latency: 960.524µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 1.784392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:30:47Z"
    - latency: 1.028966ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:29:47Z"
    - latency: 2.077549ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:29:47Z"
kind: List
metadata:
  resourceVersion: ""