apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "67264"
    uid: 93d746fc-fbdc-4607-873a-9c6aeaaed926
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:03:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:31:34Z"
    - latency: 1.099319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:30:34Z"
    - latency: 1.312331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:29:34Z"
    - latency: 946.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:28:34Z"
    - latency: 1.142871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:27:34Z"
    - latency: 1.002466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 1.092999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 1.029813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 838.831µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 990.999µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "62982"
    uid: 3772df0d-c8d1-47cb-b4ab-d7a531a21eed
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:02:34Z"
      message: 'load-balancer-api-external: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.748432ms
      message: 'load-balancer-api-external: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 6.063259ms
      message: 'load-balancer-api-external: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 4.935276ms
      message: 'load-balancer-api-external: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 7.257835ms
      message: 'load-balancer-api-external: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 4.050111ms
      message: 'load-balancer-api-external: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 6.830729ms
      message: 'load-balancer-api-external: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 3.568727ms
      message: 'load-balancer-api-external: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 6.969508ms
      message: 'load-balancer-api-external: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 4.4059ms
      message: 'load-balancer-api-external: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
    - latency: 6.455626ms
      message: 'load-balancer-api-external: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:22:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "62981"
    uid: 5bf99bb7-ff1f-4217-ad95-c1550c5602ce
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:02:34Z"
      message: 'load-balancer-api-internal: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.714932ms
      message: 'load-balancer-api-internal: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 6.086525ms
      message: 'load-balancer-api-internal: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 4.97039ms
      message: 'load-balancer-api-internal: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 7.133229ms
      message: 'load-balancer-api-internal: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 4.284508ms
      message: 'load-balancer-api-internal: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 6.810576ms
      message: 'load-balancer-api-internal: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 3.40326ms
      message: 'load-balancer-api-internal: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 6.833138ms
      message: 'load-balancer-api-internal: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 4.390662ms
      message: 'load-balancer-api-internal: tcp connection to a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
    - latency: 6.426757ms
      message: 'load-balancer-api-internal: resolved host name a4136debc3fa249c2b319cf64fcbc532-c43008baffe81bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:22:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-ip-10-0-138-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "67263"
    uid: 1d47c445-a9e2-4ef6-8cea-88955459ebd3
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:03:34Z"
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.883475ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:31:34Z"
    - latency: 1.924339ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:30:34Z"
    - latency: 2.244963ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:29:34Z"
    - latency: 2.253262ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:28:34Z"
    - latency: 1.852548ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:27:34Z"
    - latency: 2.345806ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 2.22337ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 1.95645ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 2.274836ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 2.278321ms
      message: 'network-check-target-ip-10-0-138-23: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-ip-10-0-138-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "67261"
    uid: 57e053fc-6000-4bfc-baf6-de4f622ed327
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:03:34Z"
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.093µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:31:34Z"
    - latency: 914.088µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:30:34Z"
    - latency: 1.052595ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:29:34Z"
    - latency: 945.898µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:28:34Z"
    - latency: 1.412228ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:27:34Z"
    - latency: 867.302µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 980.315µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 1.017859ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 1.466821ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 988.371µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-ip-10-0-141-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "67262"
    uid: 98161b7d-47e0-409d-88aa-82408054c4d6
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:03:34Z"
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.013364ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:31:34Z"
    - latency: 1.85034ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:30:34Z"
    - latency: 1.859782ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:29:34Z"
    - latency: 1.967364ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:28:34Z"
    - latency: 1.810305ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:27:34Z"
    - latency: 1.850202ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 1.713297ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 1.963828ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 1.887625ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 1.941865ms
      message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:56:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: 3e0f5052-8685-417a-b817-e7be358244cf
    resourceVersion: "62979"
    uid: a9b9c594-9f9a-4b29-b01c-4ae2f130dbeb
  spec:
    sourcePod: network-check-source-6f8b768455-4x8n6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:02:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.355145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 1.82337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:26:34Z"
    - latency: 763.062µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 1.879884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:25:34Z"
    - latency: 943.557µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 1.925406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:24:34Z"
    - latency: 992.274µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 1.774268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:23:34Z"
    - latency: 1.326013ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:34Z"
    - latency: 1.776072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:22:34Z"
kind: List
metadata:
  resourceVersion: ""