apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "38528"
    uid: 07bbd68a-6972-4658-9d70-44d03b81b9e0
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:26:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.177725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:40:11Z"
    - latency: 1.167446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:39:11Z"
    - latency: 803.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:38:11Z"
    - latency: 896.815µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 1.199108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 1.235707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 1.12184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 1.071084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 889.462µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:11Z"
    - latency: 928.104µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "34939"
    uid: 0b126998-5f5b-44cb-9281-4801681f9b2b
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:25:11Z"
      message: 'load-balancer-api-external: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.756254ms
      message: 'load-balancer-api-external: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 8.573443ms
      message: 'load-balancer-api-external: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 6.881323ms
      message: 'load-balancer-api-external: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 8.963036ms
      message: 'load-balancer-api-external: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 3.595053ms
      message: 'load-balancer-api-external: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 8.496877ms
      message: 'load-balancer-api-external: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 5.079623ms
      message: 'load-balancer-api-external: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 9.177876ms
      message: 'load-balancer-api-external: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 5.3436ms
      message: 'load-balancer-api-external: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 9.50062ms
      message: 'load-balancer-api-external: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:33:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "34938"
    uid: 72c9d359-1df6-44d0-9fe3-78ba6916c954
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:25:11Z"
      message: 'load-balancer-api-internal: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.749153ms
      message: 'load-balancer-api-internal: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 8.60087ms
      message: 'load-balancer-api-internal: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 4.324674ms
      message: 'load-balancer-api-internal: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 8.87267ms
      message: 'load-balancer-api-internal: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 4.508702ms
      message: 'load-balancer-api-internal: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 8.414173ms
      message: 'load-balancer-api-internal: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 5.125809ms
      message: 'load-balancer-api-internal: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 9.140742ms
      message: 'load-balancer-api-internal: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 5.384155ms
      message: 'load-balancer-api-internal: tcp connection to a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 9.399391ms
      message: 'load-balancer-api-internal: resolved host name a49e6064f35f845f0b31579e1d003d5b-9a1d386a7e88dc00.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:33:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-network-check-target-ip-10-0-136-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "38526"
    uid: da1ee77f-5f04-4f50-bdb9-e2450195774f
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:26:11Z"
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.801112ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:40:11Z"
    - latency: 2.060562ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:39:11Z"
    - latency: 1.99028ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:38:11Z"
    - latency: 1.843883ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 2.138459ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 1.892185ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 2.155721ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 2.089375ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 2.097399ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:11Z"
    - latency: 2.086293ms
      message: 'network-check-target-ip-10-0-136-169: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-network-check-target-ip-10-0-137-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "38527"
    uid: 42dff7cf-7fbe-4313-87f4-edacd97c1ef2
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:26:11Z"
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.352573ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:40:11Z"
    - latency: 2.061964ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:39:11Z"
    - latency: 2.215157ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:38:11Z"
    - latency: 2.177916ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 2.134415ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 2.234526ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 2.250678ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 2.093531ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 2.340666ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:11Z"
    - latency: 2.165724ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-network-check-target-ip-10-0-137-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "38525"
    uid: 3d145c0e-0d39-462e-8bea-c083954d6c35
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:26:11Z"
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.84µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:40:11Z"
    - latency: 874.756µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:39:11Z"
    - latency: 1.256451ms
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:38:11Z"
    - latency: 973.867µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 1.017427ms
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 980.056µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 1.138003ms
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 798.765µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 984.924µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:11Z"
    - latency: 934.762µs
      message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:19:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-76-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-76.ec2.internal
      uid: 6f5da97c-e9a4-4e5e-8809-7ed61ea28352
    resourceVersion: "34937"
    uid: 3f2e330e-55a8-4e10-9093-f4bc23ab4c72
  spec:
    sourcePod: network-check-source-989f8b8dc-v6h2j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:25:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 775.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 1.864823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:37:11Z"
    - latency: 1.097688ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 1.866011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:36:11Z"
    - latency: 1.105105ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 1.749152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:35:11Z"
    - latency: 830.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 1.814424ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:34:11Z"
    - latency: 831.836µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:11Z"
    - latency: 2.372877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:33:11Z"
kind: List
metadata:
  resourceVersion: ""