apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "21608"
    uid: 5df7b12e-4b2c-48dd-8a42-48c5ea3fa65d
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:16:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 1.052005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 1.177217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 1.081526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:34:18Z"
    - latency: 1.00145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:33:18Z"
    - latency: 870.602µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:32:18Z"
    - latency: 947.72µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:31:18Z"
    - latency: 1.06096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:30:18Z"
    - latency: 1.054569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:29:18Z"
    - latency: 1.112289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "22721"
    uid: 5e9905fc-21b3-4585-87a5-64f14be2b902
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:15:18Z"
      message: 'load-balancer-api-external: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.166742ms
      message: 'load-balancer-api-external: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:39:18Z"
    - latency: 6.562294ms
      message: 'load-balancer-api-external: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:39:18Z"
    - latency: 3.749178ms
      message: 'load-balancer-api-external: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:38:18Z"
    - latency: 8.44489ms
      message: 'load-balancer-api-external: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:38:18Z"
    - latency: 4.775745ms
      message: 'load-balancer-api-external: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 7.481459ms
      message: 'load-balancer-api-external: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 4.589451ms
      message: 'load-balancer-api-external: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 7.144897ms
      message: 'load-balancer-api-external: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 5.013099ms
      message: 'load-balancer-api-external: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 6.867957ms
      message: 'load-balancer-api-external: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:35:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "22720"
    uid: 5debb4cf-eebb-4111-99bb-4e5a95f78f78
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:15:18Z"
      message: 'load-balancer-api-internal: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.32667ms
      message: 'load-balancer-api-internal: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:39:18Z"
    - latency: 6.664747ms
      message: 'load-balancer-api-internal: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:39:18Z"
    - latency: 3.738906ms
      message: 'load-balancer-api-internal: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:38:18Z"
    - latency: 8.410228ms
      message: 'load-balancer-api-internal: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:38:18Z"
    - latency: 4.942531ms
      message: 'load-balancer-api-internal: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 7.587326ms
      message: 'load-balancer-api-internal: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 4.57543ms
      message: 'load-balancer-api-internal: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 7.108563ms
      message: 'load-balancer-api-internal: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 5.062856ms
      message: 'load-balancer-api-internal: tcp connection to a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 6.913318ms
      message: 'load-balancer-api-internal: resolved host name a3785c85d41a94cf081e32782ccbdaac-868a8e23a37210ad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:35:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-129-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "21605"
    uid: 4466010c-b1c9-460f-a180-7404fc54fc69
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:16:18Z"
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 767.303µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 942.797µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 831.908µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 916.973µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:34:18Z"
    - latency: 1.138554ms
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:33:18Z"
    - latency: 831.344µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:32:18Z"
    - latency: 970.427µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:31:18Z"
    - latency: 1.373615ms
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:30:18Z"
    - latency: 854.142µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:29:18Z"
    - latency: 862.547µs
      message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-130-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "21606"
    uid: e14eae4d-96f2-443c-99c1-c18837556743
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:16:18Z"
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079839ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 1.971596ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 1.973532ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 1.76181ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:34:18Z"
    - latency: 1.869354ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:33:18Z"
    - latency: 1.827332ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:32:18Z"
    - latency: 1.904739ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:31:18Z"
    - latency: 2.293236ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:30:18Z"
    - latency: 2.098098ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:29:18Z"
    - latency: 2.005316ms
      message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-134-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "21607"
    uid: b79faa68-e93e-4579-9838-227557162aff
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:16:18Z"
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.130996ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 2.111706ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 2.233112ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 2.711891ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:34:18Z"
    - latency: 2.24143ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:33:18Z"
    - latency: 2.256886ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:32:18Z"
    - latency: 2.118607ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:31:18Z"
    - latency: 2.276168ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:30:18Z"
    - latency: 2.195179ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:29:18Z"
    - latency: 2.312025ms
      message: 'network-check-target-ip-10-0-134-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:09:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-158-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-158.ec2.internal
      uid: 211b1651-fc46-46b6-9c70-5428c39d8320
    resourceVersion: "22718"
    uid: fc81cdc8-344b-4680-a29b-ed8c452db647
  spec:
    sourcePod: network-check-source-7d88cb55d8-hk9cz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:15:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:39:18Z"
    - latency: 1.91514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:39:18Z"
    - latency: 1.058427ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:38:18Z"
    - latency: 1.851686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:38:18Z"
    - latency: 1.04777ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 2.182212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:37:18Z"
    - latency: 733.282µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 1.943784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:36:18Z"
    - latency: 1.03695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:35:18Z"
    - latency: 1.6349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:35:18Z"
kind: List
metadata:
  resourceVersion: ""