apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "61888"
    uid: db64b0f9-7a58-483b-93aa-1f3cb5bdea62
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:19:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.346905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 1.381546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 978.215µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 1.209016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 1.365919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:08Z"
    - latency: 1.236203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:08Z"
    - latency: 1.067654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:08Z"
    - latency: 986.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:08Z"
    - latency: 1.658713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:08Z"
    - latency: 889.701µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "62645"
    uid: 60d5c81f-d050-4897-a4f3-deb3b2909f5d
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:18:08Z"
      message: 'load-balancer-api-external: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.392416ms
      message: 'load-balancer-api-external: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:08Z"
    - latency: 8.741003ms
      message: 'load-balancer-api-external: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:48:08Z"
    - latency: 3.214223ms
      message: 'load-balancer-api-external: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 10.028995ms
      message: 'load-balancer-api-external: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 5.182073ms
      message: 'load-balancer-api-external: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 8.840488ms
      message: 'load-balancer-api-external: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 4.794522ms
      message: 'load-balancer-api-external: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 9.271501ms
      message: 'load-balancer-api-external: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 6.108636ms
      message: 'load-balancer-api-external: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 8.464135ms
      message: 'load-balancer-api-external: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:44:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "62646"
    uid: 99b2afcf-6c22-443d-9044-b0397ae825ab
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:18:08Z"
      message: 'load-balancer-api-internal: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.678017ms
      message: 'load-balancer-api-internal: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:08Z"
    - latency: 8.797504ms
      message: 'load-balancer-api-internal: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:48:08Z"
    - latency: 3.392462ms
      message: 'load-balancer-api-internal: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 10.101066ms
      message: 'load-balancer-api-internal: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 5.102205ms
      message: 'load-balancer-api-internal: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 8.815864ms
      message: 'load-balancer-api-internal: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 4.787829ms
      message: 'load-balancer-api-internal: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 9.205463ms
      message: 'load-balancer-api-internal: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 7.425929ms
      message: 'load-balancer-api-internal: tcp connection to a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 8.364563ms
      message: 'load-balancer-api-internal: resolved host name a98f4251fe0f64b34b549850304536f8-ab3af937a76749df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:44:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-network-check-target-ip-10-0-132-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "61885"
    uid: ab0468b3-c6e4-44f6-b57b-37fbe4c67c96
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:19:08Z"
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.137µs
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 959.227µs
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 966.715µs
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 810.234µs
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 1.030846ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:08Z"
    - latency: 1.273136ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:08Z"
    - latency: 1.020664ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:08Z"
    - latency: 1.425979ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:08Z"
    - latency: 882.774µs
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:08Z"
    - latency: 1.486945ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-network-check-target-ip-10-0-137-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "61887"
    uid: f18008d9-b2b8-43a6-bddb-9dda14b261da
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:19:08Z"
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.133731ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 2.340247ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 2.130408ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 2.235518ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 2.284414ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:08Z"
    - latency: 2.467167ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:08Z"
    - latency: 2.403136ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:08Z"
    - latency: 2.196297ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:08Z"
    - latency: 2.325201ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:08Z"
    - latency: 2.00193ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-network-check-target-ip-10-0-138-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "61886"
    uid: 538bab54-d637-40a2-bc41-9a493fcde589
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:19:08Z"
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.72172ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 1.945397ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 2.004242ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 1.969553ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 2.017154ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:08Z"
    - latency: 2.005389ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:42:08Z"
    - latency: 1.854325ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:41:08Z"
    - latency: 2.353283ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:40:08Z"
    - latency: 1.849768ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:39:08Z"
    - latency: 2.896782ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:38:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:12:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-170-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-170.ec2.internal
      uid: ee0ca3a9-d389-4c02-8c90-e74b43158983
    resourceVersion: "62644"
    uid: 6dca4f85-31d7-44a2-98df-bdfc0e37a5f7
  spec:
    sourcePod: network-check-source-6f8b768455-n8jzw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:18:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.7µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:08Z"
    - latency: 1.885655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:48:08Z"
    - latency: 1.32907ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 1.897453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:47:08Z"
    - latency: 1.115233ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 1.830113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:46:08Z"
    - latency: 863.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 1.982574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:45:08Z"
    - latency: 1.040068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:08Z"
    - latency: 1.697997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:44:08Z"
kind: List
metadata:
  resourceVersion: ""