apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22257"
    uid: 2cb18d0b-8836-448a-a8f0-70a096b2a9d2
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:38:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.219µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 1.556253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 1.560149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 1.210287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:56:43Z"
    - latency: 1.082743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:55:43Z"
    - latency: 994.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:54:43Z"
    - latency: 969.531µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:43Z"
    - latency: 1.349905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:43Z"
    - latency: 1.768763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:43Z"
    - latency: 1.057428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22922"
    uid: 6bc5b73a-1ca7-41de-8cc2-eaa0c5a3a7cc
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:37:43Z"
      message: 'load-balancer-api-external: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.685831ms
      message: 'load-balancer-api-external: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:01:43Z"
    - latency: 7.970139ms
      message: 'load-balancer-api-external: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:01:43Z"
    - latency: 4.90742ms
      message: 'load-balancer-api-external: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:00:43Z"
    - latency: 7.731537ms
      message: 'load-balancer-api-external: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:00:43Z"
    - latency: 5.114346ms
      message: 'load-balancer-api-external: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 12.495915ms
      message: 'load-balancer-api-external: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 5.156781ms
      message: 'load-balancer-api-external: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 7.433203ms
      message: 'load-balancer-api-external: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 4.327632ms
      message: 'load-balancer-api-external: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 8.751989ms
      message: 'load-balancer-api-external: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:57:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22921"
    uid: d7d392b9-d0ab-4f80-ae08-f5f5befa75c2
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:37:43Z"
      message: 'load-balancer-api-internal: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.867536ms
      message: 'load-balancer-api-internal: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:01:43Z"
    - latency: 7.878364ms
      message: 'load-balancer-api-internal: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:01:43Z"
    - latency: 4.477338ms
      message: 'load-balancer-api-internal: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:00:43Z"
    - latency: 7.769398ms
      message: 'load-balancer-api-internal: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:00:43Z"
    - latency: 5.065192ms
      message: 'load-balancer-api-internal: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 12.47723ms
      message: 'load-balancer-api-internal: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 5.183175ms
      message: 'load-balancer-api-internal: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 7.463069ms
      message: 'load-balancer-api-internal: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 3.974115ms
      message: 'load-balancer-api-internal: tcp connection to ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 8.956771ms
      message: 'load-balancer-api-internal: resolved host name ac6bd3b14d884479791db715ada2cfba-e7a139cca1659904.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:57:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-network-check-target-ip-10-0-129-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22254"
    uid: 67473b02-67d5-46d6-bf9c-7bc04be77c84
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:38:43Z"
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 756.641µs
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 1.470138ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 896.41µs
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 1.1057ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:56:43Z"
    - latency: 895.514µs
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:55:43Z"
    - latency: 765.62µs
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:54:43Z"
    - latency: 832.619µs
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:43Z"
    - latency: 1.000074ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:43Z"
    - latency: 1.044837ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:43Z"
    - latency: 919.232µs
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-network-check-target-ip-10-0-130-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22256"
    uid: 8851d42d-6195-463e-8b7f-fc24d360ab5b
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:38:43Z"
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.874017ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 2.463808ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 2.299382ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 2.187842ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:56:43Z"
    - latency: 2.134816ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:55:43Z"
    - latency: 2.193083ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:54:43Z"
    - latency: 2.222644ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:43Z"
    - latency: 2.270847ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:43Z"
    - latency: 2.428107ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:43Z"
    - latency: 2.151961ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-network-check-target-ip-10-0-131-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22255"
    uid: e0ab0bc1-8f74-4f6b-9b5c-5f2b50a43ffa
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:38:43Z"
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.798198ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 1.927915ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 1.926154ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 1.826602ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:56:43Z"
    - latency: 1.67753ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:55:43Z"
    - latency: 2.130431ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:54:43Z"
    - latency: 1.940133ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:43Z"
    - latency: 1.700764ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:43Z"
    - latency: 1.783993ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:43Z"
    - latency: 1.889801ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:31:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-199-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-199.ec2.internal
      uid: 9a0e10c1-faa1-43f5-9051-9c14e8154dbb
    resourceVersion: "22920"
    uid: 0fde7a23-7ae1-43ec-ba2b-0c5b11425879
  spec:
    sourcePod: network-check-source-8894fc9bd-ppng7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:37:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075801ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:01:43Z"
    - latency: 1.845346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:01:43Z"
    - latency: 1.165667ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:00:43Z"
    - latency: 2.504934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:00:43Z"
    - latency: 753.045µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 2.029839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:59:43Z"
    - latency: 953.069µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 2.30717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:58:43Z"
    - latency: 1.077628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:57:43Z"
    - latency: 2.05859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:57:43Z"
kind: List
metadata:
  resourceVersion: ""