Confidential compute is currently surfaced in Akash via placement attributes that select nodes with SEV-SNP and Kata runtime support. What's missing is a per-service knob to control whether the provider injects an attestation sidecar into the resulting confidential VM. The default needs to be sensible if a tenant placed a workload on confidential-compute hardware via placement attributes, they almost certainly want attestation while leaving an opt-out for tenants bringing their own attestation tooling.
Confidential compute is currently surfaced in Akash via placement attributes that select nodes with SEV-SNP and Kata runtime support. What's missing is a per-service knob to control whether the provider injects an attestation sidecar into the resulting confidential VM. The default needs to be sensible if a tenant placed a workload on confidential-compute hardware via placement attributes, they almost certainly want attestation while leaving an opt-out for tenants bringing their own attestation tooling.