apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "70316"
    uid: cdb037f3-b805-4610-b4e9-9097e148b280
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:56:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.167085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:38:06Z"
    - latency: 909.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 983.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 1.041619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 1.113683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 1.259642ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 1.003672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:32:06Z"
    - latency: 1.408298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:31:06Z"
    - latency: 1.001316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:30:06Z"
    - latency: 1.001579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:29:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "69692"
    uid: 3d80219b-c353-4475-a2ca-a6c5fa290cf5
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:55:06Z"
      message: 'load-balancer-api-external: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.157061ms
      message: 'load-balancer-api-external: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 6.757204ms
      message: 'load-balancer-api-external: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 2.819758ms
      message: 'load-balancer-api-external: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 7.603757ms
      message: 'load-balancer-api-external: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 4.041829ms
      message: 'load-balancer-api-external: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 6.708046ms
      message: 'load-balancer-api-external: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 3.262917ms
      message: 'load-balancer-api-external: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 7.218696ms
      message: 'load-balancer-api-external: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 4.219262ms
      message: 'load-balancer-api-external: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 7.297629ms
      message: 'load-balancer-api-external: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:33:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "69693"
    uid: 37dcb1ab-a89f-47a5-95f6-8c7324dadaa4
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:55:06Z"
      message: 'load-balancer-api-internal: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.17073ms
      message: 'load-balancer-api-internal: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 6.672711ms
      message: 'load-balancer-api-internal: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 2.828959ms
      message: 'load-balancer-api-internal: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 7.661091ms
      message: 'load-balancer-api-internal: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 4.045628ms
      message: 'load-balancer-api-internal: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 6.762524ms
      message: 'load-balancer-api-internal: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 3.179535ms
      message: 'load-balancer-api-internal: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 7.307151ms
      message: 'load-balancer-api-internal: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 4.795359ms
      message: 'load-balancer-api-internal: tcp connection to a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 7.271517ms
      message: 'load-balancer-api-internal: resolved host name a251e5d98d7d0432abdaadd4cfea3dd3-4540f5564f8fe7dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:33:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-network-check-target-ip-10-0-129-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "70314"
    uid: f2c5ca65-c428-4dc6-bcdf-e952e01580b7
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:56:06Z"
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289406ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:38:06Z"
    - latency: 2.326908ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 2.458554ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 2.422516ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 2.497086ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 2.397964ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 1.943322ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:32:06Z"
    - latency: 2.243034ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:31:06Z"
    - latency: 2.591019ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:30:06Z"
    - latency: 2.004926ms
      message: 'network-check-target-ip-10-0-129-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:29:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-network-check-target-ip-10-0-132-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "70313"
    uid: f863776c-a3f0-460f-ab12-d855972484aa
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:56:06Z"
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.969µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:38:06Z"
    - latency: 915µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 897.35µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 1.447098ms
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 1.49317ms
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 947.155µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 780.975µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:32:06Z"
    - latency: 1.273387ms
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:31:06Z"
    - latency: 910.322µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:30:06Z"
    - latency: 945.636µs
      message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:29:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-network-check-target-ip-10-0-143-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "70315"
    uid: 4c9402fb-892f-405b-9cfb-066e5755d711
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:56:06Z"
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.421208ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:38:06Z"
    - latency: 2.352901ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 2.566343ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 1.979029ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 2.979233ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 2.538313ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 2.579078ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:32:06Z"
    - latency: 2.361479ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:31:06Z"
    - latency: 2.712412ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:30:06Z"
    - latency: 2.093933ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:29:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:49:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-169-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-169.ec2.internal
      uid: 358f08ae-e8b4-4e70-8fdc-a146f4346215
    resourceVersion: "69691"
    uid: 1848bd90-22dc-47b2-adb5-d2c68d57eac6
  spec:
    sourcePod: network-check-source-6f8b768455-t6nwd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:55:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.325µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 1.85851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:37:06Z"
    - latency: 934.111µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 1.956827ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:36:06Z"
    - latency: 847.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 1.975564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:35:06Z"
    - latency: 968.71µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 1.887402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:34:06Z"
    - latency: 910.511µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:33:06Z"
    - latency: 2.365808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:33:06Z"
kind: List
metadata:
  resourceVersion: ""