apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "60414"
    uid: 0e194b66-f38a-443f-afd4-1431509f88a5
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08: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.03989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 1.260297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 1.026101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 984.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 829.661µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:08Z"
    - latency: 985.3µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:08Z"
    - latency: 1.151567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:08Z"
    - latency: 994.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:08Z"
    - latency: 995.239µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:08Z"
    - latency: 980.959µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "61493"
    uid: 79b1567f-1cd8-4eba-a2e3-6985e6d8df17
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:07:08Z"
      message: 'load-balancer-api-external: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.096592ms
      message: 'load-balancer-api-external: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:08Z"
    - latency: 7.241875ms
      message: 'load-balancer-api-external: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:37:08Z"
    - latency: 5.178283ms
      message: 'load-balancer-api-external: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 7.804502ms
      message: 'load-balancer-api-external: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 4.863107ms
      message: 'load-balancer-api-external: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 7.483948ms
      message: 'load-balancer-api-external: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 3.204131ms
      message: 'load-balancer-api-external: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 7.881702ms
      message: 'load-balancer-api-external: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 3.878427ms
      message: 'load-balancer-api-external: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 9.355905ms
      message: 'load-balancer-api-external: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:33:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "61494"
    uid: bf72824c-eb11-40b9-b925-cee8cea37db0
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:07:08Z"
      message: 'load-balancer-api-internal: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.980393ms
      message: 'load-balancer-api-internal: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:08Z"
    - latency: 7.344031ms
      message: 'load-balancer-api-internal: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:37:08Z"
    - latency: 4.245268ms
      message: 'load-balancer-api-internal: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 7.741956ms
      message: 'load-balancer-api-internal: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 4.896772ms
      message: 'load-balancer-api-internal: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 7.554344ms
      message: 'load-balancer-api-internal: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 3.737889ms
      message: 'load-balancer-api-internal: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 7.958942ms
      message: 'load-balancer-api-internal: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 3.865293ms
      message: 'load-balancer-api-internal: tcp connection to a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 9.550303ms
      message: 'load-balancer-api-internal: resolved host name a661c9bd9cf4d4bca8f088fb6c511632-311fd9d7f176793b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:33:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-129-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "60411"
    uid: 62b85197-08f6-4d84-8613-7488e8f3afec
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08:08Z"
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055747ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 988.57µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 1.031191ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 821.277µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 1.021938ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:08Z"
    - latency: 931.741µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:08Z"
    - latency: 1.420225ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:08Z"
    - latency: 1.270561ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:08Z"
    - latency: 950.35µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:08Z"
    - latency: 1.103397ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-133-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "60413"
    uid: efcffe69-0226-48bb-afcb-b242875be7f1
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08:08Z"
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.484439ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 2.496815ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 2.23791ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 2.61516ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 2.151995ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:08Z"
    - latency: 2.598797ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:08Z"
    - latency: 2.62439ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:08Z"
    - latency: 2.257893ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:08Z"
    - latency: 2.379795ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:08Z"
    - latency: 2.475206ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-135-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "60412"
    uid: 6751b1c7-dc29-4bc0-8c96-6a8032517287
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:08:08Z"
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.326468ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 2.108895ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 2.030859ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 2.323082ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 2.471816ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:32:08Z"
    - latency: 2.478041ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:31:08Z"
    - latency: 2.623756ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:30:08Z"
    - latency: 2.402858ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:29:08Z"
    - latency: 2.22407ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:28:08Z"
    - latency: 2.28578ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T01:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: a349990f-1c9c-4f9f-af05-78661a727d72
    resourceVersion: "61492"
    uid: 2ad24a56-f21f-49df-a874-7c2b9bcfe5fb
  spec:
    sourcePod: network-check-source-6f8b768455-8s6fn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T01:07:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.352µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:37:08Z"
    - latency: 2.004927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:37:08Z"
    - latency: 1.164734ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 1.824323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:36:08Z"
    - latency: 900.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 2.06536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:35:08Z"
    - latency: 1.007279ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 1.700839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:34:08Z"
    - latency: 1.143233ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T01:33:08Z"
    - latency: 1.759409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T01:33:08Z"
kind: List
metadata:
  resourceVersion: ""