build:macos_arm64 --cpu=darwin_arm64
build:macos_arm64 --macos_minimum_os=11.0
build:macos_arm64 --config=clang_local
build:macos_arm64 --platforms=@build_bazel_apple_support//configs/platforms:darwin_arm64

# iOS configs for each architecture and the fat binary builds.
build:ios --apple_platform_type=ios
build:ios --copt=-fembed-bitcode
build:ios --copt=-Wno-c++11-narrowing
build:ios --config=clang_local
build:ios --config=apple-toolchain

### Container Images

All container images are available as manifest lists and support the described
architectures. It is also possible to pull a specific architecture directly by
adding the "-$ARCH" suffix  to the container image name.

name | architectures
---- | -------------

### Container Images

All container images are available as manifest lists and support the described
architectures. It is also possible to pull a specific architecture directly by
adding the "-$ARCH" suffix  to the container image name.

name | architectures
---- | -------------

          </description>
        </field>
        <field>
          <name>arch</name>
          <version>1.0.0+</version>
          <type>String</type>
          <description>
            The architecture of the OS to be used to activate a profile.
          </description>
        </field>
        <field>
          <name>version</name>
          <version>1.0.0+</version>
          <type>String</type>

command to run a standalone MinIO server on Linux hosts running 64-bit Intel/AMD architectures. Replace ``/data`` with the path to the drive or directory in which you want MinIO to store data. ```sh wget https://dl.min.io/server/minio/release/linux-amd64/minio chmod +x minio ./minio server /data ``` The following table lists supported architectures. Replace the `wget` URL with the architecture for your Linux host. | Architecture | URL | | -------- | ------ | | 64-bit Intel/AMD | <https://dl.min.io/serv...

- **MS-SMB2 Section 3.1.5.3**: Receiving an SMB_COM_NEGOTIATE
- **MS-SMB2 Section 3.2.4.1.6**: Alternative Channel Creation
- **MS-SMB2 Section 3.3.5.15.12**: Channel Binding

## 3. Multi-Channel Architecture

### 3.1 Channel States
```java
public enum ChannelState {
    DISCONNECTED(0),     // Not connected
    CONNECTING(1),       // Connection in progress
    AUTHENTICATING(2),   // Authentication in progress

   * same order. (It is guaranteed to return true for instances constructed from the same values in
   * the same order if {@code strictfp} is in effect, or if the system architecture guarantees
   * {@code strictfp}-like semantics.)
   */
  @Override
  public boolean equals(@Nullable Object obj) {
    if (obj == null) {
      return false;
    }

- **MS-SMB2 Section 3.2.4.24**: FSCTL_SRV_REQUEST_RESUME_KEY
- **MS-SMB2 Section 3.3.5.15.12**: Cluster Reconnect
- **MS-RRP**: Windows Remote Registry Protocol (for witness service discovery)

## 3. Witness Architecture

### 3.1 Witness Service Types
```java
public enum WitnessServiceType {
    CLUSTER_WITNESS,     // Cluster-aware witness service
    FILE_SERVER_WITNESS, // Individual file server witness

([#87077](https://github.com/kubernetes/kubernetes/pull/87077), [@soltysh](https://github.com/soltysh)) [SIG Architecture, CLI and Testing]
- The deprecated command `kubectl rolling-update` has been removed ([#88057](https://github.com/kubernetes/kubernetes/pull/88057), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG Architecture, CLI and Testing]

#### client-go:

  controller-manager, and scheduler server components, we no longer
  reference the individual architectures in the image names, specifically
  in the 'FROM' directive of the server image Dockerfiles.
  
  As a result, server images for non-amd64 images copy in the go-runner
  amd64 binary instead of the go-runner that matches that architecture.
  
  This commit explicitly sets the '--platform=linux/${arch}' to ensure