apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "147239"
    uid: 2d1cd591-9a52-46ce-b7bd-0ba9e23db3c7
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.404081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 1.516537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 1.264134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:08Z"
    - latency: 1.361336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:08Z"
    - latency: 1.059684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:08Z"
    - latency: 1.106895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:08Z"
    - latency: 972.446µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:08Z"
    - latency: 1.011942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:08Z"
    - latency: 1.712642ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:08Z"
    - latency: 1.072756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "149172"
    uid: c70346c6-cc7d-4f52-81ff-0751a5f4e976
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:39:08Z"
      message: 'load-balancer-api-external: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.830312ms
      message: 'load-balancer-api-external: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:39:08Z"
    - latency: 10.164491ms
      message: 'load-balancer-api-external: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:39:08Z"
    - latency: 15.949282ms
      message: 'load-balancer-api-external: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:38:08Z"
    - latency: 7.422368ms
      message: 'load-balancer-api-external: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:38:08Z"
    - latency: 16.540957ms
      message: 'load-balancer-api-external: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:37:08Z"
    - latency: 7.184771ms
      message: 'load-balancer-api-external: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:37:08Z"
    - latency: 13.748431ms
      message: 'load-balancer-api-external: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 7.026354ms
      message: 'load-balancer-api-external: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 17.849921ms
      message: 'load-balancer-api-external: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 8.075823ms
      message: 'load-balancer-api-external: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:35:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "149171"
    uid: 9c18d78d-cb7f-4ef9-aa3c-7d29717f527d
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:39:08Z"
      message: 'load-balancer-api-internal: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.67283ms
      message: 'load-balancer-api-internal: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:39:08Z"
    - latency: 10.230674ms
      message: 'load-balancer-api-internal: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:39:08Z"
    - latency: 15.423675ms
      message: 'load-balancer-api-internal: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:38:08Z"
    - latency: 7.322925ms
      message: 'load-balancer-api-internal: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:38:08Z"
    - latency: 17.948024ms
      message: 'load-balancer-api-internal: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:37:08Z"
    - latency: 7.108113ms
      message: 'load-balancer-api-internal: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:37:08Z"
    - latency: 17.687184ms
      message: 'load-balancer-api-internal: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 6.965399ms
      message: 'load-balancer-api-internal: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 17.854591ms
      message: 'load-balancer-api-internal: tcp connection to aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 8.111764ms
      message: 'load-balancer-api-internal: resolved host name aecd1c3c96de8475f9740aa30c76e91e-62e547c281a6ed6e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:35:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-network-check-target-ip-10-0-129-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "147238"
    uid: f3e761df-65f1-4372-8ab9-a3286d23ca78
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:08Z"
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.018162ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 2.27533ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 3.068579ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:08Z"
    - latency: 2.46202ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:08Z"
    - latency: 2.178245ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:08Z"
    - latency: 2.979228ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:08Z"
    - latency: 2.351412ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:08Z"
    - latency: 2.595066ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:08Z"
    - latency: 2.233337ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:08Z"
    - latency: 3.714141ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-network-check-target-ip-10-0-130-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "147237"
    uid: 21136fbc-9d2a-4d35-9116-3933ed01d8c2
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:08Z"
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.782441ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 2.273984ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 2.370966ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:08Z"
    - latency: 2.154356ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:08Z"
    - latency: 2.192731ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:08Z"
    - latency: 2.549569ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:08Z"
    - latency: 2.236386ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:08Z"
    - latency: 2.368431ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:08Z"
    - latency: 1.990379ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:08Z"
    - latency: 3.805886ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-network-check-target-ip-10-0-138-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "147236"
    uid: 48a7ab64-fd77-4913-9751-11bc43e73886
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:40:08Z"
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.690797ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 1.026901ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 899.619µs
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:34:08Z"
    - latency: 1.035549ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:33:08Z"
    - latency: 928.659µs
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:32:08Z"
    - latency: 1.054631ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:31:08Z"
    - latency: 1.407133ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:30:08Z"
    - latency: 1.393117ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:29:08Z"
    - latency: 1.032148ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:28:08Z"
    - latency: 1.790278ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-200.ec2.internal
      uid: d05563d0-6e0d-409d-8c3a-a6a31ce4ce76
    resourceVersion: "149170"
    uid: 0b2f316c-d0f1-4e74-9a20-952f0b7a14fd
  spec:
    sourcePod: network-check-source-6f78d59f99-846hg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T05:39:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052383ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:39:08Z"
    - latency: 1.822439ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:39:08Z"
    - latency: 984.286µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:38:08Z"
    - latency: 2.082802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:38:08Z"
    - latency: 2.338162ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:37:08Z"
    - latency: 1.970922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:37:08Z"
    - latency: 1.203549ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 2.33678ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:36:08Z"
    - latency: 1.07801ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:35:08Z"
    - latency: 2.011236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:35:08Z"
kind: List
metadata:
  resourceVersion: ""