apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "44492"
    uid: 0b0a0a8b-1a31-4ddf-b5ad-4939aa949464
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:37:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 1.40672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 930.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 896.107µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:55:49Z"
    - latency: 984.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:54:49Z"
    - latency: 921.915µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:53:49Z"
    - latency: 1.025253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:52:49Z"
    - latency: 963.951µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:51:49Z"
    - latency: 852.598µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:50:49Z"
    - latency: 1.014027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:49:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "46800"
    uid: ad9236e6-a91b-4e64-ae32-f1279034ed77
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:36:49Z"
      message: 'load-balancer-api-external: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.332335ms
      message: 'load-balancer-api-external: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T19:00:49Z"
    - latency: 7.519412ms
      message: 'load-balancer-api-external: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T19:00:49Z"
    - latency: 4.71664ms
      message: 'load-balancer-api-external: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:59:49Z"
    - latency: 6.336389ms
      message: 'load-balancer-api-external: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:59:49Z"
    - latency: 4.57145ms
      message: 'load-balancer-api-external: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 6.9962ms
      message: 'load-balancer-api-external: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 3.383341ms
      message: 'load-balancer-api-external: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 8.088786ms
      message: 'load-balancer-api-external: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 4.964769ms
      message: 'load-balancer-api-external: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 6.874462ms
      message: 'load-balancer-api-external: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:56:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "46801"
    uid: 9f0685af-9ee8-4ccf-849f-33e71549d9a3
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:36:49Z"
      message: 'load-balancer-api-internal: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.912802ms
      message: 'load-balancer-api-internal: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T19:00:49Z"
    - latency: 7.451367ms
      message: 'load-balancer-api-internal: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T19:00:49Z"
    - latency: 4.729045ms
      message: 'load-balancer-api-internal: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:59:49Z"
    - latency: 6.395854ms
      message: 'load-balancer-api-internal: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:59:49Z"
    - latency: 3.616133ms
      message: 'load-balancer-api-internal: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 6.902327ms
      message: 'load-balancer-api-internal: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 5.667074ms
      message: 'load-balancer-api-internal: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 8.164347ms
      message: 'load-balancer-api-internal: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 5.116686ms
      message: 'load-balancer-api-internal: tcp connection to ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 6.747551ms
      message: 'load-balancer-api-internal: resolved host name ac5286a55b00f4c23a21358b9f0509df-9127f808d9a55b95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:56:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-network-check-target-ip-10-0-138-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "44488"
    uid: aab4d07c-89f3-45ed-bd48-b57256e1ce79
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:37:49Z"
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.365µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 1.046276ms
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 1.240463ms
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 837.612µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:55:49Z"
    - latency: 1.030356ms
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:54:49Z"
    - latency: 938.863µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:53:49Z"
    - latency: 846.927µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:52:49Z"
    - latency: 768.387µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:51:49Z"
    - latency: 919.416µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:50:49Z"
    - latency: 895.462µs
      message: 'network-check-target-ip-10-0-138-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:49:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-network-check-target-ip-10-0-139-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "44491"
    uid: 7a1f25fd-7a91-4338-be58-97877595b8c0
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:37:49Z"
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.226777ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 1.971788ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 1.860395ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 2.109487ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:55:49Z"
    - latency: 2.096307ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:54:49Z"
    - latency: 2.308503ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:53:49Z"
    - latency: 2.350902ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:52:49Z"
    - latency: 2.016362ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:51:49Z"
    - latency: 1.92128ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:50:49Z"
    - latency: 2.023487ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:49:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-network-check-target-ip-10-0-143-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "44489"
    uid: d5762f94-39f9-4bc6-86fd-03c1aa4566aa
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:37:49Z"
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.163676ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 2.316957ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 2.270751ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 2.079993ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:55:49Z"
    - latency: 1.980381ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:54:49Z"
    - latency: 2.316057ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:53:49Z"
    - latency: 2.996507ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:52:49Z"
    - latency: 2.31031ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:51:49Z"
    - latency: 2.183113ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:50:49Z"
    - latency: 2.28231ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:49:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T18:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-216.ec2.internal
      uid: 74a229e3-f337-49e1-abd0-6d3d208f040f
    resourceVersion: "46798"
    uid: 1335086d-7f04-4cba-809d-51b0443faee8
  spec:
    sourcePod: network-check-source-7f44b6dd87-d7qp2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T18:36:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.512µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T19:00:49Z"
    - latency: 1.675172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T19:00:49Z"
    - latency: 840.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:59:49Z"
    - latency: 2.051593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:59:49Z"
    - latency: 828.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 1.674155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:58:49Z"
    - latency: 758.998µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 1.926679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:57:49Z"
    - latency: 816.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T18:56:49Z"
    - latency: 2.189057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T18:56:49Z"
kind: List
metadata:
  resourceVersion: ""