apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "53083"
    uid: 695fd993-5afa-4038-bab9-86658bee6d33
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:50:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 930.305µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 957.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 900.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:08:28Z"
    - latency: 1.334332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:07:28Z"
    - latency: 1.394361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:06:28Z"
    - latency: 1.22455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:05:28Z"
    - latency: 1.10203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:04:28Z"
    - latency: 1.25837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:03:28Z"
    - latency: 1.093844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:02:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "55115"
    uid: 16b4d681-b8a3-4d45-a031-2a4b525b1471
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:49:28Z"
      message: 'load-balancer-api-external: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.905017ms
      message: 'load-balancer-api-external: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:13:28Z"
    - latency: 6.65644ms
      message: 'load-balancer-api-external: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:13:28Z"
    - latency: 4.95594ms
      message: 'load-balancer-api-external: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:12:28Z"
    - latency: 7.536362ms
      message: 'load-balancer-api-external: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:12:28Z"
    - latency: 4.126984ms
      message: 'load-balancer-api-external: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 7.673026ms
      message: 'load-balancer-api-external: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 4.090074ms
      message: 'load-balancer-api-external: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 8.047237ms
      message: 'load-balancer-api-external: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 4.456391ms
      message: 'load-balancer-api-external: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 8.721918ms
      message: 'load-balancer-api-external: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:09:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "55114"
    uid: bdc9d616-5f80-4479-88d6-98ff14d448e8
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:49:28Z"
      message: 'load-balancer-api-internal: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.902075ms
      message: 'load-balancer-api-internal: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:13:28Z"
    - latency: 6.675391ms
      message: 'load-balancer-api-internal: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:13:28Z"
    - latency: 5.006245ms
      message: 'load-balancer-api-internal: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:12:28Z"
    - latency: 7.430391ms
      message: 'load-balancer-api-internal: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:12:28Z"
    - latency: 4.154994ms
      message: 'load-balancer-api-internal: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 7.661091ms
      message: 'load-balancer-api-internal: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 4.145524ms
      message: 'load-balancer-api-internal: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 7.969164ms
      message: 'load-balancer-api-internal: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 4.430285ms
      message: 'load-balancer-api-internal: tcp connection to a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 8.666037ms
      message: 'load-balancer-api-internal: resolved host name a19d3e2f2458048b2bca35df1a3ca2f4-06ffaae7875dbee4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:09:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-network-check-target-ip-10-0-128-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "53080"
    uid: aaa94faf-9e59-482c-bdb0-ec924e7759ff
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:50:28Z"
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.866µs
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 1.197886ms
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 1.358432ms
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 952.433µs
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:08:28Z"
    - latency: 843.922µs
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:07:28Z"
    - latency: 1.576699ms
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:06:28Z"
    - latency: 1.087672ms
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:05:28Z"
    - latency: 1.401091ms
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:04:28Z"
    - latency: 2.135682ms
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:03:28Z"
    - latency: 887.283µs
      message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:02:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-network-check-target-ip-10-0-139-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "53081"
    uid: c203075b-62d6-4c18-b539-6fc6a34a19c4
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:50:28Z"
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.348038ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 2.27264ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 2.515ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 2.447633ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:08:28Z"
    - latency: 2.334528ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:07:28Z"
    - latency: 2.360747ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:06:28Z"
    - latency: 2.150139ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:05:28Z"
    - latency: 2.457582ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:04:28Z"
    - latency: 2.992906ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:03:28Z"
    - latency: 2.222552ms
      message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:02:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-network-check-target-ip-10-0-143-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "53082"
    uid: e62304f1-ca23-4fe1-8ff0-e1116ee09baa
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:50:28Z"
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.683832ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 2.384485ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 2.467405ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 2.605579ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:08:28Z"
    - latency: 2.920934ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:07:28Z"
    - latency: 2.679932ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:06:28Z"
    - latency: 2.354746ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:05:28Z"
    - latency: 2.399946ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:04:28Z"
    - latency: 2.591421ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:03:28Z"
    - latency: 2.418488ms
      message: 'network-check-target-ip-10-0-143-244: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:02:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T04:43:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-18-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-18.ec2.internal
      uid: 943008c2-3966-4822-ad94-040b8607bafc
    resourceVersion: "55113"
    uid: 8963da9f-9a33-41c2-8c85-550287f0e9f8
  spec:
    sourcePod: network-check-source-6f8b768455-r2m4h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:49:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.065032ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:13:28Z"
    - latency: 1.750314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:13:28Z"
    - latency: 1.004575ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:12:28Z"
    - latency: 1.963118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:12:28Z"
    - latency: 963.064µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 1.9403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:11:28Z"
    - latency: 1.084196ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 1.908739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:10:28Z"
    - latency: 972.887µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T05:09:28Z"
    - latency: 1.624697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T05:09:28Z"
kind: List
metadata:
  resourceVersion: ""