apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32527"
    uid: 424ff67c-ea17-465c-9b62-a45204bcd0bf
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:32:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.759µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 1.143026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 814.543µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 1.282698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 873.661µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 1.187852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:36Z"
    - latency: 1.038572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:01:36Z"
    - latency: 1.055036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:36Z"
    - latency: 818.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:36Z"
    - latency: 1.089248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32528"
    uid: 4d8d960d-2250-4a90-aa68-90700b9fcbc8
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:31:36Z"
      message: 'load-balancer-api-external: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.54839ms
      message: 'load-balancer-api-external: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 9.562766ms
      message: 'load-balancer-api-external: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 7.416391ms
      message: 'load-balancer-api-external: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 9.506829ms
      message: 'load-balancer-api-external: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 5.509146ms
      message: 'load-balancer-api-external: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 8.396867ms
      message: 'load-balancer-api-external: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 5.088403ms
      message: 'load-balancer-api-external: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 8.122356ms
      message: 'load-balancer-api-external: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 4.258435ms
      message: 'load-balancer-api-external: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 7.117495ms
      message: 'load-balancer-api-external: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32529"
    uid: 613cf359-232e-446d-a1d5-6a5d138dea84
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:31:36Z"
      message: 'load-balancer-api-internal: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.534094ms
      message: 'load-balancer-api-internal: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 9.519216ms
      message: 'load-balancer-api-internal: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 7.40209ms
      message: 'load-balancer-api-internal: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 9.580155ms
      message: 'load-balancer-api-internal: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 6.551309ms
      message: 'load-balancer-api-internal: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 8.345102ms
      message: 'load-balancer-api-internal: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 5.120759ms
      message: 'load-balancer-api-internal: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 8.068173ms
      message: 'load-balancer-api-internal: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 5.88739ms
      message: 'load-balancer-api-internal: tcp connection to a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 7.041861ms
      message: 'load-balancer-api-internal: resolved host name a0b71b06eb95047bf95482b13869fe42-e976390f587f183b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-ip-10-0-139-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32523"
    uid: 9d1f19ad-2afb-4afe-b96f-f6f5704544b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:32:36Z"
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.332734ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 734.517µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 796.839µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 833.551µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 1.579191ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 1.031936ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:36Z"
    - latency: 820.758µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:01:36Z"
    - latency: 870.59µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:36Z"
    - latency: 741.328µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:36Z"
    - latency: 803.113µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-ip-10-0-140-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32525"
    uid: ae40540f-0292-475b-819b-803ae43088f0
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:32:36Z"
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.783651ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 2.389008ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 2.283139ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 2.039168ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 1.779234ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 2.210605ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:36Z"
    - latency: 2.275324ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:01:36Z"
    - latency: 2.334892ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:36Z"
    - latency: 2.24456ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:36Z"
    - latency: 2.403095ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-ip-10-0-140-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32524"
    uid: 3fdf980a-9ba8-4f27-9294-28576af684ef
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:32:36Z"
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.22004ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 2.044408ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 1.926945ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 2.020947ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 2.280333ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 1.829635ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:36Z"
    - latency: 2.118226ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:01:36Z"
    - latency: 1.94929ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:36Z"
    - latency: 1.909184ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:36Z"
    - latency: 1.749804ms
      message: 'network-check-target-ip-10-0-140-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:25:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.ec2.internal
      uid: 281ba227-f130-4372-a68e-c13befc71046
    resourceVersion: "32526"
    uid: 5dd43e9f-f041-4ce9-9471-a714aaaaabae
  spec:
    sourcePod: network-check-source-7d88cb55d8-457ph
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:31:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 841.013µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 2.408744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:07:36Z"
    - latency: 1.070492ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 1.752016ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:06:36Z"
    - latency: 731.772µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 1.573517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:05:36Z"
    - latency: 933.296µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 1.655005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:04:36Z"
    - latency: 834.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:36Z"
    - latency: 2.052327ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:03:36Z"
kind: List
metadata:
  resourceVersion: ""