apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "54303"
    uid: 69a0f968-7eae-447f-a937-5c7ca27f0d6e
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34: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.106232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 989.048µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 944.504µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 1.062028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 1.125918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:39Z"
    - latency: 1.073548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:39Z"
    - latency: 1.211069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:39Z"
    - latency: 1.204089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:39Z"
    - latency: 1.083534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:39Z"
    - latency: 910.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "55429"
    uid: 81c99f60-b185-44a3-b6e4-12b4efaa1736
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:33:39Z"
      message: 'load-balancer-api-external: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.563945ms
      message: 'load-balancer-api-external: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:39Z"
    - latency: 10.82237ms
      message: 'load-balancer-api-external: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:03:39Z"
    - latency: 4.792842ms
      message: 'load-balancer-api-external: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 10.386515ms
      message: 'load-balancer-api-external: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 4.158376ms
      message: 'load-balancer-api-external: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 8.51624ms
      message: 'load-balancer-api-external: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 4.749747ms
      message: 'load-balancer-api-external: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 8.400995ms
      message: 'load-balancer-api-external: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 4.478392ms
      message: 'load-balancer-api-external: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 12.873504ms
      message: 'load-balancer-api-external: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "55428"
    uid: 36b3fe29-15f5-416f-a20f-c040985533b1
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:33:39Z"
      message: 'load-balancer-api-internal: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.627018ms
      message: 'load-balancer-api-internal: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:39Z"
    - latency: 10.769686ms
      message: 'load-balancer-api-internal: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:03:39Z"
    - latency: 4.789327ms
      message: 'load-balancer-api-internal: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 10.257546ms
      message: 'load-balancer-api-internal: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 5.787659ms
      message: 'load-balancer-api-internal: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 8.625408ms
      message: 'load-balancer-api-internal: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 5.234534ms
      message: 'load-balancer-api-internal: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 8.282649ms
      message: 'load-balancer-api-internal: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 4.384716ms
      message: 'load-balancer-api-internal: tcp connection to ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 12.907545ms
      message: 'load-balancer-api-internal: resolved host name ae3d78000d546488eaaa6a6353b37212-e0e53447f1f09345.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-network-check-target-ip-10-0-128-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "54302"
    uid: 912c5204-e17b-4899-872c-9ae1b8692456
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:39Z"
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306626ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 2.398929ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 1.848312ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 2.273606ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 2.333256ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:39Z"
    - latency: 2.354889ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:39Z"
    - latency: 2.071661ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:39Z"
    - latency: 2.261355ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:39Z"
    - latency: 2.333306ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:39Z"
    - latency: 2.200057ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-network-check-target-ip-10-0-133-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "54301"
    uid: ce2f41f4-024a-48f9-9909-97f1cb8bd032
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:39Z"
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938338ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 1.944173ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 2.151695ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 1.869073ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 2.072804ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:39Z"
    - latency: 2.112834ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:39Z"
    - latency: 1.848518ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:39Z"
    - latency: 1.987196ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:39Z"
    - latency: 1.942814ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:39Z"
    - latency: 1.968595ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-network-check-target-ip-10-0-140-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "54300"
    uid: c33efb02-8a11-49fe-97dc-c7d1f4f3fd6c
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:39Z"
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 811.444µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 899.078µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 808.474µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 1.603733ms
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 912.629µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:39Z"
    - latency: 1.578303ms
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:39Z"
    - latency: 789.181µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:39Z"
    - latency: 832.082µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:39Z"
    - latency: 837.12µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:39Z"
    - latency: 885.371µs
      message: 'network-check-target-ip-10-0-140-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-204.ec2.internal
      uid: e69abd84-6001-4719-a76f-2e1968b9adbb
    resourceVersion: "55427"
    uid: 0d278954-94ef-41e4-b37e-56f49070a9c9
  spec:
    sourcePod: network-check-source-989f8b8dc-cnqtk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:33:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 789.668µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:39Z"
    - latency: 1.596431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:03:39Z"
    - latency: 936.357µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 1.679881ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:02:39Z"
    - latency: 1.439764ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 1.682948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:01:39Z"
    - latency: 1.193237ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 1.594691ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:00:39Z"
    - latency: 928.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:39Z"
    - latency: 2.043784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:39Z"
kind: List
metadata:
  resourceVersion: ""