TLS client certificates and two-step config fetch for confidential clusters
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Feature Request
Environment
Confidential Clusters.
Desired Feature
For confidential cluster use cases, we want to deliver the full Ignition config only to nodes that passed attestation against a specific attestation server.
The design would look like the following:
- Get the config from the cloud metadata
- It contains no secret values
- It includes a new config entry that points to the attestation server (KBS?) to use for attestation
- It includes a merge/replace config that needs mutual TLS to be fetched
- Ignition would call out to the attestation agent (KBS client?) to perform the attestation.
- The attestation client will get back a TLS client certificate.
- Ignition would then use this client certificate to fetch the full config and resume configuration/booting.
Other Information
N/A
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 files, tests, or entry points are named. Start by mapping Ignition's cloud-metadata fetch, merge/replace configuration handling, and the attestation-client integration described here. Done would require an agreed design and implementation for attestation, TLS client-certificate retrieval, authenticated full-config fetching, and resumed boot configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100