output "bucket" { description = "Where evidence goes." value = oci_objectstorage_bucket.evidence.name } output "capture" { description = "Set these, then run capture.sh from the Standard (t1) folder." value = <<-EOT export CLUSTER_ID=${var.cluster_id} REGION=${var.region} OS_NAMESPACE=${data.oci_objectstorage_namespace.this.namespace} EVIDENCE_BUCKET=${oci_objectstorage_bucket.evidence.name} # Set KUBE_ENDPOINT=PRIVATE_ENDPOINT when the API server has no public endpoint. ./capture.sh EOT } output "verify" { description = "Checks, on a test pod you do not mind isolating." value = <<-EOT Run the capture command above against a test pod, then: oci os object list -ns ${data.oci_objectstorage_namespace.this.namespace} -bn ${oci_objectstorage_bucket.evidence.name} --prefix / --query 'data[].name' # pod.json, images.tsv, logs, events, capture.log, each with a .sha256 oci bv boot-volume-backup list --compartment-id ${local.node_compartment} --query "data[?\"freeform-tags\".incident==''].\"display-name\"" kubectl get pod -n --show-labels # quarantine=true As someone who can delete objects in the bucket, the retention rule must still refuse this: oci os object delete -ns ${data.oci_objectstorage_namespace.this.namespace} -bn ${oci_objectstorage_bucket.evidence.name} --name ////pod.json Download the folder with an account that can read it, then run evidence-verify on it. EOT }