that they span multiple clusters. Creating a Federated HPA targeting
multiple clusters ensures that cluster-level autoscalers are
consistently deployed across those clusters, and dynamically managed
to ensure that autoscaling can occur optimially in all clusters,
within a set of global constraints on the total number of replicas
permitted across all clusters.  If replicas are not

 * Enumeration of SMB Witness Service types as defined in MS-SWN specification.
 * These types represent different categories of witness services available in
 * clustered file server environments.
 */
public enum WitnessServiceType {
    /**
     * Cluster-aware witness service for general cluster resources
     */
    CLUSTER_WITNESS,

    /**
     * Individual file server witness for standalone servers
     */
    FILE_SERVER_WITNESS,

- Update read/write operations for RDMA

---

### Phase 6: Witness Protocol
**Priority: LOW** | **Estimated Effort: 4-5 weeks**

Witness protocol enables rapid failover notification for clustered file servers.

#### 6.1 Core Witness Infrastructure
```
Package: jcifs.internal.witness
├── WitnessClient.java           - Witness client implementation

- The kube-apiserver exposes four new metrics to inform about errors on the clusterIP and nodePort allocation logic ([#120843](https://github.com/kubernetes/kubernetes/pull/120843),...

with a service account may only reference secrets specified in the service account's secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers.

**Note**: This only impacts the cluster if the ServiceAccount admission plugin is used (most cluster should have this on by default as recommended in https://kubernetes.io/docs/reference/access-authn-authz/ad...

  Please see [the KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1710-selinux-relabeling#story-3-cluster-upgrade) how we expect to warn users before any SELinux behavior changes and how they can opt-out before. Note that this field and feature gate is useful only with clusters that run with SELinux enabled. No action is required on clusters without SELinux. ([#127981](https://github.com/kubernetes/kubernetes/pull/127981), [@jsafrane](https://github.com/jsafrane)) [SIG...

    .setSize(10)
    .execute()
    .getResponse();
```

## Troubleshooting

### Common Issues

**Index Creation Fails**
- Verify OpenSearch cluster is accessible
- Check index permissions and mappings
- Ensure sufficient cluster resources

**Suggestions Not Appearing**
- Confirm documents are indexed: `suggester.refresh()`
- Check query formatting and filters
- Verify analyzer configurations

## 1. Overview

The SMB Witness Protocol enables rapid notification of resource changes in a clustered file server environment. It provides fast failover capabilities by allowing clients to register for notifications about server node availability, share movement, and other critical cluster events.

## 2. Protocol Specification Reference

- **MS-SWN**: Service Witness Protocol Specification

- In "large" clusters, kube-proxy in iptables mode will now sometimes
  leave unused rules in iptables for a while (up to `--iptables-sync-period`)
  before deleting them. This improves performance by not requiring it to
  check for stale rules on every sync. (In smaller clusters, it will still

- `etcd: Update etcd to `v3.6.6`. (#135271, @bzsuni) [SIG API Machinery, Cloud Provider, Cluster Lifecycle, Etcd and Testing]