apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32217"
    uid: fddb1c7d-e541-4665-a676-2eed2a00faff
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.235095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 1.002439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 908.118µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 1.002189ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 1.195281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 1.075521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:24:37Z"
    - latency: 1.160759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:23:37Z"
    - latency: 985.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:22:37Z"
    - latency: 988.011µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:21:37Z"
    - latency: 873.085µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:20:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32218"
    uid: ee31ffbd-5b88-4e50-b29d-f986d1950e28
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:53:37Z"
      message: 'load-balancer-api-external: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.826135ms
      message: 'load-balancer-api-external: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 9.410218ms
      message: 'load-balancer-api-external: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 4.743997ms
      message: 'load-balancer-api-external: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 9.098279ms
      message: 'load-balancer-api-external: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 4.678731ms
      message: 'load-balancer-api-external: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 8.161531ms
      message: 'load-balancer-api-external: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 5.193595ms
      message: 'load-balancer-api-external: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 8.268799ms
      message: 'load-balancer-api-external: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 4.521498ms
      message: 'load-balancer-api-external: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 8.045861ms
      message: 'load-balancer-api-external: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32219"
    uid: f2d21553-f651-43e7-bc6e-61fe249798bc
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:53:37Z"
      message: 'load-balancer-api-internal: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.898092ms
      message: 'load-balancer-api-internal: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 9.354558ms
      message: 'load-balancer-api-internal: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 4.834903ms
      message: 'load-balancer-api-internal: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 9.063599ms
      message: 'load-balancer-api-internal: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 4.685373ms
      message: 'load-balancer-api-internal: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 8.066323ms
      message: 'load-balancer-api-internal: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 5.188383ms
      message: 'load-balancer-api-internal: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 8.232496ms
      message: 'load-balancer-api-internal: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 4.496602ms
      message: 'load-balancer-api-internal: tcp connection to ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 7.97653ms
      message: 'load-balancer-api-internal: resolved host name ac27c7dae433b45069bdd88d701f0f05-a309f3df13d33670.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-133-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32214"
    uid: 2dc61bd8-94dd-449e-8637-9f06485605a8
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:37Z"
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.632455ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 2.463451ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 2.155829ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 1.877555ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 2.084064ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 2.085445ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:24:37Z"
    - latency: 2.2808ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:23:37Z"
    - latency: 2.140195ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:22:37Z"
    - latency: 2.029295ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:21:37Z"
    - latency: 2.183257ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:20:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-137-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32213"
    uid: 9731e929-2b87-4910-a5f2-c7a61c5fa97a
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:37Z"
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.56µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 904.191µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 862.106µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 862.683µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 1.034681ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 1.531219ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:24:37Z"
    - latency: 1.004647ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:23:37Z"
    - latency: 1.157868ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:22:37Z"
    - latency: 1.199587ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:21:37Z"
    - latency: 809.552µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:20:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-138-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32215"
    uid: b025f934-ec54-4c63-8062-a4d003647811
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:37Z"
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.257116ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 2.122193ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 2.281255ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 2.017871ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 2.602079ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 2.233629ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:24:37Z"
    - latency: 2.367486ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:23:37Z"
    - latency: 2.678893ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:22:37Z"
    - latency: 2.090794ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:21:37Z"
    - latency: 2.261832ms
      message: 'network-check-target-ip-10-0-138-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:20:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 5c757cc5-29e7-4ee9-bfcc-0496471498f0
    resourceVersion: "32216"
    uid: 0b7ba630-6f98-47da-a80f-aa6418754c25
  spec:
    sourcePod: network-check-source-56499946bc-5khc9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:53:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.031µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 1.714591ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:29:37Z"
    - latency: 1.062969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 1.587835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:28:37Z"
    - latency: 813.629µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 1.647873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:27:37Z"
    - latency: 862.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 1.525428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:26:37Z"
    - latency: 802.372µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:25:37Z"
    - latency: 1.87702ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:25:37Z"
kind: List
metadata:
  resourceVersion: ""