apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "75961"
    uid: ef244e35-294d-454f-afb9-ab3e9a7026fe
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:50:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.815µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:32Z"
    - latency: 987.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:32Z"
    - latency: 1.818328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:32Z"
    - latency: 1.122084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 1.109827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 996.022µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 1.116954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 1.88373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 859.812µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:32Z"
    - latency: 1.120749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "72642"
    uid: 4ec57814-0434-4a9a-b5fd-19ca7dbb6e38
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:32Z"
      message: 'load-balancer-api-external: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.034778ms
      message: 'load-balancer-api-external: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 7.000816ms
      message: 'load-balancer-api-external: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 5.311793ms
      message: 'load-balancer-api-external: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 7.575605ms
      message: 'load-balancer-api-external: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 4.853971ms
      message: 'load-balancer-api-external: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 8.204507ms
      message: 'load-balancer-api-external: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 5.692039ms
      message: 'load-balancer-api-external: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 7.642794ms
      message: 'load-balancer-api-external: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 4.497958ms
      message: 'load-balancer-api-external: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 9.044209ms
      message: 'load-balancer-api-external: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:39:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "72643"
    uid: 526ac3dc-2dce-4f2e-bb2b-9b86e9b3a660
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:32Z"
      message: 'load-balancer-api-internal: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.178692ms
      message: 'load-balancer-api-internal: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 7.023899ms
      message: 'load-balancer-api-internal: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 5.267947ms
      message: 'load-balancer-api-internal: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 7.614688ms
      message: 'load-balancer-api-internal: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 4.812348ms
      message: 'load-balancer-api-internal: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 8.140422ms
      message: 'load-balancer-api-internal: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 5.69864ms
      message: 'load-balancer-api-internal: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 7.628962ms
      message: 'load-balancer-api-internal: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 4.018424ms
      message: 'load-balancer-api-internal: tcp connection to add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 9.066644ms
      message: 'load-balancer-api-internal: resolved host name add0aa5cf92b34fa9a90e777b0b1986a-212dac4c885d95fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:39:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-network-check-target-ip-10-0-129-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "75960"
    uid: 1e1fb46a-0851-4332-b502-a2115ae3c3f8
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:50:32Z"
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400075ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:32Z"
    - latency: 2.265267ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:32Z"
    - latency: 2.438827ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:32Z"
    - latency: 2.258357ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 2.079047ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 2.332689ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 2.345993ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 2.701602ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 2.811144ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:32Z"
    - latency: 2.333047ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-network-check-target-ip-10-0-135-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "75959"
    uid: 2916a98e-da5b-417d-9469-21efebd2f8cf
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:50:32Z"
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.519917ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:32Z"
    - latency: 918.891µs
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:32Z"
    - latency: 728.914µs
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:32Z"
    - latency: 1.336429ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 1.425594ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 965.683µs
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 1.094006ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 905.562µs
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 941.397µs
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:32Z"
    - latency: 917.128µs
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-network-check-target-ip-10-0-139-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "75958"
    uid: d4100e75-6aac-4dc9-b5fc-f2196cf2681e
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:50:32Z"
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.904168ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:32Z"
    - latency: 1.944382ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:32Z"
    - latency: 2.026456ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:32Z"
    - latency: 1.817703ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 1.876995ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 1.975684ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 2.020823ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 1.966156ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 2.096146ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:32Z"
    - latency: 2.028363ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:43:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-243-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-243.ec2.internal
      uid: d171228b-9bd7-48c6-b5b9-3d322a381222
    resourceVersion: "72641"
    uid: 9202ab50-0e44-4677-9252-789c4225759a
  spec:
    sourcePod: network-check-source-6f8b768455-4wj5s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.017µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 1.614261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:43:32Z"
    - latency: 1.184258ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 1.939501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:42:32Z"
    - latency: 925.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 1.76813ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:41:32Z"
    - latency: 1.025343ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 1.860785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:40:32Z"
    - latency: 974.61µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:32Z"
    - latency: 2.707037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:39:32Z"
kind: List
metadata:
  resourceVersion: ""