cloudflare/cloudflared
Publicmirrored from https://github.com/cloudflare/cloudflaredAvailable
CHANGES.md
211lines · modecode
| 1 | **Experimental**: This is a new format for release notes. The format and availability is subject to change. |
| 2 | |
| 3 | ## 2021.10.4 |
| 4 | ### Improvements |
| 5 | - Collect quic transport metrics on RTT, packets and bytes transferred. |
| 6 | |
| 7 | ### Bug Fixes |
| 8 | - Fix race condition that was writing to the connection after the http2 handler returns. |
| 9 | |
| 10 | ## 2021.9.2 |
| 11 | |
| 12 | ### New features |
| 13 | - `cloudflared` can now run with `quic` as the underlying tunnel transport protocol. To try it, change or add "protocol: quic" to your config.yml file or |
| 14 | run cloudflared with the `--protocol quic` flag. e.g: |
| 15 | `cloudflared tunnel --protocol quic run <tunnel-name>` |
| 16 | |
| 17 | ### Bug Fixes |
| 18 | - Fixed some generic transport bugs in `quic` mode. It's advised to upgrade to at least this version (2021.9.2) when running `cloudflared` |
| 19 | with `quic` protocol. |
| 20 | - `cloudflared` docker images will now show version. |
| 21 | |
| 22 | |
| 23 | ## 2021.8.4 |
| 24 | ### Improvements |
| 25 | - Temporary tunnels (those hosted on trycloudflare.com that do not require a Cloudflare login) now run as Named Tunnels |
| 26 | underneath. We recall that these tunnels should not be relied upon for production usage as they come with no guarantee |
| 27 | of uptime. Previous cloudflared versions will soon be unable to run legacy temporary tunnels and will require an update |
| 28 | (to this version or more recent). |
| 29 | |
| 30 | ## 2021.8.2 |
| 31 | ### Improvements |
| 32 | - Because Equinox os shutting down, all cloudflared releases are now present [here](https://github.com/cloudflare/cloudflared/releases). |
| 33 | [Equinox](https://dl.equinox.io/cloudflare/cloudflared/stable) will no longer receive updates. |
| 34 | |
| 35 | ## 2021.8.0 |
| 36 | ### Bug fixes |
| 37 | - Prevents tunnel from accidentally running when only proxy-dns should run. |
| 38 | |
| 39 | ### Improvements |
| 40 | - If auto protocol transport lookup fails, we now default to a transport instead of not connecting. |
| 41 | |
| 42 | ## 2021.6.0 |
| 43 | ### Bug Fixes |
| 44 | - Fixes a http2 transport (the new default for Named Tunnels) to work with unix socket origins. |
| 45 | |
| 46 | |
| 47 | ## 2021.5.10 |
| 48 | ### Bug Fixes |
| 49 | - Fixes a memory leak in h2mux transport that connects cloudflared to Cloudflare edge. |
| 50 | |
| 51 | |
| 52 | ## 2021.5.9 |
| 53 | ### New Features |
| 54 | - Uses new Worker based login helper service to facilitate token exchange in cloudflared flows. |
| 55 | |
| 56 | ### Bug Fixes |
| 57 | - Fixes Centos-7 builds. |
| 58 | |
| 59 | ## 2021.5.8 |
| 60 | ### New Features |
| 61 | - When creating a DNS record to point a hostname at a tunnel, you can now use --overwrite-dns to overwrite any existing |
| 62 | DNS records with that hostname. This works both when using the CLI to provision DNS, as well as when starting an adhoc |
| 63 | named tunnel, e.g.: |
| 64 | - `cloudflared tunnel route dns --overwrite-dns foo-tunnel foo.example.com` |
| 65 | - `cloudflared tunnel --overwrite-dns --name foo-tunnel --hostname foo.example.com` |
| 66 | |
| 67 | ## 2021.5.7 |
| 68 | ### New Features |
| 69 | - Named Tunnels will automatically select the protocol to connect to Cloudflare's edge network. |
| 70 | |
| 71 | ## 2021.5.0 |
| 72 | |
| 73 | ### New Features |
| 74 | - It is now possible to run the same tunnel using more than one `cloudflared` instance. This is a server-side change and |
| 75 | is compatible with any client version that uses Named Tunnels. |
| 76 | |
| 77 | To get started, visit our [developer documentation](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/deploy-cloudflared-replicas). |
| 78 | - `cloudflared tunnel ingress validate` will now warn about unused keys in your config file. This is helpful for |
| 79 | detecting typos in your config. |
| 80 | - If `cloudflared` detects it is running inside a Linux container, it will limit itself to use only the number of CPUs |
| 81 | the pod has been granted, instead of trying to use every CPU available. |
| 82 | |
| 83 | ## 2021.4.0 |
| 84 | |
| 85 | ### Bug Fixes |
| 86 | |
| 87 | - Fixed proxying of websocket requests to avoid possibility of losing initial frames that were sent in the same TCP |
| 88 | packet as response headers [#345](https://github.com/cloudflare/cloudflared/issues/345). |
| 89 | - `proxy-dns` option now works in conjunction with running a named tunnel [#346](https://github.com/cloudflare/cloudflared/issues/346). |
| 90 | |
| 91 | ## 2021.3.6 |
| 92 | |
| 93 | ### Bug Fixes |
| 94 | |
| 95 | - Reverted 2021.3.5 improvement to use HTTP/2 in a best-effort manner between cloudflared and origin services because |
| 96 | it was found to break in some cases. |
| 97 | |
| 98 | ## 2021.3.5 |
| 99 | |
| 100 | ### Improvements |
| 101 | |
| 102 | - HTTP/2 transport is now always chosen if origin server supports it and the service url scheme is HTTPS. |
| 103 | This was previously done in a best attempt manner. |
| 104 | |
| 105 | ### Bug Fixes |
| 106 | |
| 107 | - The MacOS binaries were not successfully released in 2021.3.3 and 2021.3.4. This release is aimed at addressing that. |
| 108 | |
| 109 | ## 2021.3.3 |
| 110 | |
| 111 | ### Improvements |
| 112 | |
| 113 | - Tunnel create command, as well as, running ad-hoc tunnels using `cloudflared tunnel -name NAME`, will not overwrite |
| 114 | existing files when writing tunnel credentials. |
| 115 | |
| 116 | ### Bug Fixes |
| 117 | |
| 118 | - Tunnel create and delete commands no longer use path to credentials from the configuration file. |
| 119 | If you need ot place tunnel credentials file at a specific location, you must use `--credentials-file` flag. |
| 120 | - Access ssh-gen creates properly named keys for SSH short lived certs. |
| 121 | |
| 122 | |
| 123 | ## 2021.3.2 |
| 124 | |
| 125 | ### New Features |
| 126 | |
| 127 | - It is now possible to obtain more detailed information about the cloudflared connectors to Cloudflare Edge via |
| 128 | `cloudflared tunnel info <name/uuid>`. It is possible to sort the output as well as output in different formats, |
| 129 | such as: `cloudflared tunnel info --sort-by version --invert-sort --output json <name/uuid>`. |
| 130 | You can obtain more information via `cloudflared tunnel info --help`. |
| 131 | |
| 132 | ### Bug Fixes |
| 133 | |
| 134 | - Don't look for configuration file in default paths when `--config FILE` flag is present after `tunnel` subcommand. |
| 135 | - cloudflared access token command now functions correctly with the new token-per-app change from 2021.3.0. |
| 136 | |
| 137 | |
| 138 | ## 2021.3.0 |
| 139 | |
| 140 | ### New Features |
| 141 | |
| 142 | - [Cloudflare One Routing](https://developers.cloudflare.com/cloudflare-one/tutorials/warp-to-tunnel) specific commands |
| 143 | now show up in the `cloudflared tunnel route --help` output. |
| 144 | - There is a new ingress type that allows cloudflared to proxy SOCKS5 as a bastion. You can use it with an ingress |
| 145 | rule by adding `service: socks-proxy`. Traffic is routed to any destination specified by the SOCKS5 packet but only |
| 146 | if allowed by a rule. In the following example we allow proxying to a certain CIDR but explicitly forbid one address |
| 147 | within it: |
| 148 | ``` |
| 149 | ingress: |
| 150 | - hostname: socks.example.com |
| 151 | service: socks-proxy |
| 152 | originRequest: |
| 153 | ipRules: |
| 154 | - prefix: 192.168.1.8/32 |
| 155 | allow: false |
| 156 | - prefix: 192.168.1.0/24 |
| 157 | ports: [80, 443] |
| 158 | allow: true |
| 159 | ``` |
| 160 | |
| 161 | |
| 162 | ### Improvements |
| 163 | |
| 164 | - Nested commands, such as `cloudflared tunnel run`, now consider CLI arguments even if they appear earlier on the |
| 165 | command. For instance, `cloudflared --config config.yaml tunnel run` will now behave the same as |
| 166 | `cloudflared tunnel --config config.yaml run` |
| 167 | - Warnings are now shown in the output logs whenever cloudflared is running without the most recent version and |
| 168 | `no-autoupdate` is `true`. |
| 169 | - Access tokens are now stored per Access App instead of per request path. This decreases the number of times that the |
| 170 | user is required to authenticate with an Access policy redundantly. |
| 171 | |
| 172 | ### Bug Fixes |
| 173 | |
| 174 | - GitHub [PR #317](https://github.com/cloudflare/cloudflared/issues/317) was broken in 2021.2.5 and is now fixed again. |
| 175 | |
| 176 | ## 2021.2.5 |
| 177 | |
| 178 | ### New Features |
| 179 | |
| 180 | - We introduce [Cloudflare One Routing](https://developers.cloudflare.com/cloudflare-one/tutorials/warp-to-tunnel) in |
| 181 | beta mode. Cloudflare customer can now connect users and private networks with RFC 1918 IP addresses via the |
| 182 | Cloudflare edge network. Users running Cloudflare WARP client in the same organization can connect to the services |
| 183 | made available by Argo Tunnel IP routes. Please share your feedback in the GitHub issue tracker. |
| 184 | |
| 185 | ## 2021.2.4 |
| 186 | |
| 187 | ### Bug Fixes |
| 188 | |
| 189 | - Reverts the Improvement released in 2021.2.3 for CLI arguments as it introduced a regression where cloudflared failed |
| 190 | to read URLs in configuration files. |
| 191 | - cloudflared now logs the reason for failed connections if the error is recoverable. |
| 192 | |
| 193 | ## 2021.2.3 |
| 194 | |
| 195 | ### Backward Incompatible Changes |
| 196 | |
| 197 | - Removes db-connect. The Cloudflare Workers product will continue to support db-connect implementations with versions |
| 198 | of cloudflared that predate this release and include support for db-connect. |
| 199 | |
| 200 | ### New Features |
| 201 | |
| 202 | - Introduces support for proxy configurations with websockets in arbitrary TCP connections (#318). |
| 203 | |
| 204 | ### Improvements |
| 205 | |
| 206 | - (reverted) Nested command line argument handling. |
| 207 | |
| 208 | ### Bug Fixes |
| 209 | |
| 210 | - The maximum number of upstream connections is now limited by default which should fix reported issues of cloudflared |
| 211 | exhausting CPU usage when faced with connectivity issues. |
| 212 | |