apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39632"
    uid: 47e76c42-32e9-4d76-813a-7cd54d168c69
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.132026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:01Z"
    - latency: 1.034807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 1.282426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 1.29343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 1.217379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 778.24µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 1.100217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:01Z"
    - latency: 1.191056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:01Z"
    - latency: 797.299µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:01Z"
    - latency: 1.207955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39059"
    uid: 4b83024e-3389-4cfd-a5a7-5d763b7dc348
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:52:01Z"
      message: 'load-balancer-api-external: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.209106ms
      message: 'load-balancer-api-external: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 7.762634ms
      message: 'load-balancer-api-external: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 6.03884ms
      message: 'load-balancer-api-external: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 7.381981ms
      message: 'load-balancer-api-external: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 6.073168ms
      message: 'load-balancer-api-external: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 6.46665ms
      message: 'load-balancer-api-external: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 5.566835ms
      message: 'load-balancer-api-external: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 6.752432ms
      message: 'load-balancer-api-external: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 6.481621ms
      message: 'load-balancer-api-external: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 7.447015ms
      message: 'load-balancer-api-external: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39060"
    uid: b2d9aba8-3751-4627-8703-9a60bfc97c3e
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:52:01Z"
      message: 'load-balancer-api-internal: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.213718ms
      message: 'load-balancer-api-internal: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 7.694568ms
      message: 'load-balancer-api-internal: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 7.136821ms
      message: 'load-balancer-api-internal: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 7.330452ms
      message: 'load-balancer-api-internal: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 6.082889ms
      message: 'load-balancer-api-internal: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 6.387115ms
      message: 'load-balancer-api-internal: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 5.538472ms
      message: 'load-balancer-api-internal: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 6.688143ms
      message: 'load-balancer-api-internal: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 10.791241ms
      message: 'load-balancer-api-internal: tcp connection to a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 7.482783ms
      message: 'load-balancer-api-internal: resolved host name a0852419f5cea4f18bbd7bb054fed4a8-6bf2ec118d0b0a3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-network-check-target-ip-10-0-129-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39629"
    uid: 085aafee-4301-48e6-ba72-3379b690d3c5
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:01Z"
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.333µs
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:01Z"
    - latency: 1.100673ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 1.604447ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 1.533046ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 882.085µs
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 1.57928ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 980.232µs
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:01Z"
    - latency: 1.192943ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:01Z"
    - latency: 761.096µs
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:01Z"
    - latency: 1.504414ms
      message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-network-check-target-ip-10-0-129-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39630"
    uid: 9ceab67d-8af4-46df-b919-edccd8a1c0c1
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:01Z"
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950575ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:01Z"
    - latency: 1.772968ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 2.207571ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 1.886675ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 2.060869ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 2.217781ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 2.074315ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:01Z"
    - latency: 2.103979ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:01Z"
    - latency: 1.726925ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:01Z"
    - latency: 1.752038ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-network-check-target-ip-10-0-137-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39631"
    uid: 2b06f0e9-d772-4f82-a42e-418c1641d4c9
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:01Z"
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.381004ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:01Z"
    - latency: 2.220482ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 2.322045ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 2.095025ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 2.114919ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 2.499919ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 2.492455ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:01Z"
    - latency: 2.085488ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:01Z"
    - latency: 1.757914ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:01Z"
    - latency: 2.159869ms
      message: 'network-check-target-ip-10-0-137-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-190-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-190.ec2.internal
      uid: bae04284-1679-4c9b-bd09-0e97e0bcd520
    resourceVersion: "39058"
    uid: babac6da-52dc-4ed5-9185-d223e04cb091
  spec:
    sourcePod: network-check-source-6f8b768455-cjdzd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:52:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 2.505059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:01Z"
    - latency: 1.24993ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 1.973613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:01Z"
    - latency: 817.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 2.257819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:01Z"
    - latency: 894.442µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 1.838891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:01Z"
    - latency: 948.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:01Z"
    - latency: 2.193452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:01Z"
kind: List
metadata:
  resourceVersion: ""