apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31743"
    uid: a56e027a-0914-4cd4-bb3a-b0d94f8cf178
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.558µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 1.00108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 786.359µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 921.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 893.789µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 1.350172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:13:03Z"
    - latency: 1.352297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:12:03Z"
    - latency: 866.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:11:03Z"
    - latency: 945.045µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:10:03Z"
    - latency: 1.274555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31744"
    uid: f46d313a-8ed9-4971-8239-9d6a6bd8342f
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:42:03Z"
      message: 'load-balancer-api-external: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.509997ms
      message: 'load-balancer-api-external: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 8.57894ms
      message: 'load-balancer-api-external: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 5.005751ms
      message: 'load-balancer-api-external: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 8.360309ms
      message: 'load-balancer-api-external: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 4.801333ms
      message: 'load-balancer-api-external: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 8.287448ms
      message: 'load-balancer-api-external: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 5.701216ms
      message: 'load-balancer-api-external: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 10.87646ms
      message: 'load-balancer-api-external: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 4.841984ms
      message: 'load-balancer-api-external: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 11.656206ms
      message: 'load-balancer-api-external: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:14:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31745"
    uid: aaa65aa6-c40d-4430-8264-7f351b1c8e9c
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:42:03Z"
      message: 'load-balancer-api-internal: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.510535ms
      message: 'load-balancer-api-internal: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 8.546309ms
      message: 'load-balancer-api-internal: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 5.16367ms
      message: 'load-balancer-api-internal: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 8.321367ms
      message: 'load-balancer-api-internal: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 5.67352ms
      message: 'load-balancer-api-internal: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 8.260844ms
      message: 'load-balancer-api-internal: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 5.687091ms
      message: 'load-balancer-api-internal: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 10.822596ms
      message: 'load-balancer-api-internal: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 4.835832ms
      message: 'load-balancer-api-internal: tcp connection to a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 11.617959ms
      message: 'load-balancer-api-internal: resolved host name a0a396a026e6c46199c4929f3c2430f5-079001cec371f26a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:14:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-network-check-target-ip-10-0-128-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31740"
    uid: e93e8fb5-41c7-48f0-bd09-8e315d1541c8
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:03Z"
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.287796ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 2.317378ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 2.278519ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 2.230052ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 2.338651ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 2.322923ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:13:03Z"
    - latency: 2.383638ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:12:03Z"
    - latency: 2.394767ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:11:03Z"
    - latency: 2.2337ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:10:03Z"
    - latency: 2.069216ms
      message: 'network-check-target-ip-10-0-128-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-network-check-target-ip-10-0-132-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31739"
    uid: d54656cd-a8c6-48c0-b1f0-7cb38881197f
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:03Z"
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.1µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 885.896µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 754.802µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 771.076µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 829.695µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 720.389µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:13:03Z"
    - latency: 902.877µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:12:03Z"
    - latency: 823.72µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:11:03Z"
    - latency: 792.187µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:10:03Z"
    - latency: 752.04µs
      message: 'network-check-target-ip-10-0-132-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-network-check-target-ip-10-0-138-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31741"
    uid: db640569-5ebe-4788-b973-ed3b389b6a1e
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:03Z"
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382797ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 2.384123ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 2.078235ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 2.016005ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 2.34305ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 2.274977ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:13:03Z"
    - latency: 2.915605ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:12:03Z"
    - latency: 2.471924ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:11:03Z"
    - latency: 2.36377ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:10:03Z"
    - latency: 2.302618ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:36:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-182.ec2.internal
      uid: 42311df0-2220-4969-ba83-29d322a043ac
    resourceVersion: "31742"
    uid: e9362c9c-81f8-4ef2-bfb5-53d7407c5b33
  spec:
    sourcePod: network-check-source-989f8b8dc-9lf9x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:42:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.259372ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 1.830763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:18:03Z"
    - latency: 1.135315ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 1.901156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:17:03Z"
    - latency: 897.265µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 1.762999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:16:03Z"
    - latency: 746.941µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 1.627551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:15:03Z"
    - latency: 923.731µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:14:03Z"
    - latency: 1.70011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:14:03Z"
kind: List
metadata:
  resourceVersion: ""