apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "21144"
    uid: bb11aaba-0cbb-4d70-95d1-492a2aeeb471
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.497009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:39Z"
    - latency: 1.52291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:39Z"
    - latency: 1.050778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:39Z"
    - latency: 1.51647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 1.025672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 893.468µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 1.088295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 1.087211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 1.150275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:06:39Z"
    - latency: 1.375508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:05:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "19800"
    uid: 19322dc3-342d-4703-988d-e390c68b0656
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:59:39Z"
      message: 'load-balancer-api-external: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.146258ms
      message: 'load-balancer-api-external: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 9.439855ms
      message: 'load-balancer-api-external: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 5.386696ms
      message: 'load-balancer-api-external: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 9.843831ms
      message: 'load-balancer-api-external: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 5.71736ms
      message: 'load-balancer-api-external: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 8.56944ms
      message: 'load-balancer-api-external: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 6.463872ms
      message: 'load-balancer-api-external: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 10.718183ms
      message: 'load-balancer-api-external: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 6.431406ms
      message: 'load-balancer-api-external: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 8.628818ms
      message: 'load-balancer-api-external: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:07:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "19799"
    uid: c67b13a9-2d37-45fa-b2c7-bd462d2d64cf
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:59:39Z"
      message: 'load-balancer-api-internal: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.564985ms
      message: 'load-balancer-api-internal: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 9.503045ms
      message: 'load-balancer-api-internal: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 6.068458ms
      message: 'load-balancer-api-internal: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 9.823474ms
      message: 'load-balancer-api-internal: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 5.631957ms
      message: 'load-balancer-api-internal: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 8.65ms
      message: 'load-balancer-api-internal: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 6.431375ms
      message: 'load-balancer-api-internal: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 10.632818ms
      message: 'load-balancer-api-internal: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 8.042803ms
      message: 'load-balancer-api-internal: tcp connection to acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 8.702083ms
      message: 'load-balancer-api-internal: resolved host name acc21c554c16745cfa346fc9363ef9af-3e01000dfaa440cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:07:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-ip-10-0-134-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "21141"
    uid: e260cf88-7550-4787-b8fb-afa3f863d263
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063472ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:39Z"
    - latency: 1.081459ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:39Z"
    - latency: 1.047947ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:39Z"
    - latency: 1.003609ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 1.079152ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 864.351µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 1.109573ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 1.106657ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 890.651µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:06:39Z"
    - latency: 1.615245ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:05:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-ip-10-0-134-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "21142"
    uid: 109f0f85-9928-4bce-94be-58a6a86da656
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212269ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:39Z"
    - latency: 2.386013ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:39Z"
    - latency: 2.048233ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:39Z"
    - latency: 2.126113ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 2.356594ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 2.068081ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 1.997317ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 2.395377ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 2.321659ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:06:39Z"
    - latency: 2.160728ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:05:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-ip-10-0-138-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "21143"
    uid: 28172b8d-eec7-4345-ba1a-234650e2aa1b
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.467264ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:39Z"
    - latency: 2.37124ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:39Z"
    - latency: 1.989552ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:39Z"
    - latency: 2.764562ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 2.25522ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 2.217696ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 2.238712ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 2.34295ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 2.230424ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:06:39Z"
    - latency: 2.460472ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:05:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:53:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: f80d460f-00e8-4f0b-b9a4-c854f7d0062d
    resourceVersion: "19798"
    uid: 76b99206-cb65-45da-9547-a9050bdc4091
  spec:
    sourcePod: network-check-source-869dcfcdcd-8bb8m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:59:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.967µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 1.903547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:11:39Z"
    - latency: 1.025946ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 2.310232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:10:39Z"
    - latency: 1.246838ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 1.866584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:09:39Z"
    - latency: 926.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 2.224365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:08:39Z"
    - latency: 1.002232ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:07:39Z"
    - latency: 2.114598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:07:39Z"
kind: List
metadata:
  resourceVersion: ""