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

            stk.pop();
            stk.pop();
        });
        root.map(Activation::getOs).ifPresent(oa -> {
            stk.push(new ActivationFrame("os", Optional.of(oa)));
            stk.push(new ActivationFrame("arch", Optional.empty()));
            validator.accept(oa.getArch());
            stk.peek().location = "family";
            validator.accept(oa.getFamily());
            stk.peek().location = "name";

  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]

- kubeadm: Control plane images (etcd, kube-apiserver, kube-proxy, etc.) no longer use arch suffixes. Arch suffixes are kept for kube-dns only. ([#66960](https://github.com/kubernetes/kubernetes/pull/66960),
[@rosti](https://github.com/rosti)) Courtesy of SIG Cluster Lifecycle, SIG Release, and SIG Testing

  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}` ([#94552](https://github.com/kubernetes/kubernetes/pull/94552), [@justaugustus](https://github.com/justaugustus)) [SIG Release]

            <li>Property check: {@code ${my.property} != 'some-value'}</li>
            <li>Regex matching: {@code matches(${os.version}, '.*aws')}</li>
            <li>Complex condition: {@code ${os.name} == 'windows' && ${os.arch} != 'amd64' && inrange(${os.version}, '[10,)')}</li>
            <li>String length check: {@code length(${user.name}) > 5}</li>
            <li>Substring with version: {@code substring(${java.version}, 0, 3) == '1.8'}</li>

synchronized class Os { private static final String OS_NAME; private static final String OS_ARCH; private static final String OS_VERSION; private static final String PATH_SEP; private String family; private String name; private String version; private String arch; public void Os(); public void Os(String); public void setFamily(String); public void setName(String); public void setArch(String); public void setVersion(String); public boolean eval() throws Exception; public static boolean isFamily(String); public...

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

- The deprecated mondo `kubernetes-test` tarball is no longer built. Users running Kubernetes e2e tests should use the `kubernetes-test-portable` and `kubernetes-test-{OS}-{ARCH}` tarballs instead. ([#83093](https://github.com/kubernetes/kubernetes/pull/83093), [@ixdy](https://github.com/ixdy))

### Scheduling