apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "69417"
    uid: 76fdfb45-6df1-4a94-965f-ee8a5b03ff90
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:37:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 1.342551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 1.333441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 1.337047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 1.18458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:01:04Z"
    - latency: 948.275µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:00:04Z"
    - latency: 1.371713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:59:04Z"
    - latency: 1.338985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:58:04Z"
    - latency: 1.062444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:57:04Z"
    - latency: 1.329444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:56:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "70214"
    uid: dddf5ed1-bc51-47da-9ca5-1132c0d7007c
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:36:04Z"
      message: 'load-balancer-api-external: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.020165ms
      message: 'load-balancer-api-external: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:06:04Z"
    - latency: 9.021595ms
      message: 'load-balancer-api-external: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:06:04Z"
    - latency: 4.814486ms
      message: 'load-balancer-api-external: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 7.748272ms
      message: 'load-balancer-api-external: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 4.757742ms
      message: 'load-balancer-api-external: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 8.613444ms
      message: 'load-balancer-api-external: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 4.301626ms
      message: 'load-balancer-api-external: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 8.879377ms
      message: 'load-balancer-api-external: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 7.607141ms
      message: 'load-balancer-api-external: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 9.494239ms
      message: 'load-balancer-api-external: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:02:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "70213"
    uid: b26a0852-0424-466f-8943-6105a61df1a7
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:36:04Z"
      message: 'load-balancer-api-internal: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.388137ms
      message: 'load-balancer-api-internal: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:06:04Z"
    - latency: 8.94111ms
      message: 'load-balancer-api-internal: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:06:04Z"
    - latency: 3.912081ms
      message: 'load-balancer-api-internal: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 7.6953ms
      message: 'load-balancer-api-internal: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 3.533152ms
      message: 'load-balancer-api-internal: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 8.540718ms
      message: 'load-balancer-api-internal: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 4.29714ms
      message: 'load-balancer-api-internal: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 8.931709ms
      message: 'load-balancer-api-internal: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 11.335491ms
      message: 'load-balancer-api-internal: tcp connection to acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 9.356675ms
      message: 'load-balancer-api-internal: resolved host name acbc07ee188364fb4adcd926d4e91768-e586ba5b055f9b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:02:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-ip-10-0-130-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "69416"
    uid: bc3ab5e5-8249-4430-b307-35ba7d34d82e
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:37:04Z"
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.36308ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 2.151741ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 2.463045ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 2.84189ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 2.164774ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:01:04Z"
    - latency: 2.424658ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:00:04Z"
    - latency: 2.426628ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:59:04Z"
    - latency: 2.494033ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:58:04Z"
    - latency: 2.396658ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:57:04Z"
    - latency: 2.183082ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:56:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-ip-10-0-133-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "69414"
    uid: f4eb8245-1e45-41a7-be86-45e86f2a65dc
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:37:04Z"
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087077ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 1.741351ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 1.683183ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 953.758µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 1.381259ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:01:04Z"
    - latency: 1.112007ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:00:04Z"
    - latency: 964.98µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:59:04Z"
    - latency: 1.450746ms
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:58:04Z"
    - latency: 981.275µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:57:04Z"
    - latency: 964.523µs
      message: 'network-check-target-ip-10-0-133-42: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:56:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-ip-10-0-135-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "69415"
    uid: f47a5561-0a6c-46f8-a042-f069bacf8b8f
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:37:04Z"
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063246ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 2.046495ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 2.423408ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 2.492145ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 2.353944ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:01:04Z"
    - latency: 2.580553ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:00:04Z"
    - latency: 2.387966ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:59:04Z"
    - latency: 2.236508ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:58:04Z"
    - latency: 2.367577ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:57:04Z"
    - latency: 2.170662ms
      message: 'network-check-target-ip-10-0-135-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:56:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:30:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-42.ec2.internal
      uid: eb26025f-26b5-41c4-935e-6440567961aa
    resourceVersion: "70211"
    uid: d8479a94-5476-4a59-bf6b-44e80b34fa6b
  spec:
    sourcePod: network-check-source-6f8b768455-pbvpl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:36:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.19614ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:06:04Z"
    - latency: 1.577267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:06:04Z"
    - latency: 923.539µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 1.981986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:05:04Z"
    - latency: 903.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 2.602384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:04:04Z"
    - latency: 1.205888ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 1.815527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:03:04Z"
    - latency: 1.06108ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:02:04Z"
    - latency: 1.881198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T22:02:04Z"
kind: List
metadata:
  resourceVersion: ""