ironcore-dev / ironcore-dev/ceph-provider
Not empty `Volume` can't be encrypted
Open
Nobody has claimed this yet.
area/storage
bug
- Dominant language
- Go
- Stars
- 4
- Forks
- 8
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
Describe the bug
If a Volume references an image the Volume can't be encrypted.
{"imageId": "505323310729f021ec9e940ba9e345109fb200bcb46730d706ff716ed9603e1", "error": "failed to set encryption header: failed to set encryption format: rbd: ret=-95, Operation not supported"}
github.com/onmetal/cephlet/pkg/controllers.(*ImageReconciler).
Investigation needed to check expected behaviour.
To Reproduce
metadata:
name: encryption-test
spec:
image: ghcr.io/onmetal/onmetal-image/gardenlinux:rootfs-dev-20230223
volumeClassRef:
name: general-purpose
encryption:
secretRef:
name: encryption-key-secret
resources:
storage: 5Gi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at pkg/controllers.(*ImageReconciler) and reproduce the failure with the provided Volume manifest and image reference. Investigate the expected behavior when an image-backed Volume is encrypted, then verify the chosen behavior against the reported RBD encryption error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100