apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "54525"
    uid: f83ad287-5b5b-4eb0-80ab-d5cb8159ddfd
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:26:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.118324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 907.364µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 1.045878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 911.761µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 980.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:50:38Z"
    - latency: 886.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:38Z"
    - latency: 944.976µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:38Z"
    - latency: 958.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:38Z"
    - latency: 1.049856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:38Z"
    - latency: 1.032056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "55475"
    uid: 75cd3646-7b80-4415-80d5-0f0adcd56bd9
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:25:38Z"
      message: 'load-balancer-api-external: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.489979ms
      message: 'load-balancer-api-external: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:55:38Z"
    - latency: 9.380015ms
      message: 'load-balancer-api-external: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:55:38Z"
    - latency: 4.769753ms
      message: 'load-balancer-api-external: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 6.737772ms
      message: 'load-balancer-api-external: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 7.663529ms
      message: 'load-balancer-api-external: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 8.824747ms
      message: 'load-balancer-api-external: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 5.662176ms
      message: 'load-balancer-api-external: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 8.675471ms
      message: 'load-balancer-api-external: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 3.665208ms
      message: 'load-balancer-api-external: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 8.748021ms
      message: 'load-balancer-api-external: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:51:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "55474"
    uid: 1cf4e56c-60f7-42db-b89a-b19fe987039d
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:25:38Z"
      message: 'load-balancer-api-internal: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.457604ms
      message: 'load-balancer-api-internal: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:55:38Z"
    - latency: 9.485649ms
      message: 'load-balancer-api-internal: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:55:38Z"
    - latency: 5.025579ms
      message: 'load-balancer-api-internal: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 6.749023ms
      message: 'load-balancer-api-internal: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 4.805601ms
      message: 'load-balancer-api-internal: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 8.890434ms
      message: 'load-balancer-api-internal: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 6.286507ms
      message: 'load-balancer-api-internal: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 8.704136ms
      message: 'load-balancer-api-internal: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 3.653574ms
      message: 'load-balancer-api-internal: tcp connection to aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 8.822097ms
      message: 'load-balancer-api-internal: resolved host name aba784e2cb6a34be6b4966b697c47adf-ec621d796787d6fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:51:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-ip-10-0-133-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "54524"
    uid: 2cd945ce-3612-4f55-8971-c595748815d6
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:26:38Z"
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.792592ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 2.617994ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 2.438023ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 2.361974ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 2.543495ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:50:38Z"
    - latency: 2.371823ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:38Z"
    - latency: 2.36546ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:38Z"
    - latency: 2.523057ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:38Z"
    - latency: 2.21426ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:38Z"
    - latency: 2.760527ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-ip-10-0-143-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "54523"
    uid: 4f0db29c-3a27-493e-8367-0251e60897b6
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:26:38Z"
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.347249ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 1.898859ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 2.196056ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 2.284416ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 2.361439ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:50:38Z"
    - latency: 2.124332ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:38Z"
    - latency: 2.367381ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:38Z"
    - latency: 2.255384ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:38Z"
    - latency: 2.178417ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:38Z"
    - latency: 2.243027ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-ip-10-0-143-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "54522"
    uid: c6aac50c-93f9-4558-bf35-8da252dbf818
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:26:38Z"
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.056375ms
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 854.719µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 827.126µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 974.859µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 910.413µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:50:38Z"
    - latency: 978.601µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:38Z"
    - latency: 725.277µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:38Z"
    - latency: 906.956µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:38Z"
    - latency: 910.952µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:38Z"
    - latency: 959.007µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:19:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 02a2cf08-bba9-417f-9893-60574bdeea38
    resourceVersion: "55473"
    uid: edb4a5a9-dad7-4d16-b806-107e8ccce12d
  spec:
    sourcePod: network-check-source-989f8b8dc-kpmsh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:25:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127604ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:55:38Z"
    - latency: 1.573855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:55:38Z"
    - latency: 1.055634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 2.071877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:54:38Z"
    - latency: 964.712µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 1.702127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:53:38Z"
    - latency: 821.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 1.73702ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:52:38Z"
    - latency: 866.287µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:51:38Z"
    - latency: 1.706508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:51:38Z"
kind: List
metadata:
  resourceVersion: ""