apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "29928"
    uid: efdea7b9-32c9-49da-a7a3-1ce8ff72d0ec
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:55:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.164µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:02:00Z"
    - latency: 942.423µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:01:00Z"
    - latency: 1.034907ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 779.529µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 1.124109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 741.174µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 1.010928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 1.091408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:55:00Z"
    - latency: 912.417µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:54:00Z"
    - latency: 929.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "28356"
    uid: c43db74f-6b82-4108-8907-bf69a591e5eb
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:54:00Z"
      message: 'load-balancer-api-external: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.551981ms
      message: 'load-balancer-api-external: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 6.669769ms
      message: 'load-balancer-api-external: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 4.435312ms
      message: 'load-balancer-api-external: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 6.314271ms
      message: 'load-balancer-api-external: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 5.628771ms
      message: 'load-balancer-api-external: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 6.557817ms
      message: 'load-balancer-api-external: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 5.332995ms
      message: 'load-balancer-api-external: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 6.502282ms
      message: 'load-balancer-api-external: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 4.873588ms
      message: 'load-balancer-api-external: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 7.211593ms
      message: 'load-balancer-api-external: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:56:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "28357"
    uid: 613d2389-516b-4665-b9fb-8d59187ceae0
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:54:00Z"
      message: 'load-balancer-api-internal: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.578586ms
      message: 'load-balancer-api-internal: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 6.71017ms
      message: 'load-balancer-api-internal: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 4.449214ms
      message: 'load-balancer-api-internal: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 6.25376ms
      message: 'load-balancer-api-internal: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 5.182036ms
      message: 'load-balancer-api-internal: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 6.518625ms
      message: 'load-balancer-api-internal: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 5.375386ms
      message: 'load-balancer-api-internal: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 6.590084ms
      message: 'load-balancer-api-internal: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 4.825438ms
      message: 'load-balancer-api-internal: tcp connection to a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 7.091679ms
      message: 'load-balancer-api-internal: resolved host name a4406c40ab9df4fde82eb5f08ab8f505-fd45bfaeb364e5b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:56:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-network-check-target-ip-10-0-129-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "29925"
    uid: 1b2b4ab0-8da0-4f11-a9cb-b9837b2113f5
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:55:00Z"
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 712.527µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:02:00Z"
    - latency: 679.475µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:01:00Z"
    - latency: 1.245838ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 789.756µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 789.732µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 795.22µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 1.332603ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 881.534µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:55:00Z"
    - latency: 980.069µs
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:54:00Z"
    - latency: 1.086199ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-network-check-target-ip-10-0-139-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "29927"
    uid: f5343d43-8f69-444f-894a-324482802dde
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:55:00Z"
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.636746ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:02:00Z"
    - latency: 2.064459ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:01:00Z"
    - latency: 2.062269ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 1.574961ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 1.828572ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 1.540955ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 1.978558ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 1.918545ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:55:00Z"
    - latency: 1.878871ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:54:00Z"
    - latency: 1.681132ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-network-check-target-ip-10-0-141-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "29926"
    uid: ccb853b3-72b4-450d-9b65-f12baf7950af
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:55:00Z"
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.784933ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:02:00Z"
    - latency: 2.025807ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:01:00Z"
    - latency: 2.11616ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 2.020613ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 2.064116ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 1.777437ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 2.164112ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 1.907919ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:55:00Z"
    - latency: 1.936344ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:54:00Z"
    - latency: 1.983978ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T13:47:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-53-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-53.ec2.internal
      uid: adaa552b-9981-409a-85e3-9067b688c9d8
    resourceVersion: "28355"
    uid: 7d95ffab-c87e-4dbe-a962-81c742d63be6
  spec:
    sourcePod: network-check-source-7f44b6dd87-hbj7x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T13:54:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 748.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 1.571798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:00:00Z"
    - latency: 799.835µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 1.595167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:59:00Z"
    - latency: 845.949µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 1.604012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:58:00Z"
    - latency: 756.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 2.002011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:57:00Z"
    - latency: 845.223µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T13:56:00Z"
    - latency: 1.987866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T13:56:00Z"
kind: List
metadata:
  resourceVersion: ""