apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "56489"
    uid: e88a4e8c-bafd-4e9b-ba03-6ab845cf2071
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:46:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 1.233948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 1.235767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 1.134383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:56Z"
    - latency: 1.010768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:56Z"
    - latency: 1.068878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:56Z"
    - latency: 1.23744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:56Z"
    - latency: 1.425878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:56Z"
    - latency: 1.02198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:56Z"
    - latency: 1.389453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "58290"
    uid: bcab7004-b583-408a-bc97-d62fc1205087
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:45:56Z"
      message: 'load-balancer-api-external: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.700176ms
      message: 'load-balancer-api-external: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:56Z"
    - latency: 8.202974ms
      message: 'load-balancer-api-external: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:09:56Z"
    - latency: 5.282541ms
      message: 'load-balancer-api-external: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:08:56Z"
    - latency: 8.798236ms
      message: 'load-balancer-api-external: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:08:56Z"
    - latency: 3.977857ms
      message: 'load-balancer-api-external: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 9.663588ms
      message: 'load-balancer-api-external: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 4.860823ms
      message: 'load-balancer-api-external: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 8.321466ms
      message: 'load-balancer-api-external: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 3.601204ms
      message: 'load-balancer-api-external: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 8.949379ms
      message: 'load-balancer-api-external: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:05:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "58291"
    uid: f015ce0b-6ae5-4d78-ad9f-dd2f02c414b4
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:45:56Z"
      message: 'load-balancer-api-internal: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.686639ms
      message: 'load-balancer-api-internal: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:56Z"
    - latency: 8.163046ms
      message: 'load-balancer-api-internal: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:09:56Z"
    - latency: 5.293792ms
      message: 'load-balancer-api-internal: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:08:56Z"
    - latency: 8.835873ms
      message: 'load-balancer-api-internal: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:08:56Z"
    - latency: 4.091425ms
      message: 'load-balancer-api-internal: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 9.609234ms
      message: 'load-balancer-api-internal: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 4.858477ms
      message: 'load-balancer-api-internal: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 8.301426ms
      message: 'load-balancer-api-internal: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 3.613262ms
      message: 'load-balancer-api-internal: tcp connection to a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 8.790559ms
      message: 'load-balancer-api-internal: resolved host name a4e69fc72a6de4f2a99cb707d1236ac8-25a57e449a88264d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:05:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-network-check-target-ip-10-0-128-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "56485"
    uid: 1b809cc0-14fb-450b-8b13-99ca1e22d0af
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:46:56Z"
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.628461ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 1.090737ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 897.444µs
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 979.556µs
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:56Z"
    - latency: 1.160929ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:56Z"
    - latency: 1.273797ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:56Z"
    - latency: 1.339801ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:56Z"
    - latency: 1.570582ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:56Z"
    - latency: 881.44µs
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:56Z"
    - latency: 1.799353ms
      message: 'network-check-target-ip-10-0-128-189: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-network-check-target-ip-10-0-129-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "56487"
    uid: 7b645b51-45ea-4337-836e-c6b18a8811b7
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:46:56Z"
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264559ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 2.379122ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 2.502412ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 2.499407ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:56Z"
    - latency: 2.400778ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:56Z"
    - latency: 2.308557ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:56Z"
    - latency: 2.147752ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:56Z"
    - latency: 2.77101ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:56Z"
    - latency: 2.443091ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:56Z"
    - latency: 2.300201ms
      message: 'network-check-target-ip-10-0-129-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-network-check-target-ip-10-0-141-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "56486"
    uid: 4e15cfb1-585e-4754-9441-a47c5312222a
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:46:56Z"
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250195ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 2.092548ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 2.305395ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 2.64051ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:04:56Z"
    - latency: 2.55946ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:56Z"
    - latency: 2.376269ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:56Z"
    - latency: 2.512789ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:56Z"
    - latency: 2.37385ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:56Z"
    - latency: 2.379385ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:56Z"
    - latency: 2.582726ms
      message: 'network-check-target-ip-10-0-141-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-189.ec2.internal
      uid: 227b90ea-e0e7-4667-b48a-a3d55cc0cf1e
    resourceVersion: "58288"
    uid: 3ba9847f-05e2-41cc-960c-a01328049add
  spec:
    sourcePod: network-check-source-6f8b768455-6nqxb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:45:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:56Z"
    - latency: 1.987379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:09:56Z"
    - latency: 942.135µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:08:56Z"
    - latency: 1.809465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:08:56Z"
    - latency: 997.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 2.002307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:07:56Z"
    - latency: 1.209715ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 1.898308ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:06:56Z"
    - latency: 814.552µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:05:56Z"
    - latency: 1.88167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:05:56Z"
kind: List
metadata:
  resourceVersion: ""