apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61257"
    uid: 2f63d399-69fd-4c9e-882f-9fee765502f2
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:33:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 867.968µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 869.51µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 903.808µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 870.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 1.263047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 995.704µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:03:10Z"
    - latency: 1.132373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:02:10Z"
    - latency: 851.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:01:10Z"
    - latency: 990.785µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:00:10Z"
    - latency: 949.746µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61259"
    uid: d095309b-ed77-4456-98d1-d2ac1f9a8c3b
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:32:10Z"
      message: 'load-balancer-api-external: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.255814ms
      message: 'load-balancer-api-external: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 10.023862ms
      message: 'load-balancer-api-external: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 5.781076ms
      message: 'load-balancer-api-external: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 9.101717ms
      message: 'load-balancer-api-external: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 6.099434ms
      message: 'load-balancer-api-external: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 11.198688ms
      message: 'load-balancer-api-external: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 5.261035ms
      message: 'load-balancer-api-external: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 7.338609ms
      message: 'load-balancer-api-external: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 5.191621ms
      message: 'load-balancer-api-external: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 11.225214ms
      message: 'load-balancer-api-external: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:04:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61258"
    uid: c54cfb4c-8114-4477-9f60-2444adc677cc
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:32:10Z"
      message: 'load-balancer-api-internal: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.243778ms
      message: 'load-balancer-api-internal: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 10.077653ms
      message: 'load-balancer-api-internal: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 6.499768ms
      message: 'load-balancer-api-internal: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 9.048362ms
      message: 'load-balancer-api-internal: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 7.312952ms
      message: 'load-balancer-api-internal: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 11.159308ms
      message: 'load-balancer-api-internal: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 5.424855ms
      message: 'load-balancer-api-internal: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 7.399646ms
      message: 'load-balancer-api-internal: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 5.546488ms
      message: 'load-balancer-api-internal: tcp connection to a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 11.353863ms
      message: 'load-balancer-api-internal: resolved host name a0b79b354a85347d78a37b685f1ccabb-645e55af395c79b3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:04:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-ip-10-0-130-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61254"
    uid: 237a3c85-4fa2-4090-8ca9-763aa46f772d
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:33:10Z"
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.544036ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 2.225346ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 2.823022ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 2.340899ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 2.191871ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 2.105145ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:03:10Z"
    - latency: 2.390552ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:02:10Z"
    - latency: 2.399159ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:01:10Z"
    - latency: 2.353056ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:00:10Z"
    - latency: 2.046389ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-ip-10-0-131-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61256"
    uid: 90c42613-0237-4165-b562-d94b7a4c5257
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:33:10Z"
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.269335ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 2.212984ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 2.376523ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 2.158374ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 2.228498ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 2.134112ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:03:10Z"
    - latency: 1.921867ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:02:10Z"
    - latency: 1.984958ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:01:10Z"
    - latency: 2.224751ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:00:10Z"
    - latency: 1.895904ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-ip-10-0-132-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61253"
    uid: aadcaf0d-c4b2-4237-91d6-6ffec9133b80
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:33:10Z"
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.277379ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 921.517µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 892.459µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 1.114908ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 893.699µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 851.9µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:03:10Z"
    - latency: 972.327µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:02:10Z"
    - latency: 836.291µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:01:10Z"
    - latency: 1.271063ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:00:10Z"
    - latency: 787.292µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T18:26:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: ec4e0397-e4f1-4a2c-beb2-9916fe4b6ca4
    resourceVersion: "61255"
    uid: 9703321a-347a-4c0c-ba33-dd93dc3f312b
  spec:
    sourcePod: network-check-source-869dcfcdcd-jcfxl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T18:32:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 2.247939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:08:10Z"
    - latency: 1.020357ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 1.744392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:07:10Z"
    - latency: 819.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 2.754011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:06:10Z"
    - latency: 1.237526ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 1.714613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:05:10Z"
    - latency: 958.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:04:10Z"
    - latency: 1.749434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:04:10Z"
kind: List
metadata:
  resourceVersion: ""