Releases: linode/linode-api-docs
v4.108.0
Updated
- Support Ticket Open (POST /support/tickets):
- New support tickets can now reference relevant Kubernetes clusters with the new
lkecluster_id
request body property.
- New support tickets can now reference relevant Kubernetes clusters with the new
v4.107.0
Updated
-
Linode Create (POST /linode/instances):
- Description and
interfaces
properties updated with additional VLANs information and restrictions.
- Description and
-
IP Address RDNS Update (PUT /networking/ips/{address}):
- Description updated to reflect new default RDNS value.
Fixed
-
VLANs List (GET /networking/vlans):
- Public server removed. This endpoint is currently only accessible from
https://api.linode.com/v4beta
.
- Public server removed. This endpoint is currently only accessible from
-
Firewall Rules Update (PUT /networking/firewalls/{firewallId}/rules):
- Shell and CLI example commands corrected.
- Required properties designated.
-
Kubernetes Cluster Create (POST /lke/clusters):
- Shell example corrected.
v4.106.1
v4.106.0
v4.105.1
v4.105.0
Updated
-
Kernel build dates are now accessible via the
built
value at the following endpoints:- Kernels List (GET /linode/kernels)
- Kernel View (GET /linode/kernels/{kernelId})
-
Block Storage Volume hardware type (HDD or NVME) is now accessible via the
hardware_type
value at the following endpoints:- Volumes List (GET /volumes)
- Volume View (GET /volumes/{volumeId})
Fixed
-
A bug has been fixed by requiring a Volume
active
status for the following endpoints:- Volume Clone (POST /volumes/{volumeId}/clone)
- Volume Resize (POST /volumes/{volumeId}/resize)
-
The following endpoints now return an
updated
value in their responses for public distribution Images:- Images List (GET /images)
- Image View (GET /images/{imageId})
-
Users must now have
read_write
Grants for anydevices
included in requests when accessing the Firewall Create (POST /networking/firewalls) endpoint.
v4.104.0
Added
- Specify a Payment Method when accessing the Payment Make (POST /account/payments) endpoint by utilizing the new
payment_method_id
property.
Fixed
-
Previously, the specification erroneously stated that
google_pay
type Payment Methods could be added with the Payment Method Add (POST /account/payment-methods) endpoint. At this time, non-credit_card
type Payment Methods can only be added using Linode Cloud Manager. Thegoogle_pay
type has been removed from the endpoint's Request Body Schema accordingly. -
A bug was fixed that uploaded the SSH keys of deleted Users that were included in the
authorized_users
array when accessing the following endpoints:- Linode Create (POST /linode/instances)
- Disk Create (POST /linode/instances/{linodeId}/disks)
v4.102.0
Added
-
NodeBalancers that are assigned to an individual Linode can be quickly viewed by accessing the Linode NodeBalanacers View (GET /linode/instances/{linodeId}/nodebalancers) endpoint.
-
Kubeconfig files for an LKE Cluster can be deleted and regenerated by accessing the Kubeconfig Delete (DELETE /lke/clusters/{clusterId}/kubeconfig) endpoint.
Changed
-
Cloud Firewalls are now available in every data center Region! Accordingly, limited availability language has been removed from all Cloud Firewall endpoint descriptions in the specification.
-
You can now add up to 6 active Payment Methods when accessing the Payment Method Add (POST /account/payment-methods) endpoint. Previously, only one
credit_card
type and onegoogle_pay
type Payment Method was allowed.
Fixed
- Previously, Restricted Users did not have access to the Cloud Firewalls they created. Now, when a Restricted User creates a Cloud Firewall, that user has read/write access to that Firewall after it is created.
v4.101.1
v4.101.0
Added
-
You can now deactivate Payment Methods by accessing the Payment Method Delete (DELETE /account/payment-methods/{paymentMethodId}) endpoint.
-
Linode APIv4 now supports adding an autoscaler configuration for Node Pools using the Linode Kubernetes Engine (LKE) endpoints listed below. Note: While adding an autoscaler config is supported by the Linode APIv4, issuing requests to these endpoints will not yet take any effect on your Node Pools. The cluster-autoscaler will be available in a subsequent Linode Kubernetes Engine release. Please refer to the LKE Changelog to learn when adding an autoscaler config for Node Pools is released.
- Kubernetes Cluster Create (POST /lke/clusters)
- Node Pool Create (POST /lke/clusters/{clusterId}/pools)
- Node Pool Update (PUT /lke/clusters/{clusterId}/pools/{poolId})