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

chore(deps): Bump github.com/openziti/ziti from 1.1.9 to 1.2.0 #127

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 11, 2024

Bumps github.com/openziti/ziti from 1.1.9 to 1.2.0.

Release notes

Sourced from github.com/openziti/ziti's releases.

v1.2.0

Release 1.2.0

What's New

  • New Router Metrics
  • Changes to identity connect status
  • HA Bootstrap Changes
  • Connect Events
  • SDK Events
  • Bug fixes and other HA work

New Router Metrics

The following new metrics are available for edge routers:

  1. edge.connect.failures - meter tracking failed connect attempts from sdks This tracks failures to not having a valid token. Other failures which happen earlier in the connection process may not be tracked here.
  2. edge.connect.successes - meter tracking successful connect attempts from sdks
  3. edge.disconnects - meter tracking disconnects of previously successfully connected sdks
  4. edge.connections - gauge tracking count of currently connected sdks

Identity Connect Status

Ziti tracks whether an identity is currently connected to an edge router. This is the hasEdgeRouterConnection field on Identity.

Identity connection status used to be driven off of heartbeats from the edge router. This feature doesn't work correctly when running with controller HA.

To address this, while also providing more operation insight, connect events were added (see below for more details on the events themselves).

The controller can be configured to use status from heartbeats, connect events or both. If both are used as source, then if either reports the identity as connected, then it will show as connected. This is intended for when you have a mix of routers and they don't all yet supported connect events.

The controller now also aims to be more precise about identity state. There is a new field on Identity: edgeRouterConnectionStatus. This field can have one of three values:

  • offline
  • online
  • unknown

If the identity is reported as connected to any ER, it will be marked as online. If the identity has been reported as connected, but the reporting ER is now offline, the identity may still be connected to the ER. While in this state

... (truncated)

Changelog

Sourced from github.com/openziti/ziti's changelog.

Release 1.2.0

What's New

  • New Router Metrics
  • Changes to identity connect status
  • HA Bootstrap Changes
  • Connect Events
  • SDK Events
  • Bug fixes and other HA work

New Router Metrics

The following new metrics are available for edge routers:

  1. edge.connect.failures - meter tracking failed connect attempts from sdks This tracks failures to not having a valid token. Other failures which happen earlier in the connection process may not be tracked here.
  2. edge.connect.successes - meter tracking successful connect attempts from sdks
  3. edge.disconnects - meter tracking disconnects of previously successfully connected sdks
  4. edge.connections - gauge tracking count of currently connected sdks

Identity Connect Status

Ziti tracks whether an identity is currently connected to an edge router. This is the hasEdgeRouterConnection field on Identity.

Identity connection status used to be driven off of heartbeats from the edge router. This feature doesn't work correctly when running with controller HA.

To address this, while also providing more operation insight, connect events were added (see below for more details on the events themselves).

The controller can be configured to use status from heartbeats, connect events or both. If both are used as source, then if either reports the identity as connected, then it will show as connected. This is intended for when you have a mix of routers and they don't all yet supported connect events.

The controller now also aims to be more precise about identity state. There is a new field on Identity: edgeRouterConnectionStatus. This field can have one of three values:

  • offline
  • online
  • unknown

If the identity is reported as connected to any ER, it will be marked as online. If the identity has been reported as connected, but the reporting ER is now offline, the identity may still be connected to the ER. While in this state it will be marked as 'unknown'. After a configurable interval, it will be marked

... (truncated)

Commits
  • e9d6d83 Merge pull request #2519 from openziti/update-deps
  • 43b5ad5 Update deps and changelog
  • cdd2d80 Merge pull request #2518 from openziti/remove.unused.linter.field
  • d757798 removes unused field
  • 8797c35 Merge pull request #2511 from openziti/connect-events
  • 893e0f1 Merge pull request #2514 from openziti/squash-docker-images
  • 5ed13fb reduce Docker image sizes
  • 74386da Update deps and changelog. Test fixes and spiffe id check
  • 6e19839 Fixes from testing
  • fb80926 Simplify raft bootstrapping and controller initialization. Fixes #2212
  • Additional commits viewable in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [github.com/openziti/ziti](https://github.com/openziti/ziti) from 1.1.9 to 1.2.0.
- [Release notes](https://github.com/openziti/ziti/releases)
- [Changelog](https://github.com/openziti/ziti/blob/main/CHANGELOG.md)
- [Commits](openziti/ziti@v1.1.9...v1.2.0)

---
updated-dependencies:
- dependency-name: github.com/openziti/ziti
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Nov 11, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 25, 2024

Superseded by #130.

@dependabot dependabot bot closed this Nov 25, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/openziti/ziti-1.2.0 branch November 25, 2024 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants