zalando / zalando/postgres-operator
signatures for the containers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS EKS, OpenShift 4.7
- Are you running Postgres Operator in production? yes
- Type of issue? question
Are there signatures available Docker Content Trust (Notary) or GPG/SigStore (skopeo)?
It'd be nice to have signatures available to ensure the Image authenticity and integrity of the containers.
Kind regards,
--
stafwag
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
No repository file, test, or entry point is identified in the issue. Start by locating how the operator container image is built and published, then compare Docker Content Trust, GPG, and Sigstore options for the stated Kubernetes deployment. Done should include a defined signing approach and a way to verify image authenticity and integrity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- devops, release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100