apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "76865"
    uid: 355a7999-b252-4c8b-91bd-d56e7fe6683b
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:00:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 877.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:48:52Z"
    - latency: 826.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:47:52Z"
    - latency: 1.078407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:46:52Z"
    - latency: 1.506274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:45:52Z"
    - latency: 844.565µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:44:52Z"
    - latency: 1.133646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:43:52Z"
    - latency: 1.160665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:42:52Z"
    - latency: 975.558µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:41:52Z"
    - latency: 914.317µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:40:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "81014"
    uid: 6937e348-a522-4819-9456-dbef010c8771
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:59:52Z"
      message: 'load-balancer-api-external: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.831717ms
      message: 'load-balancer-api-external: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:53:52Z"
    - latency: 7.173472ms
      message: 'load-balancer-api-external: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:53:52Z"
    - latency: 3.642318ms
      message: 'load-balancer-api-external: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:52:52Z"
    - latency: 8.218835ms
      message: 'load-balancer-api-external: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:52:52Z"
    - latency: 2.920745ms
      message: 'load-balancer-api-external: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:51:52Z"
    - latency: 6.749303ms
      message: 'load-balancer-api-external: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:51:52Z"
    - latency: 3.901243ms
      message: 'load-balancer-api-external: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:50:52Z"
    - latency: 7.014937ms
      message: 'load-balancer-api-external: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:50:52Z"
    - latency: 4.55759ms
      message: 'load-balancer-api-external: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 7.100022ms
      message: 'load-balancer-api-external: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:49:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "81015"
    uid: 6acb9a32-7f8e-409e-90aa-f2e50c76f0a5
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:59:52Z"
      message: 'load-balancer-api-internal: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.82279ms
      message: 'load-balancer-api-internal: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:53:52Z"
    - latency: 7.196374ms
      message: 'load-balancer-api-internal: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:53:52Z"
    - latency: 5.557218ms
      message: 'load-balancer-api-internal: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:52:52Z"
    - latency: 8.297658ms
      message: 'load-balancer-api-internal: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:52:52Z"
    - latency: 2.957799ms
      message: 'load-balancer-api-internal: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:51:52Z"
    - latency: 6.709167ms
      message: 'load-balancer-api-internal: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:51:52Z"
    - latency: 2.730112ms
      message: 'load-balancer-api-internal: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:50:52Z"
    - latency: 7.0801ms
      message: 'load-balancer-api-internal: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:50:52Z"
    - latency: 3.796734ms
      message: 'load-balancer-api-internal: tcp connection to a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 7.031599ms
      message: 'load-balancer-api-internal: resolved host name a5820ab158e7c454cb63614e1bab1503-057ff3c09efa204d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:49:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-ip-10-0-128-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "76862"
    uid: 8fa83bc4-1878-492f-a5a1-932028665eab
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:00:52Z"
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.31µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 857.279µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:48:52Z"
    - latency: 832.801µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:47:52Z"
    - latency: 976.765µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:46:52Z"
    - latency: 1.66895ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:45:52Z"
    - latency: 1.027101ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:44:52Z"
    - latency: 855.523µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:43:52Z"
    - latency: 1.053679ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:42:52Z"
    - latency: 1.34276ms
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:41:52Z"
    - latency: 776.184µs
      message: 'network-check-target-ip-10-0-128-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:40:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-ip-10-0-130-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "76864"
    uid: 41501633-9937-47a7-8ee4-b413c0e82a88
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:00:52Z"
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.544936ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 2.411047ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:48:52Z"
    - latency: 2.49718ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:47:52Z"
    - latency: 2.510469ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:46:52Z"
    - latency: 2.333302ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:45:52Z"
    - latency: 2.255512ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:44:52Z"
    - latency: 2.346602ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:43:52Z"
    - latency: 2.465199ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:42:52Z"
    - latency: 2.313541ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:41:52Z"
    - latency: 2.362196ms
      message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:40:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-ip-10-0-131-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "76863"
    uid: 3975b430-32c7-4959-8560-27b05fd99882
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:00:52Z"
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.995954ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 1.990069ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:48:52Z"
    - latency: 1.972549ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:47:52Z"
    - latency: 1.973065ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:46:52Z"
    - latency: 2.403544ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:45:52Z"
    - latency: 1.745029ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:44:52Z"
    - latency: 1.982335ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:43:52Z"
    - latency: 1.983299ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:42:52Z"
    - latency: 1.912673ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:41:52Z"
    - latency: 2.017294ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:40:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:53:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-146.ec2.internal
      uid: b8b051c0-3879-4fef-bcbf-58e92db67fbe
    resourceVersion: "81013"
    uid: 1c068afa-9c04-4eb6-85ac-062ebf6b0b9f
  spec:
    sourcePod: network-check-source-7d88cb55d8-48xbr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:59:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.383252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:53:52Z"
    - latency: 1.789319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:53:52Z"
    - latency: 1.46982ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:52:52Z"
    - latency: 1.892033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:52:52Z"
    - latency: 1.017415ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:51:52Z"
    - latency: 1.877918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:51:52Z"
    - latency: 975.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:50:52Z"
    - latency: 1.78088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:50:52Z"
    - latency: 1.076065ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T10:49:52Z"
    - latency: 1.817514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T10:49:52Z"
kind: List
metadata:
  resourceVersion: ""