build(deps): bump github.com/talos-systems/talos/pkg/machinery from 1.1.1 to 1.2.0

[dependabot[bot]]

Bumps github.com/talos-systems/talos/pkg/machinery from 1.1.1 to 1.2.0.

Release notes

Sourced from github.com/talos-systems/talos/pkg/machinery's releases.

v1.2.0

Talos 1.2.0 (2022-09-01)

Welcome to the v1.2.0 release of Talos!

Please try out the release binaries and report any issues at https://github.com/siderolabs/talos/issues.

Talos API access from Kubernetes

Talos now supports access to its API from within Kubernetes. It can be configured in the machine config as below:

machine:
  features:
    kubernetesTalosAPIAccess:
      enabled: true
      allowedRoles:
        - os:reader
      allowedKubernetesNamespaces:
        - kube-system

This feature introduces a new custom resource definition, serviceaccounts.talos.dev. Creating custom resources of this type will provide credentials to access Talos API from within Kubernetes.

The new CLI subcommand talosctl inject serviceaccount can be used to configure Kubernetes manifests with Talos service accounts as below:

talosctl inject serviceaccount -f manifests.yaml > manifests-injected.yaml
kubectl apply -f manifests-injected.yaml

See documentation for more details.

Apply Config Patches

talosctl apply-config now supports patching the machine config file in memory before submitting it to the node.

Etcd Configuration

Configuration setting cluster.etcd.subnet is deprecated, but still supported.

Two new configuration settings are introduce to control precisely which subnet is used for etcd peer communication:

cluster:
</tr></table> 

... (truncated)

Changelog

Sourced from github.com/talos-systems/talos/pkg/machinery's changelog.

Talos 1.2.0-alpha.2 (2022-08-10)

Welcome to the v1.2.0-alpha.2 release of Talos!
This is a pre-release of Talos

Please try out the release binaries and report any issues at https://github.com/siderolabs/talos/issues.

Talos API access from Kubernetes

Talos now supports access to its API from within Kubernetes. It can be configured in the machine config as below:

machine:
  features:
    kubernetesTalosAPIAccess:
      enabled: true
      allowedRoles:
        - os:reader
      allowedKubernetesNamespaces:
        - kube-system

This feature introduces a new custom resource definition, serviceaccounts.talos.dev. Creating custom resources of this type will provide credentials to access Talos API from within Kubernetes.

The new CLI subcommand talosctl inject serviceaccount can be used to configure Kubernetes manifests with Talos service accounts as below:

talosctl inject serviceaccount -f manifests.yaml > manifests-injected.yaml
kubectl apply -f manifests-injected.yaml

See documentation for more details.

Generating Talos secrets from PKI directory

It is now possible to generate a secrets bundle from a Kubernetes PKI directory (e.g. /etc/kubernetes/pki).

You can also specify a bootstrap token to be used in the secrets bundle.

This secrets bundle can then be used to generate a machine config.

This facilitates migrating clusters (e.g. created using kubeadm) to Talos.

talosctl gen secrets --kubernetes-bootstrap-token znzio1.1ifu15frz7jd59pv --from-kubernetes-pki /etc/kubernetes/pki
talosctl gen config --with-secrets secrets.yaml my-cluster https://172.20.0.1:6443
</tr></table> 

... (truncated)

Commits

• c568770 release(v1.2.0): prepare release
• d77c05d chore: update kernel to 5.15.64
• ece66fe fix: properly handle configContext being nil in Talos client
• a3a29ec fix: change the type of returned gRPC connection object from the client
• 6234141 fix: expose Talos client gRPC connection via the function Conn
• 7b0a272 release(v1.2.0-beta.2): prepare release
• e2ad584 test: fix cli reboot test
• d761a20 feat: track progress of action API calls
• 7ee20e8 fix: limit apid backoff max delay
• 80448a2 fix: always abort the maintenance service
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #52.