apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32532"
    uid: 62ca7158-56b7-4cf6-a084-ac210291a501
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:26:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 930.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 843.591µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 849.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 1.272263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 764.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 949.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:56:26Z"
    - latency: 1.171077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:55:26Z"
    - latency: 829.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:54:26Z"
    - latency: 739.922µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:53:26Z"
    - latency: 1.020077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:52:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32534"
    uid: 37910d5a-9bf2-4020-8479-f3c61d3a6058
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:25:26Z"
      message: 'load-balancer-api-external: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.131548ms
      message: 'load-balancer-api-external: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 7.106375ms
      message: 'load-balancer-api-external: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 5.408952ms
      message: 'load-balancer-api-external: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 6.936402ms
      message: 'load-balancer-api-external: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 4.242425ms
      message: 'load-balancer-api-external: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 7.221905ms
      message: 'load-balancer-api-external: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 4.892028ms
      message: 'load-balancer-api-external: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 6.979961ms
      message: 'load-balancer-api-external: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 5.370708ms
      message: 'load-balancer-api-external: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 7.246864ms
      message: 'load-balancer-api-external: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:57:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32533"
    uid: 69a9c2fa-4f14-41f9-b706-a181396c4142
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:25:26Z"
      message: 'load-balancer-api-internal: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.109202ms
      message: 'load-balancer-api-internal: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 7.034575ms
      message: 'load-balancer-api-internal: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 5.381624ms
      message: 'load-balancer-api-internal: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 6.853496ms
      message: 'load-balancer-api-internal: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 4.10974ms
      message: 'load-balancer-api-internal: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 7.155406ms
      message: 'load-balancer-api-internal: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 4.646134ms
      message: 'load-balancer-api-internal: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 6.9225ms
      message: 'load-balancer-api-internal: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 4.984456ms
      message: 'load-balancer-api-internal: tcp connection to af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 7.145776ms
      message: 'load-balancer-api-internal: resolved host name af13492f0f551461c90123b8d350690b-089741d8bdac694a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:57:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-network-check-target-ip-10-0-130-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32528"
    uid: e55495f4-00b0-4d2e-9082-8dec76e5ed70
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:26:26Z"
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.096861ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 858.645µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 824.079µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 1.609578ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 732.982µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 810.412µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:56:26Z"
    - latency: 905.006µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:55:26Z"
    - latency: 1.370579ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:54:26Z"
    - latency: 744.304µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:53:26Z"
    - latency: 853.094µs
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:52:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-network-check-target-ip-10-0-138-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32529"
    uid: 814d4c2f-82c2-4972-8b01-99c5b667a9ee
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:26:26Z"
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.989187ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 2.033914ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 2.355139ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 2.087826ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 2.016969ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 2.216429ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:56:26Z"
    - latency: 2.341236ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:55:26Z"
    - latency: 2.344993ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:54:26Z"
    - latency: 1.990732ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:53:26Z"
    - latency: 2.165778ms
      message: 'network-check-target-ip-10-0-138-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:52:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-network-check-target-ip-10-0-141-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32531"
    uid: cea69215-640a-4eea-ba9c-ae1b11686340
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:26:26Z"
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272595ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 2.090356ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 2.627295ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 2.378811ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 2.60624ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 2.097079ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:56:26Z"
    - latency: 2.129268ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:55:26Z"
    - latency: 2.346511ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:54:26Z"
    - latency: 1.980488ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:53:26Z"
    - latency: 2.302119ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:52:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-227.ec2.internal
      uid: 363a20e6-86ec-4897-9074-b379b694e6e3
    resourceVersion: "32530"
    uid: 7ca0be9a-b85f-41f0-b244-6b564a2c2140
  spec:
    sourcePod: network-check-source-8894fc9bd-vvx4n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:25:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.041µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 1.665782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:01:26Z"
    - latency: 992.786µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 1.60569ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:00:26Z"
    - latency: 871.606µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 1.608859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:59:26Z"
    - latency: 1.242064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 1.731206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:58:26Z"
    - latency: 1.026652ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:57:26Z"
    - latency: 1.655655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:57:26Z"
kind: List
metadata:
  resourceVersion: ""