apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "86202"
    uid: c0cbf57b-6d51-4bcc-a30b-668cac1b1372
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 1.07966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 925.609µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 994.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:49Z"
    - latency: 1.119761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:49Z"
    - latency: 919.806µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:49Z"
    - latency: 1.074881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:49Z"
    - latency: 951.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:49Z"
    - latency: 793.397µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:49Z"
    - latency: 959.907µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "87508"
    uid: d40ab69b-ee09-4ffe-87e7-3a0cc814678b
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:49Z"
      message: 'load-balancer-api-external: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.964113ms
      message: 'load-balancer-api-external: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:49Z"
    - latency: 7.164494ms
      message: 'load-balancer-api-external: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:03:49Z"
    - latency: 4.876766ms
      message: 'load-balancer-api-external: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:49Z"
    - latency: 8.87667ms
      message: 'load-balancer-api-external: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:02:49Z"
    - latency: 4.411866ms
      message: 'load-balancer-api-external: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 7.871082ms
      message: 'load-balancer-api-external: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 4.480361ms
      message: 'load-balancer-api-external: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 8.224234ms
      message: 'load-balancer-api-external: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 5.924319ms
      message: 'load-balancer-api-external: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 7.682375ms
      message: 'load-balancer-api-external: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "87507"
    uid: f021aa58-333f-4223-b9e4-4b98255260bf
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:49Z"
      message: 'load-balancer-api-internal: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.943231ms
      message: 'load-balancer-api-internal: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:49Z"
    - latency: 7.127112ms
      message: 'load-balancer-api-internal: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:03:49Z"
    - latency: 4.716513ms
      message: 'load-balancer-api-internal: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:49Z"
    - latency: 8.788601ms
      message: 'load-balancer-api-internal: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:02:49Z"
    - latency: 4.40229ms
      message: 'load-balancer-api-internal: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 7.901157ms
      message: 'load-balancer-api-internal: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 3.966313ms
      message: 'load-balancer-api-internal: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 8.103479ms
      message: 'load-balancer-api-internal: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 5.807947ms
      message: 'load-balancer-api-internal: tcp connection to a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 7.757719ms
      message: 'load-balancer-api-internal: resolved host name a39f53579758d40e78b683918fd4eea0-08f3d070d5cf15c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-ip-10-0-135-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "86200"
    uid: 0c6f4eb8-3645-44e5-909c-946699b64834
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:49Z"
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.823028ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 1.865793ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 2.48798ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 2.45978ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:49Z"
    - latency: 2.714592ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:49Z"
    - latency: 1.614673ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:49Z"
    - latency: 2.396631ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:49Z"
    - latency: 2.214958ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:49Z"
    - latency: 2.091816ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:49Z"
    - latency: 2.094434ms
      message: 'network-check-target-ip-10-0-135-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-ip-10-0-137-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "86201"
    uid: ce7f41a1-b5db-496b-87a5-378e85595bac
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:49Z"
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.689903ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 2.097755ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 2.247505ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 2.516162ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:49Z"
    - latency: 2.638528ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:49Z"
    - latency: 2.2088ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:49Z"
    - latency: 2.54291ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:49Z"
    - latency: 2.355095ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:49Z"
    - latency: 2.338608ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:49Z"
    - latency: 2.466235ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-ip-10-0-139-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "86199"
    uid: bdbc36dd-d6ed-4ccb-97f6-73a2b829f73e
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:49Z"
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.452814ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 943.029µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 953.497µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 1.746486ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:58:49Z"
    - latency: 1.347623ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:57:49Z"
    - latency: 755.012µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:56:49Z"
    - latency: 931.343µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:55:49Z"
    - latency: 946.027µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:54:49Z"
    - latency: 851.935µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:53:49Z"
    - latency: 979.058µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:52:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c49c6eac-d53c-4eb9-b22c-fafc58d2fd94
    resourceVersion: "87506"
    uid: 4fe8fa3e-5555-4291-9547-df89dd794bba
  spec:
    sourcePod: network-check-source-6f8b768455-dfc9q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.749µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:49Z"
    - latency: 1.661772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:03:49Z"
    - latency: 838.913µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:49Z"
    - latency: 2.333258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:02:49Z"
    - latency: 1.116505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 1.694655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:01:49Z"
    - latency: 866.328µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 1.733989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:00:49Z"
    - latency: 1.032336ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:59:49Z"
    - latency: 1.657649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:59:49Z"
kind: List
metadata:
  resourceVersion: ""