apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "53690"
    uid: 4835d8fd-a609-4324-abb1-c524c131dba6
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:35:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.395612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 1.165266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 972.61µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 1.00068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 1.353327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:21Z"
    - latency: 1.101895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:21Z"
    - latency: 1.411331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:21Z"
    - latency: 959.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:21Z"
    - latency: 976.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:55:21Z"
    - latency: 1.462013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:54:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "54455"
    uid: 24427b85-0ad0-44c1-8059-ff6c6a457e50
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:34:21Z"
      message: 'load-balancer-api-external: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.585156ms
      message: 'load-balancer-api-external: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:21Z"
    - latency: 6.947941ms
      message: 'load-balancer-api-external: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:04:21Z"
    - latency: 5.150891ms
      message: 'load-balancer-api-external: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 7.337194ms
      message: 'load-balancer-api-external: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 4.735462ms
      message: 'load-balancer-api-external: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 6.261134ms
      message: 'load-balancer-api-external: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 4.150317ms
      message: 'load-balancer-api-external: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 7.119004ms
      message: 'load-balancer-api-external: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 5.275555ms
      message: 'load-balancer-api-external: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 6.509263ms
      message: 'load-balancer-api-external: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:00:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "54454"
    uid: edcfbe53-ded6-41d7-99e8-a862ee9751de
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:34:21Z"
      message: 'load-balancer-api-internal: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.835882ms
      message: 'load-balancer-api-internal: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:21Z"
    - latency: 6.852908ms
      message: 'load-balancer-api-internal: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:04:21Z"
    - latency: 5.176883ms
      message: 'load-balancer-api-internal: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 7.397936ms
      message: 'load-balancer-api-internal: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 3.730329ms
      message: 'load-balancer-api-internal: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 6.157821ms
      message: 'load-balancer-api-internal: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 4.153608ms
      message: 'load-balancer-api-internal: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 7.087852ms
      message: 'load-balancer-api-internal: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 5.26456ms
      message: 'load-balancer-api-internal: tcp connection to a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 6.41503ms
      message: 'load-balancer-api-internal: resolved host name a992d40e8cd4b40389521784d13f1a71-6812150ce31e7bc2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:00:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-network-check-target-ip-10-0-129-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "53687"
    uid: 2ed715a3-efdb-4212-9547-9f8c0c3c1376
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:35:21Z"
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.111447ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 2.033638ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 2.229926ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 2.292624ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 2.335596ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:21Z"
    - latency: 2.174717ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:21Z"
    - latency: 2.065803ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:21Z"
    - latency: 2.246395ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:21Z"
    - latency: 2.727687ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:55:21Z"
    - latency: 2.774532ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:54:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-network-check-target-ip-10-0-136-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "53689"
    uid: c14afb3f-5f18-4489-9175-f5ec1a368076
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:35:21Z"
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.356219ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 2.69093ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 2.588808ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 2.243167ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 2.874175ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:21Z"
    - latency: 2.515174ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:21Z"
    - latency: 2.120842ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:21Z"
    - latency: 2.650173ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:21Z"
    - latency: 2.523054ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:55:21Z"
    - latency: 2.500525ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:54:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-network-check-target-ip-10-0-137-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "53688"
    uid: 1f4dae2c-09b0-4f61-b5d7-86105decfb4c
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:35:21Z"
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.358375ms
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 921.304µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 986.202µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 908.578µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 1.442909ms
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:59:21Z"
    - latency: 1.436578ms
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:58:21Z"
    - latency: 855.5µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:57:21Z"
    - latency: 798.794µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:56:21Z"
    - latency: 965.261µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:55:21Z"
    - latency: 842.322µs
      message: 'network-check-target-ip-10-0-137-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:54:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T17:28:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-197.ec2.internal
      uid: 02907513-e27f-4621-b811-dd250d67fb55
    resourceVersion: "54453"
    uid: 80c51847-6ba8-4b0a-9be5-540b90e63c7d
  spec:
    sourcePod: network-check-source-989f8b8dc-2c8q8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T17:34:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.177508ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:04:21Z"
    - latency: 1.783495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:04:21Z"
    - latency: 898.745µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 1.834597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:03:21Z"
    - latency: 1.199864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 1.740432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:02:21Z"
    - latency: 953.257µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 1.916557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:01:21Z"
    - latency: 797.252µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:00:21Z"
    - latency: 1.746927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:00:21Z"
kind: List
metadata:
  resourceVersion: ""