Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify target type in create target group #3269

Closed
wants to merge 8 commits into from
2 changes: 1 addition & 1 deletion pkg/machinery/go.mod
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ require (
golang.org/x/net v0.0.0-20210226172049-e18ecbb05110 // indirect
golang.org/x/text v0.3.5 // indirect
google.golang.org/genproto v0.0.0-20210302174412-5ede27ff9881
google.golang.org/grpc v1.36.0
google.golang.org/grpc v1.36.1
google.golang.org/protobuf v1.26.0
gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c // indirect
gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b
Expand Down
4 changes: 2 additions & 2 deletions pkg/machinery/go.sum
Original file line number Diff line number Diff line change
Expand Up @@ -178,8 +178,8 @@ google.golang.org/grpc v1.19.0/go.mod h1:mqu4LbDTu4XGKhr4mRzUsmM4RtVoemTSY81AxZi
google.golang.org/grpc v1.23.0/go.mod h1:Y5yQAOtifL1yxbo5wqy6BxZv8vAUGQwXBOALyacEbxg=
google.golang.org/grpc v1.25.1/go.mod h1:c3i+UQWmh7LiEpx4sFZnkU36qjEYZ0imhYfXVyQciAY=
google.golang.org/grpc v1.27.0/go.mod h1:qbnxyOmOxrQa7FizSgH+ReBfzJrCY1pSN7KXBS8abTk=
google.golang.org/grpc v1.36.0 h1:o1bcQ6imQMIOpdrO3SWf2z5RV72WbDwdXuK0MDlc8As=
google.golang.org/grpc v1.36.0/go.mod h1:qjiiYl8FncCW8feJPdyg3v6XW24KsRHe+dy9BAGRRjU=
google.golang.org/grpc v1.36.1 h1:cmUfbeGKnz9+2DD/UYsMQXeqbHZqZDs4eQwW0sFOpBY=
google.golang.org/grpc v1.36.1/go.mod h1:qjiiYl8FncCW8feJPdyg3v6XW24KsRHe+dy9BAGRRjU=
google.golang.org/protobuf v0.0.0-20200109180630-ec00e32a8dfd/go.mod h1:DFci5gLYBciE7Vtevhsrf46CRTquxDuWsQurQQe4oz8=
google.golang.org/protobuf v0.0.0-20200221191635-4d8936d0db64/go.mod h1:kwYJMbMJ01Woi6D6+Kah6886xMZcty6N08ah7+eCXa0=
google.golang.org/protobuf v0.0.0-20200228230310-ab0ca4ff8a60/go.mod h1:cfTl7dwQJ+fmap5saPgwCLgHXTUD7jkjRqWcaiX5VyM=
Expand Down
3 changes: 2 additions & 1 deletion website/content/docs/v0.9/Cloud Platforms/aws.md
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,8 @@ aws elbv2 create-target-group \
--name talos-aws-tutorial-tg \
--protocol TCP \
--port 6443 \
--vpc-id $VPC
--vpc-id $VPC \
--target-type ip
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this got already fixed in some other PR

```

Now, using the target group's ARN, and the **PrivateIpAddress** from the instances that you created :
Expand Down
32 changes: 16 additions & 16 deletions website/content/docs/v0.9/Introduction/what-is-new.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,38 +5,38 @@ weight: 5

## Control Plane as Static Pods

Talos now runs Kubernetes control plane as static pods managed via machine configuration.
This change makes bootstrap process much more stable and resilient to failures.
For single control plane node clusters it eliminates bugs with control plane being unavailable after a reboot.
As control plane configuration is managed via Talos API, even if control plane configuration was wrong and
API server is not available, change can be rolled back using `talosctl` to bring the control plane back up.
Talos now runs the Kubernetes control plane as static pods managed via machine configuration.
This change makes the bootstrap process much more stable and resilient to failures.
For single control plane node clusters it eliminates bugs with the control plane being unavailable after a reboot.
As the control plane configuration is managed via the Talos API, even if the control plane configuration was wrong and
the API server is not available, the change can be rolled back using `talosctl` to bring the control plane back up.
When upgrading from Talos 0.8, control plane can be [converted](../../guides/converting-control-plane/) to run as static pods.

## ECDSA Certificates and Keys for Kubernetes

Talos now generates uses ECDSA keys for Kubernetes and etcd PKI.
ECDSA keys are much smaller and all PKI operations are much faster (for example, generating certificate from the CA) which
ECDSA keys are much smaller than RSA keys and all PKI operations are much faster (for example, generating a certificate from the CA) which
leads to much faster bootstrap and boot times.

## Immediate Machine Configuration Updates

Changes to `.cluster` part of Talos machine configuration can now be [applied immediately](../../guides/editing-machine-configuration) (without a reboot).
This allows for example updating versions of control plane components, adding additional arguments or modifying bootstrap manifests.
Future versions of Talos will expand on that to allow most of the machine configuration to be applied without a reboot.
Changes to the `.cluster` part of Talos machine configuration can now be [applied immediately](../../guides/editing-machine-configuration) (without a reboot).
This allows, for example, updating versions of control plane components, adding additional arguments or modifying bootstrap manifests.
Future versions of Talos will expand on this to allow most of the machine configuration to be applied without a reboot.

## Disk Encryption

Talos now supports encryption for `STATE` and `EPHEMERAL` partitions of the system disk.
`STATE` partition holds machine configuration and `EPHEMERAL` partition is mounted as `/var` which stores container runtime
state, configuration files laid on top of Talos read-only immutable root filesystem.
Encryption key in Talos 0.9 is derived from the Node UUID which is unique machine identifier provided by the manufacturer.
Disk encryption is not enabled by default, it needs to be [enabled](../../guides/disk-encryption/) via machine configuration.
The `STATE` partition holds machine configuration and the `EPHEMERAL` partition is mounted as `/var` which stores container runtime
state, and configuration files laid on top of Talos read-only immutable root filesystem.
The encryption key in Talos 0.9 is derived from the Node UUID which is a unique machine identifier provided by the manufacturer.
Disk encryption is not enabled by default: it needs to be [enabled](../../guides/disk-encryption/) via machine configuration.

## Virtual IP for the Control Plane Endpoint

Talos adds support for Virtual L2 [shared IP](../../guides/vip/) for the control plane: control plane nodes make sure only one of the nodes
adverties shared IP via ARP.
If one of the control plane nodes goes down, another node takes over shared IP.
Talos adds support for Virtual L2 [shared IP](../../guides/vip/) for the control plane: control plane nodes ensure only one of the nodes
advertise the shared IP via ARP.
If one of the control plane nodes goes down, another node takes over the shared IP.

## Updated Components

Expand Down