Releases: OpsMx/oes-birger
Releases · OpsMx/oes-birger
v5.1.1-rc1
OP-22464-Controller-Debuglogs added logs
v5.1.1
Full Changelog: v5.1.0...v5.1.1
v5.1.0
BREAKING CHANGE
The --jaeger-endpoint has been renamed to --otlp-endpoint, which is how the open tracing systems have evolved.
This also changes the JAEGER_TRACE_URL envar to OTLP_URL.
What's Changed
- chore: update deps, Jaeger -> OTLP by @skandragon in #34
Full Changelog: v5.0.2...v5.1.0
v5.0.2
What's Changed
- set scheme on control and service URLs by @skandragon in #32
Full Changelog: v5.0.1...v5.0.2
v5.0.1
What's Changed
- Bump golang.org/x/crypto from 0.16.0 to 0.17.0 by @dependabot in #28
- add kubernetes example by @skandragon in #29
- chore: update deps by @skandragon in #30
- add keepalives to long-running wait-for-request in client by @skandragon in #31
Full Changelog: v5.0.0...v5.0.1
v5.0.0
BREAKING CHANGES
- The controller can be configured with optional TLS certificates for the command and control server, the service server, and the agent server. These are independent but could be the same certificates if a single hostname is used, a wildcard certificate is used, or multiple hostnames are present in the TLS certificate.
- By default, non-secure HTTP connections are used by all controller endpoints. It is expected that either certificates will be provided to the controller, the controller will have an ingress for all (or at least the agent) connections, or both controller TLS and secure ingress TLS termination will be used.
- All authentication is now token based (using JWTs) and the controller no longer acts as a certificate authority.
- The bootstrap command was removed as we no longer need to bootstrap certificates for command and control. The controller itself can be run with
--generate-agent-tokens
or--generate-controller-tokens
to make initial tokens for these types of connections. Each takes a list of names to generate tokens with the provided name. More than one name can be listed:--generate-agent-tokens smith,orange
. Using either of these options will cause the controller to exist after printing the tokens on stdout, and the options are exclusive. - The agent can optionally use insecure connections to the controller.
What's Changed
- chore: update deps by @skandragon in #26
- Use JWT rather than TLS certificates for authentication by @skandragon in #27
Full Changelog: v4.2.5...v5.0.0
Update base image and dependencies
What's Changed
- Update deps by @skandragon in #25
Full Changelog: v4.2.3...v4.2.5
Update Alpine base image
No functional changes.
v4.2.3
What's Changed
- fix: use a new buffer each read by @skandragon in #23
Full Changelog: v4.2.2...v4.2.3