hanzozt/zt
1
0
Fork 0
mirror of https://github.com/hanzozt/zt.git synced 2026-10-30 15:04:55 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
zt/changelogs/CHANGELOG.0.30.md
T
zeekay 241625e7d9 rename: ziti → zt across all paths 
- Repo names: ziti-* → zt-*
- Go modules: github.com/hanzozt/ziti → github.com/hanzozt/zt
- Docker images: hanzozt/ziti-* → hanzozt/zt-*
- C/Java/JS symbols: ziti_* → zt_*
- File and directory names updated
2026-02-18 18:34:19 -08:00

18 KiB
Raw Permalink Blame History

Release 0.30.5

What's New

  • Initial proxy support in host.v1/host.v2

Proxy Support in host.v1/host.v2

host.v1 and host.v2 configurations may now specify a proxy to use. Currently only HTTP Connect proxies which don't require authentication are supported.

Example using host.v1

{
    "address": "192.168.2.50",
    "port": 1234,
    "protocol": "tcp",
    "proxy": {
        "address": "192.168.1.110:3128",
        "type": "http"
    }
}

Component Updates and Bug Fixes

Release 0.30.4

What's New

  • zt edge quickstart](https://github.com/hanzozt/zt/issues/1298). You can now download the zt CLI and have a functioning network with just one command. The network it creates is ephemeral and is intended to be torn down when the process exits. It is intended for quick evaluation and testing of an overlay network. It supports the following flags:

        --already-initialized     Specifies the PKI does not need to be created and the db does not need to be initialized. Recommended to be combined with --home. If --home is not specified the environment will be destroyed on shutdown! default: false
    --ctrl-address string     Sets the advertised address for the control plane and API
    --ctrl-port int16         Sets the port to use for the control plane and API
-h, --help                    help for quickstart
    --home string             Sets the directory the environment should be installed into. Defaults to a temporary directory. If specified, the environment will not be removed on exit.
-p, --password string         Password to use for authenticating to the Ziti Edge Controller. default: admin
    --router-address string   Sets the advertised address for the integrated router
    --router-port int16       Sets the port to use for the integrated router
-u, --username string         Username to use when creating the Ziti Edge Controller. default: admin

    Example Usage:

    zt edge quickstart \
  --ctrl-address potato \
  --ctrl-port 12345 \
  --router-address avocado \
  --router-port 23456 \
  --home $HOME/.zt/pet-zt \
  --already-initialized \
  --username someOtherUsername \
  --password someOtherPassword

  • Bugfixes

Component Updates and Bug Fixes

  • github.com/hanzozt/zt: v0.30.3 -> v0.30.4
    • Fixed an issue causing router configs to be rewritten when docker compose was brought up with existing configs

Release 0.30.3

What's New

  • Bugfixes

Component Updates and Bug Fixes

Release 0.30.2

What's New

  • Identity type consolidation
  • HTTP Connect Proxy support for control channel and links

Identity Type Consolidation

Prior to this release there were four identity types:

  • User
  • Service
  • Device
  • Router

Of these four types, only Router has any functional purpose. Given that, the other three have been merged into a single Default identity type. Since Router identities can only be created by the system, it's no longer necessary to specify the identity type when creating identities.

The identity type may still be provided, but a deprecation warning will be emitted.

Backwards Compatibility

Existing non-Router identities will be migrated to the Default identity type. If an identity type other than Default is provided when creating an identity, it will be coerced to the Default type. Existing code may have issues with the new identity type being returned.

HTTP Connect Proxy support

Routers may now specify a proxy configuration which will be used when establishing connections to controllers and data links to other routers. At this point only HTTP Connect Proxies with no authentication required are supported.

Example router config:

proxy:
  type: http
  address: localhost:3128

Component Updates and Bug Fixes

Release 0.30.1

What's New

Component Updates and Bug Fixes

  • github.com/hanzozt/zt: v0.30.0 -> v0.30.1
    • Issue #1225 - Updated ZITI_ROUTER_ADVERTISED_HOST to use the more common naming convention of ZITI_ROUTER_ADVERTISED_ADDRESS
    • Issue #1233 - Added lsof to the list of prerequisites to be checked during quickstart

Release 0.30.0

What's New

  • Link management is now delegated to routers
  • Controller and routers can operate with a single listening port

Link Management Updates

Previously, the controller would do its best to determine where links needed to be established. It would send messages to the routers, telling them which addresses to dial on other routes. The routers would in turn let the controller know if link establishment was successful or if the router already had a link to the given endpoint.

With this release, the controller will only let routers know which routers exist, whether they are currently connected to the controller, and what link listeners they are advertising. The routers will now decide which links to make and let the controllers know as links are created and broken.

Link Groups

Both dialers and listeners can now specify a set of groups. If no groups are specified, the dialer or listener will be placed in the default group. Dialers will only attempt to dial listeners who have at least one group in common with them.

Failed Links

Previously when a link failed, the controller would show it in the link list as failed for a time before removing it. Now failed links are removed immediately. There are existing link events for link creation and link failure which can be used for forensics.

Duplicate Links

There is a new link status Duplicate used when a router receives a link request and determines that it's a duplicate of an existing link. This happens when two routers both have listeners and dialers. They will often dial each other at the same time, resulting in a duplicate link.

Compatibility

If you use a 0.30+ controller with older routers, the controller will still do link calculation and send dial messages, as long as the enableLegacyLinkMgmt setting is set to true.

If you use a pre 0.30.0 controller with newer routers, the new routers will still accept the dial messages.

New Configuration

Controller

The controller has three new options:

network:
    routerMessaging:
        queueSize: 100
        maxWorkers: 100
    enableLegacyLinkMgmt: true

When a router connects or disconnects from the controller, we send two sets of updates.

  1. If a router has connected we send it the the state of the other routers
  2. We send all the other routers the updated state of the connecting/disconnecting router

These messages are sent using a worker pool. The size of the queue feeding the worker pool is controlled with routerMessaging.queueSize. The max size of the worker pool is controlled used the routerMessaging.maxWorkers option.

  • queueSize
    • Min value: 0
    • Max value: 1,000,000
    • Default: 100
  • maxWorkers
    • Min value: 1
    • Max value: 10,000
    • Default: 100

If you have routers older than 0.30.0, the controller will calculate which links to dial. This can be disabled by setting enableLegacyLinkMgmt to false. This setting currently defaults to true, but will default to false in a future release. In a subsequent release this functionality will be removed all together.

Router

The router has new configuration options for link dialing.

link:
   dialers:
       - binding: transport
         groups: 
             - public
             - vpc1234
         healthyDialBackoff:
             retryBackoffFactor: 1.5
             minRetryInterval: 5s
             maxRetryInterval: 5m
         unhealthyDialBackoff:
             retryBackoffFactor: 10
             minRetryInterval: 1m
             maxRetryInterval: 1h
    listeners:
        - binding: transport
          groups: vpc1234

Groups

See above for a description of link groups work.

Default value: default

Dial Back-off

Dialers can be configured with custom back-off behavior. Each dialer has a back-off policy for dialing healthy routers (those that are connected to a controller) and a separate policy for unhealthy routers.

The back-off policies have the following attributes:

  • minRetryInterval - duration specifying the minimum time between dial attempts
  • maxRetryInterval - duration specifying the maximum time between dial attempts
  • retryBackoffFactor - factor by which to increase the retry interval between failed dial attempts
    • Min value: 1
    • Max value: 100
    • Default: 1.5 for healthy, 100 for unhealthy

Single Port Support / ALPN

Ziti Controller and Routers can operate with a single open port. In order to implement this feature we use ALPN (Application Layer Protocol Negotiation) TLS extension. It allows TLS client to request and TLS server to select appropriate application protocol handler during TLS handshake.

Protocol Details

The following protocol identifiers are defined:

id purpose
zt-ctrl Control plane connections
zt-link Fabric link connections
zt-edge Client SDK connection to Edge Routers

Standard HTTP protocol identifiers (h2, http/1.1) are used for Controller REST API and Websocket listeners.

Backward Compatibility

This feature is designed to be backward compatible with SDK clients: older client will still be able to connect without requesting zt-edge protocol.

Breaking

Older routers won't be able to establish control channel or fabric links with updated network. However, newer Edge Routers should be able to join older network in some circumstances -- only outbound links from new Routers would work.

Component Updates and Bug Fixes

Reference in New Issue View Git Blame Copy Permalink