apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "19407"
    uid: 2cd94e3e-e707-433c-aad9-d11f23fbd294
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:43:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 945.508µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 939.435µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:55:29Z"
    - latency: 834.178µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:54:29Z"
    - latency: 799.917µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:53:29Z"
    - latency: 888.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:52:29Z"
    - latency: 1.037089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:51:29Z"
    - latency: 1.143124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:50:29Z"
    - latency: 1.221229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:49:29Z"
    - latency: 1.104114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:48:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "20594"
    uid: 509f45b3-cb3c-4ca3-94f7-2ffce90cc129
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:42:29Z"
      message: 'load-balancer-api-external: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.558588ms
      message: 'load-balancer-api-external: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T10:00:29Z"
    - latency: 6.326753ms
      message: 'load-balancer-api-external: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T10:00:29Z"
    - latency: 4.502739ms
      message: 'load-balancer-api-external: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:59:29Z"
    - latency: 6.356203ms
      message: 'load-balancer-api-external: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:59:29Z"
    - latency: 5.076573ms
      message: 'load-balancer-api-external: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:58:29Z"
    - latency: 6.34986ms
      message: 'load-balancer-api-external: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:58:29Z"
    - latency: 5.208098ms
      message: 'load-balancer-api-external: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 6.088055ms
      message: 'load-balancer-api-external: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 5.076657ms
      message: 'load-balancer-api-external: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 6.602135ms
      message: 'load-balancer-api-external: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "20595"
    uid: 7e5f2784-47da-4cc3-913d-ca26f76fd581
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:42:29Z"
      message: 'load-balancer-api-internal: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.857913ms
      message: 'load-balancer-api-internal: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T10:00:29Z"
    - latency: 6.301041ms
      message: 'load-balancer-api-internal: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T10:00:29Z"
    - latency: 5.56497ms
      message: 'load-balancer-api-internal: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:59:29Z"
    - latency: 6.441132ms
      message: 'load-balancer-api-internal: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:59:29Z"
    - latency: 5.046351ms
      message: 'load-balancer-api-internal: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:58:29Z"
    - latency: 6.312703ms
      message: 'load-balancer-api-internal: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:58:29Z"
    - latency: 5.21794ms
      message: 'load-balancer-api-internal: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 6.178351ms
      message: 'load-balancer-api-internal: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 5.026233ms
      message: 'load-balancer-api-internal: tcp connection to a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 6.683111ms
      message: 'load-balancer-api-internal: resolved host name a174a22a13d344c069cbc7d5a48b5d6b-a8e812e128a733ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-network-check-target-ip-10-0-135-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "19405"
    uid: 24fc547b-87fd-4302-acf8-b8f4734e35d9
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:43:29Z"
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 725.464µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 745.058µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 1.4002ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:55:29Z"
    - latency: 924.378µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:54:29Z"
    - latency: 725.185µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:53:29Z"
    - latency: 1.217488ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:52:29Z"
    - latency: 878.353µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:51:29Z"
    - latency: 1.090426ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:50:29Z"
    - latency: 844.476µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:49:29Z"
    - latency: 899.846µs
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:48:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-network-check-target-ip-10-0-135-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "19406"
    uid: a2f62819-41a0-4aaf-9c41-d3571a4090c7
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:43:29Z"
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.863818ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 1.894566ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 1.937544ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:55:29Z"
    - latency: 1.54965ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:54:29Z"
    - latency: 1.698384ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:53:29Z"
    - latency: 1.994754ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:52:29Z"
    - latency: 2.044522ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:51:29Z"
    - latency: 1.973329ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:50:29Z"
    - latency: 2.050527ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:49:29Z"
    - latency: 1.92993ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:48:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-network-check-target-ip-10-0-138-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "19404"
    uid: 66080c31-a318-49b9-8bbc-6b8b86643ebd
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:43:29Z"
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.847358ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 2.290294ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 2.025264ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:55:29Z"
    - latency: 1.777864ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:54:29Z"
    - latency: 2.063405ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:53:29Z"
    - latency: 1.820388ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:52:29Z"
    - latency: 2.043263ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:51:29Z"
    - latency: 2.06253ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:50:29Z"
    - latency: 2.084983ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:49:29Z"
    - latency: 1.953511ms
      message: 'network-check-target-ip-10-0-138-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:48:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T09:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-232.ec2.internal
      uid: a275f756-2ffc-460f-bb0b-a5840fce0743
    resourceVersion: "20593"
    uid: 7135e2c3-00f4-4c8a-8c7b-38be56ef4918
  spec:
    sourcePod: network-check-source-7f44b6dd87-6vh2t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T09:42:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.598µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T10:00:29Z"
    - latency: 1.670486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T10:00:29Z"
    - latency: 1.093919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:59:29Z"
    - latency: 1.744055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:59:29Z"
    - latency: 1.034963ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:58:29Z"
    - latency: 1.6609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:58:29Z"
    - latency: 1.093001ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 1.629346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:57:29Z"
    - latency: 940.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T09:56:29Z"
    - latency: 1.96677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T09:56:29Z"
kind: List
metadata:
  resourceVersion: ""