### 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
---- | -------------

- kubelet

### 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
---- | -------------

                org = activationOS.getFamily();
                val = interpolate(org);
                if (org != val) {
                    activationOS.setFamily(val);
                }
                // Arch
                org = activationOS.getArch();
                val = interpolate(org);
                if (org != val) {
                    activationOS.setArch(val);
                }
                // Version

          <description>
            The general family of the OS to be used to activate a profile (e.g. 'windows')
          </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>

### 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
---- | -------------

            });
            a.map(Activation::getOs).ifPresent(oa -> {
                Interpolation nt = new Interpolation(oa, interpolator::interpolate);
                nt.performFor(oa.getArch(), "arch", oa::setArch);
                nt.performFor(oa.getFamily(), "family", oa::setFamily);
                nt.performFor(oa.getName(), "name", oa::setName);
                nt.performFor(oa.getVersion(), "version", oa::setVersion);

  amd64 binary instead of the go-runner that matches that architecture.
  
  This commit explicitly sets the '--platform=linux/${arch}' to ensure
  we're pulling the correct go-runner arch from the manifest list.
  
  Before:
  `FROM ${base_image}`
  
  After:
  `FROM --platform=linux/${arch} ${base_image}` ([#94613](https://github.com/kubernetes/kubernetes/pull/94613), [@justaugustus](https://github.com/justaugustus)) [SIG Release]