Releases: dogmatiq/proclaim
Releases · dogmatiq/proclaim
Version 0.4.3
Changed
- Proclaim is now built against Go v1.21
- Updated AWS, Kubernetes and DNS-SD related dependencies
Version 0.4.2
Changed
- The Helm chart is now versioned in lockstep with Proclaim itself
Version 0.4.1
Changed
- Drastically reduced the re-reconciliation interval from 10 hours (the Kubernetes default), to the TTL of the DNS-SD instance (typically ~1 minute). This provides much more practical drift-detection behavior. Assuming there is no DNS record drift, the only overhead is a DNS query every TTL period.
- The
Discovered
event is now only emitted when a service instance is first discovered, or returns to being discoverable after a period of undiscoverability or drift. Prior to this change the event was emitted every time drift detection was performed.
Added
- Added granular debug logging for advertise, unadvertise, discover and finalization operations.
Version 0.4.0
Added
- Added
env
key to Helm chart values
Fixed
- Handle
null
values inattributes
field
Changed
- Controller now loads all values from the
proclaim
secret as environment variables - [BC] Changed some Helm chart values for consistency:
- Added
deployment.labels
- Renamed
deploymentAnnotations
todeployment.annotations
- Renamed
podAnnotations
topod.annotations
- Renamed
podLabels
topod.labels
- Renamed
commonLabels
tocommon.labels
- Added
Removed
- Removed various unused Helm chart values
Version 0.3.0
Changed
- [BC] Changed
attributes
field to accept any scalar type- Empty string values are longer treated as "flags", use
true
instead - Regular associative attributes with empty values are now supported
- Empty string values are longer treated as "flags", use
Version 0.2.0
Added
- The controller now verifies instances are advertised correctly using DNS-SD queries
- Added "conditions" to CRD status, as per Kubernetes API design recommendations
- The
Adopted
condition indicates whether a suitable DNS provider has been found - The
Advertised
condition indicates whether the DNS records have been successfully created/updated - The
Discoverable
condition indicates whether the service is discoverable via DNS-SD
- The
- Added more granular events
- Added
targets
field to CRD, allowing (future) support for multiple targets per instance
Fixed
- Marked
DNSIMPLE_TOKEN
environment variable as "sensitive" to avoid showing its value in validation output
Changed
- [BC] Moved DNS-SD properties in CRD into
instance
subkey ofspec
- [BC] Renamed
service
fields in CRD toserviceType
for better alignment with the DNS-SD spec - [BC] Removed
targetHost
andtargetPort
fields from CRD, see newtargets
field instead
Version 0.1.0
- Initial release