Skip to content

Ptah Operator 0.2.4 qualification evidence, amendment 2

Choose a tag to compare

@denisvmedia denisvmedia released this 19 Oct 12:04
Immutable release. Only release title and notes can be modified.
bd80275

The second amendment to qualification-0.2.4, which stays the evidence the v0.2.4 acceptance was decided on.

An initial deployment check with monitoring ran on the published v0.2.4: kind with kube-prometheus-stack 92.10.1, v0.2.4 installed by digest with the profile's monitoring values, then every manager removed and restored. It found #673: the chart's ServiceMonitor selects no Service, so Prometheus had no target. With a deployer ServiceMonitor selecting the metrics Service, both managers were scraped, the lost-view alert reached the receiver 84 seconds after the removal, and its resolution 23 seconds after the restore. The owner kept v0.2.4 accepted with the defect recorded as a PA-09 exclusion (#674); #672 fixes the chart for the next release.

  • acceptance/: support/acceptance/0.2.0.json as it stands at bd80275, and the record rendered from it.
  • deployment-check-monitoring/: the check's result, step log, Prometheus targets and rules, the two receiver notifications, and the tools it ran.
  • custody/: the custody record of the restricted archive holding the check's full output, including an earlier attempt whose notifications were not dated against the removal and which is not counted.

Verify: download every asset, then run sha256sum -c SHA256SUMS. index.json lists each member's size and SHA-256.