apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "71441"
    uid: a7493cc3-ddfc-44b2-85fe-782dbfda7032
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:37:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:19:23Z"
    - latency: 1.51139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 1.00469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 887.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 1.140271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 973.922µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 1.055241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:13:23Z"
    - latency: 1.206942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:12:23Z"
    - latency: 1.213113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:11:23Z"
    - latency: 1.024404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:10:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "70340"
    uid: 6968b969-9cd9-424e-be21-6d0b54774d16
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:36:23Z"
      message: 'load-balancer-api-external: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.966125ms
      message: 'load-balancer-api-external: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 9.382549ms
      message: 'load-balancer-api-external: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 5.695099ms
      message: 'load-balancer-api-external: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 8.946968ms
      message: 'load-balancer-api-external: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 5.59729ms
      message: 'load-balancer-api-external: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 8.604796ms
      message: 'load-balancer-api-external: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 5.52292ms
      message: 'load-balancer-api-external: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 11.97991ms
      message: 'load-balancer-api-external: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 5.369307ms
      message: 'load-balancer-api-external: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 9.563182ms
      message: 'load-balancer-api-external: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:14:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "70339"
    uid: b629ad9b-420e-428d-a077-f4f50505b789
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:36:23Z"
      message: 'load-balancer-api-internal: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.940004ms
      message: 'load-balancer-api-internal: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 9.470293ms
      message: 'load-balancer-api-internal: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 5.323093ms
      message: 'load-balancer-api-internal: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 9.070467ms
      message: 'load-balancer-api-internal: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 5.571551ms
      message: 'load-balancer-api-internal: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 8.672123ms
      message: 'load-balancer-api-internal: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 4.388915ms
      message: 'load-balancer-api-internal: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 12.056067ms
      message: 'load-balancer-api-internal: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 5.358103ms
      message: 'load-balancer-api-internal: tcp connection to a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 9.648378ms
      message: 'load-balancer-api-internal: resolved host name a2945c6c2cb7e4ad4a941b9b35a541bd-58a3667fee194860.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:14:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-network-check-target-ip-10-0-129-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "71438"
    uid: ccf42089-0e54-464d-82a7-aff63b56ea75
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:37:23Z"
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.040271ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:19:23Z"
    - latency: 1.165361ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 1.042301ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 1.00636ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 972.782µs
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 903.511µs
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 1.866268ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:13:23Z"
    - latency: 1.573636ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:12:23Z"
    - latency: 1.56797ms
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:11:23Z"
    - latency: 992.125µs
      message: 'network-check-target-ip-10-0-129-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:10:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-network-check-target-ip-10-0-131-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "71439"
    uid: 81b8bbaf-d960-46d5-b399-aa26c56f7a1b
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:37:23Z"
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.057215ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:19:23Z"
    - latency: 2.399612ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 2.405787ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 2.335793ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 2.405835ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 2.397131ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 2.528279ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:13:23Z"
    - latency: 2.669479ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:12:23Z"
    - latency: 2.666531ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:11:23Z"
    - latency: 2.126801ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:10:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-network-check-target-ip-10-0-133-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "71440"
    uid: 7a011dfd-e5b7-4355-af53-825eb16ba390
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:37:23Z"
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.218788ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:19:23Z"
    - latency: 2.361495ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 2.465041ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 2.381621ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 2.480899ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 2.092988ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 2.621695ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:13:23Z"
    - latency: 2.861348ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:12:23Z"
    - latency: 2.729076ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:11:23Z"
    - latency: 2.826197ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:10:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T06:30:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-223.ec2.internal
      uid: 23fb2d01-9092-42b2-b623-b81f171db30a
    resourceVersion: "70338"
    uid: dd20b34f-28c9-4841-8ba2-493f1b84e8aa
  spec:
    sourcePod: network-check-source-7d88cb55d8-ghwrd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T06:36:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.234899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 1.99271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:18:23Z"
    - latency: 1.082967ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 2.435923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:17:23Z"
    - latency: 947.535µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 1.650425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:16:23Z"
    - latency: 1.024294ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 2.263452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:15:23Z"
    - latency: 1.15342ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T07:14:23Z"
    - latency: 1.920816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T07:14:23Z"
kind: List
metadata:
  resourceVersion: ""