Closed
Description
What would you like to be added?
This issue is for being consensus on building a FIPS 140-3 compliant flavor/variant of k8s within the kubernetes project or CNCF organization.
While not important to all users, there are a significant number of users in the US Government/public sector that require FIPS 140-3 compliance for k8s. Given that golang is adding FIPS 140-3 compliant native libs, this would be a good time to evaluate what a FIPS compliant k8s release would look like.
Why is this needed?
No FIPS compliant k8s releases are done today through the kubernetes project. While not a universal requirement, there are a significant number of users who do have 140-3 requirements who would benefit from a FIPS compliant k8s release thats not tied to a specific vendor.
Metadata
Metadata
Assignees
Labels
Categorizes issue or PR as related to a new feature.Denotes an issue or PR that has aged beyond stale and will be auto-closed.Indicates an issue or PR lacks a `triage/foo` label and requires one.Categorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Release.
Type
Projects
Status
Closed / Done