v0.20.0

Highlights

Scheduled upgrades

Schedule unattended upgrades for the future. This allows you to stage everything necessary for a chain upgrade ahead of time, and the upgrade will roll out automatically. Additionally, this enables syncing an archive node across versions without requiring action at the upgrade heights.

Example spec:

spec:
  chain:
    versions:
      - image: ghcr.io/strangelove-ventures/heighliner/noble:v1.0.0
        height: 1
      - image: ghcr.io/strangelove-ventures/heighliner/noble:v2.0.0
        height: 119000
      - image: ghcr.io/strangelove-ventures/heighliner/noble:v3.0.0
        height: 1296000
      - image: ghcr.io/strangelove-ventures/heighliner/noble:v3.1.0
        height: 2672000

When this feature is enabled, the spec.podTemplate.image value is ignored. spec.podTemplate.image is now deprecated and may be removed in a future version.

For more information, see #373

PVC sizing #380

• New PVCs will be created with the minimum size, either the spec.volumeClaimTemplate.resources.storage, spec.instanceOverrides[instanceName].volumeClaimTemplate.resources.storage if an override is set, or the size of the volume snapshot (data source or auto data source)
• PVC autoscaling now operates at the per-instance level to minimize resource usage
• autoDataSource can now be limited to snapshots from the same instance with matchInstance: true

Fixes

• Fixes issue #339 with update rollouts where more pods were taken down than intended.

What's Changed

• scheduled upgrades by @agouin in #373
• Backwards compatibility when spec.chain.versions is not populated by @agouin in #375
• simplify status and perform rollouts in correct order by @agouin in #376
• Dont require podspec image by @agouin in #378
• build(deps): Bump google.golang.org/grpc from 1.57.0 to 1.57.1 by @dependabot in #377
• Run trivy on image in PR by @agouin in #379
• PVC auto scale on a per ordinal basis by @agouin in #380
• Allow adding additional start args by @agouin in #381

Full Changelog: v0.18.0...v0.20.0