apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58117"
    uid: 145105f4-49bb-4b27-97d5-cbd9a609ca5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.117662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 1.247207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 1.135721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 903.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 1.190265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 1.134137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:52:46Z"
    - latency: 1.146267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:51:46Z"
    - latency: 1.0428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:50:46Z"
    - latency: 1.364306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:49:46Z"
    - latency: 980.713µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58121"
    uid: b55f506f-def9-43f9-af92-41de122c1937
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:21:46Z"
      message: 'load-balancer-api-external: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.658448ms
      message: 'load-balancer-api-external: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 7.867329ms
      message: 'load-balancer-api-external: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 5.298271ms
      message: 'load-balancer-api-external: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 7.771722ms
      message: 'load-balancer-api-external: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 5.186056ms
      message: 'load-balancer-api-external: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 7.822345ms
      message: 'load-balancer-api-external: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 5.003503ms
      message: 'load-balancer-api-external: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 8.20537ms
      message: 'load-balancer-api-external: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 6.272275ms
      message: 'load-balancer-api-external: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 8.266901ms
      message: 'load-balancer-api-external: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:53:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58122"
    uid: 7b047567-8a88-4e2b-bfe9-343ff4b32cce
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:21:46Z"
      message: 'load-balancer-api-internal: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.704656ms
      message: 'load-balancer-api-internal: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 7.823419ms
      message: 'load-balancer-api-internal: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 5.450614ms
      message: 'load-balancer-api-internal: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 7.740286ms
      message: 'load-balancer-api-internal: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 5.186223ms
      message: 'load-balancer-api-internal: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 7.972806ms
      message: 'load-balancer-api-internal: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 5.022699ms
      message: 'load-balancer-api-internal: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 8.137753ms
      message: 'load-balancer-api-internal: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 6.270254ms
      message: 'load-balancer-api-internal: tcp connection to aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 8.287591ms
      message: 'load-balancer-api-internal: resolved host name aedb2db4e550c47778c40542e0df46cc-a67a860a486ad37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:53:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-130-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58118"
    uid: 2312ac91-ad56-4d37-80d7-ed5e70302f4e
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:46Z"
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.238191ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 2.294814ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 1.858822ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 2.068763ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 2.285518ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 2.188504ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:52:46Z"
    - latency: 2.218464ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:51:46Z"
    - latency: 2.249229ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:50:46Z"
    - latency: 1.969077ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:49:46Z"
    - latency: 2.056753ms
      message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-137-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58120"
    uid: c96c4371-9251-4052-b50e-249dc11bd6a0
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:46Z"
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.836901ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 1.879381ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 1.96016ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 2.061917ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 2.046675ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 2.3288ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:52:46Z"
    - latency: 2.257656ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:51:46Z"
    - latency: 2.044444ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:50:46Z"
    - latency: 2.422773ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:49:46Z"
    - latency: 1.881946ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-139-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58119"
    uid: 928956c0-c9e1-41b8-9eff-245f300e8166
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:46Z"
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.872µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 964.664µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 861.225µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 1.126921ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 916.707µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 1.331259ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:52:46Z"
    - latency: 1.585135ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:51:46Z"
    - latency: 829.348µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:50:46Z"
    - latency: 1.095577ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:49:46Z"
    - latency: 1.031417ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 2d231c4f-c01b-48c9-93b2-8c1e810f57a2
    resourceVersion: "58116"
    uid: 218edd3e-ba6d-4d5c-92dc-579d0ecd421b
  spec:
    sourcePod: network-check-source-7d88cb55d8-2hvf8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:21:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.179197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 1.713768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:57:46Z"
    - latency: 1.151144ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 1.885658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:56:46Z"
    - latency: 917.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 1.80015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:55:46Z"
    - latency: 775.068µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 1.752359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:54:46Z"
    - latency: 1.146823ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:53:46Z"
    - latency: 1.719323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:53:46Z"
kind: List
metadata:
  resourceVersion: ""