Skip to content

FIPS 140-3 Compliance K8s Release  #129075

Closed
@idunbarh

Description

@idunbarh

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

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/authCategorizes an issue or PR as relevant to SIG Auth.sig/releaseCategorizes an issue or PR as relevant to SIG Release.

    Type

    No type

    Projects

    Status

    Closed / Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions