apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "55369"
    uid: 358dae5f-0573-4bb2-984f-b4b0cc270534
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:08:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.146µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 923.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 1.222766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 1.223532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:26:51Z"
    - latency: 1.300253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:25:51Z"
    - latency: 1.26083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:24:51Z"
    - latency: 1.137773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:23:51Z"
    - latency: 877.504µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:22:51Z"
    - latency: 969.717µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:21:51Z"
    - latency: 1.476221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "56842"
    uid: b8b33e0b-73ad-4d2f-8cc6-28dbeb80b89f
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:07:51Z"
      message: 'load-balancer-api-external: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.063582ms
      message: 'load-balancer-api-external: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:51Z"
    - latency: 7.093541ms
      message: 'load-balancer-api-external: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:31:51Z"
    - latency: 3.926857ms
      message: 'load-balancer-api-external: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:51Z"
    - latency: 7.566375ms
      message: 'load-balancer-api-external: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:30:51Z"
    - latency: 4.11669ms
      message: 'load-balancer-api-external: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 7.069158ms
      message: 'load-balancer-api-external: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 4.837411ms
      message: 'load-balancer-api-external: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 6.396028ms
      message: 'load-balancer-api-external: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 4.005801ms
      message: 'load-balancer-api-external: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 6.728361ms
      message: 'load-balancer-api-external: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "56843"
    uid: 77937ae3-c38c-4063-8653-3bb476a0cf04
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:07:51Z"
      message: 'load-balancer-api-internal: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.040734ms
      message: 'load-balancer-api-internal: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:51Z"
    - latency: 7.040861ms
      message: 'load-balancer-api-internal: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:31:51Z"
    - latency: 3.932224ms
      message: 'load-balancer-api-internal: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:51Z"
    - latency: 7.503905ms
      message: 'load-balancer-api-internal: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:30:51Z"
    - latency: 4.123738ms
      message: 'load-balancer-api-internal: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 6.984071ms
      message: 'load-balancer-api-internal: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 4.780295ms
      message: 'load-balancer-api-internal: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 6.429807ms
      message: 'load-balancer-api-internal: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 4.015846ms
      message: 'load-balancer-api-internal: tcp connection to a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 6.716351ms
      message: 'load-balancer-api-internal: resolved host name a8add7f4ad03b46ba8fc22f7c41092f7-107b4ead090cdec9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-129-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "55368"
    uid: 424b6b8b-129c-4b30-a964-c41a7af1cc74
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:08:51Z"
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.323094ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 2.260915ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 2.297522ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 3.17821ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:26:51Z"
    - latency: 2.212766ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:25:51Z"
    - latency: 2.247744ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:24:51Z"
    - latency: 2.480069ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:23:51Z"
    - latency: 2.142331ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:22:51Z"
    - latency: 2.349529ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:21:51Z"
    - latency: 2.26969ms
      message: 'network-check-target-ip-10-0-129-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-135-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "55366"
    uid: b1ab16c0-f069-48b2-bdf6-3d7e575aa76d
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:08:51Z"
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.286379ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 1.152409ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 1.529219ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 937.811µs
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:26:51Z"
    - latency: 965.4µs
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:25:51Z"
    - latency: 926.033µs
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:24:51Z"
    - latency: 1.453264ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:23:51Z"
    - latency: 1.246629ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:22:51Z"
    - latency: 1.223801ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:21:51Z"
    - latency: 878.869µs
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-142-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "55367"
    uid: b6b0352f-173c-4886-862e-7e1b8e7d5242
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:08:51Z"
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.836797ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 2.030661ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 2.154634ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 2.09677ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:26:51Z"
    - latency: 1.677292ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:25:51Z"
    - latency: 2.162082ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:24:51Z"
    - latency: 2.527015ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:23:51Z"
    - latency: 2.037218ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:22:51Z"
    - latency: 1.795456ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:21:51Z"
    - latency: 1.8318ms
      message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:20:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:01:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-32-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-32.ec2.internal
      uid: acedadbf-d149-42c4-b0ad-5904102e9a65
    resourceVersion: "56841"
    uid: 2cf5491c-fd69-47ef-8252-34c2a4109caf
  spec:
    sourcePod: network-check-source-685456655f-5zkxr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:07:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.619µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:51Z"
    - latency: 1.990254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:31:51Z"
    - latency: 1.127844ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:51Z"
    - latency: 1.836408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:30:51Z"
    - latency: 933.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 1.681464ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:29:51Z"
    - latency: 934.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 1.928984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:28:51Z"
    - latency: 889.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:27:51Z"
    - latency: 1.755304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:27:51Z"
kind: List
metadata:
  resourceVersion: ""