apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "18455"
    uid: 2ebb9653-f313-44c9-9e8b-602f06b61cae
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:54:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.296587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 878.551µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:00:27Z"
    - latency: 928.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:59:27Z"
    - latency: 1.37401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:58:27Z"
    - latency: 909.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:27Z"
    - latency: 922.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:27Z"
    - latency: 711.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:27Z"
    - latency: 724.58µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:27Z"
    - latency: 1.248133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:27Z"
    - latency: 1.051654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "20489"
    uid: 17fcace2-9d95-47de-b83b-6c1560db9fe7
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:53:27Z"
      message: 'load-balancer-api-external: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.06143ms
      message: 'load-balancer-api-external: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:05:27Z"
    - latency: 8.024931ms
      message: 'load-balancer-api-external: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:05:27Z"
    - latency: 9.960716ms
      message: 'load-balancer-api-external: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:04:27Z"
    - latency: 9.891498ms
      message: 'load-balancer-api-external: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:04:27Z"
    - latency: 5.236276ms
      message: 'load-balancer-api-external: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:03:27Z"
    - latency: 7.359695ms
      message: 'load-balancer-api-external: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:03:27Z"
    - latency: 4.457192ms
      message: 'load-balancer-api-external: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:02:27Z"
    - latency: 8.048309ms
      message: 'load-balancer-api-external: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:02:27Z"
    - latency: 4.161499ms
      message: 'load-balancer-api-external: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 8.664645ms
      message: 'load-balancer-api-external: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:01:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "20490"
    uid: 4a8c752b-f48e-4e18-bf45-44b9dc6c6188
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:53:27Z"
      message: 'load-balancer-api-internal: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.066731ms
      message: 'load-balancer-api-internal: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:05:27Z"
    - latency: 8.049889ms
      message: 'load-balancer-api-internal: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:05:27Z"
    - latency: 4.790476ms
      message: 'load-balancer-api-internal: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:04:27Z"
    - latency: 9.861888ms
      message: 'load-balancer-api-internal: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:04:27Z"
    - latency: 5.400774ms
      message: 'load-balancer-api-internal: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:03:27Z"
    - latency: 7.307428ms
      message: 'load-balancer-api-internal: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:03:27Z"
    - latency: 4.596664ms
      message: 'load-balancer-api-internal: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:02:27Z"
    - latency: 7.972923ms
      message: 'load-balancer-api-internal: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:02:27Z"
    - latency: 4.166022ms
      message: 'load-balancer-api-internal: tcp connection to a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 8.657664ms
      message: 'load-balancer-api-internal: resolved host name a10bdad72a7954859b76b2d022bd4971-4bd03a1dd583e7a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:01:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-131-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "18453"
    uid: 0fe54448-129b-4ad4-8747-593b6ba9b065
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:54:27Z"
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.463293ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 984.731µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:00:27Z"
    - latency: 717.362µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:59:27Z"
    - latency: 1.00874ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:58:27Z"
    - latency: 813.7µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:27Z"
    - latency: 1.303067ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:27Z"
    - latency: 777.345µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:27Z"
    - latency: 1.197723ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:27Z"
    - latency: 696.828µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:27Z"
    - latency: 1.536149ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-133-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "18454"
    uid: 95bf57f6-c015-4939-be53-f467a8ced3f8
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:54:27Z"
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.946645ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 1.930479ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:00:27Z"
    - latency: 1.825682ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:59:27Z"
    - latency: 1.997753ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:58:27Z"
    - latency: 2.270562ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:27Z"
    - latency: 2.09463ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:27Z"
    - latency: 1.960294ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:27Z"
    - latency: 1.930142ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:27Z"
    - latency: 2.138133ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:27Z"
    - latency: 1.861646ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-135-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "18452"
    uid: fa17f6ff-f9a8-4ec2-824a-16cf498fc3c7
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:54:27Z"
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.696856ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 1.812753ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:00:27Z"
    - latency: 1.651626ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:59:27Z"
    - latency: 1.770274ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:58:27Z"
    - latency: 2.002935ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:27Z"
    - latency: 1.71031ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:27Z"
    - latency: 1.775571ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:27Z"
    - latency: 1.705171ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:27Z"
    - latency: 1.773592ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:27Z"
    - latency: 1.685946ms
      message: 'network-check-target-ip-10-0-135-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:47:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 81c96c2e-4f0c-45ae-a374-e513462efd9e
    resourceVersion: "20488"
    uid: 943e243e-8d15-4369-8eeb-c021c810d9ee
  spec:
    sourcePod: network-check-source-cc88fdd44-h6jqn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:53:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.974µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:05:27Z"
    - latency: 2.304597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:05:27Z"
    - latency: 676.166µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:04:27Z"
    - latency: 1.761158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:04:27Z"
    - latency: 721.233µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:03:27Z"
    - latency: 1.808019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:03:27Z"
    - latency: 899.823µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:02:27Z"
    - latency: 1.585842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:02:27Z"
    - latency: 1.019996ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:01:27Z"
    - latency: 1.505063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:01:27Z"
kind: List
metadata:
  resourceVersion: ""