Skip to content

Latest commit

 

History

History
105 lines (82 loc) · 7.25 KB

plugin_server_nodeattestor_k8s_sat.md

File metadata and controls

105 lines (82 loc) · 7.25 KB

Server plugin: NodeAttestor "k8s_sat" (deprecated)

This plugin has been deprecated in favor of the "k8s_psat" plugin and will be removed in a future release.

Must be used in conjunction with the agent-side k8s_sat plugin

The k8s_sat plugin attests nodes running in inside of Kubernetes. The server validates the signed service account token provided by the agent. This validation can be done in two different ways depending on the value of the use_token_review_api_validation flag:

  • If this value is set to false (default behavior), the attestor validates the token locally using the key provided in service_account_key_file.
  • If this value is set to true, the validation is performed using the Kubernetes Token Review API.

Note: If your cluster supports Service Account Token Volume Projection you should instead consider using the k8s_psat attestor due to the security considerations below.

The server uses a one-time UUID provided by the agent to generate a SPIFFE ID with the form:

spiffe://<trust_domain>/spire/agent/k8s_sat/<cluster>/<UUID>

The server does not need to be running in Kubernetes in order to perform node attestation. In fact, the plugin can be configured to attest nodes running in multiple clusters.

The main configuration accepts the following values:

Configuration Description Default
clusters A map of clusters, keyed by an arbitrary ID, that are authorized for attestation.

Each cluster in the main configuration requires the following configuration:

Configuration Description Default
service_account_allow_list A list of service account names, qualified by namespace (for example, "default:blog" or "production:web") to allow for node attestation. Attestation will be rejected for tokens bound to service accounts that aren't in the allow list.
use_token_review_api_validation Specifies how the service account token is validated. If false, validation is done locally using the provided key. If true, validation is done using token review API. false
service_account_key_file It is only used if use_token_review_api_validation is set to false. Path on disk to a PEM encoded file containing public keys used in validating tokens for that cluster. RSA and ECDSA keys are supported. For RSA, X509 certificates, PKCS1, and PKIX encoded public keys are accepted. For ECDSA, X509 certificates, and PKIX encoded public keys are accepted.
kube_config_file It is only used if use_token_review_api_validation is set to true. Path to a k8s configuration file for API Server authentication. A Kubernetes configuration file must be specified if SPIRE server runs outside of the k8s cluster. If empty, SPIRE server is assumed to be running inside the cluster and in-cluster configuration is used. ""

A sample configuration for SPIRE server running inside or outside a Kubernetes cluster and validating the service account token with a key file located at "/run/k8s-certs/sa.pub":

    NodeAttestor "k8s_sat" {
        plugin_data {
            clusters = {
                "MyCluster" = {
                    service_account_allow_list = ["production:spire-agent"]
                    service_account_key_file = "/run/k8s-certs/sa.pub"
                }
        }
    }

A sample configuration for SPIRE server running inside of a Kubernetes cluster and validating the service account token with the kubernetes token review API:

    NodeAttestor "k8s_sat" {
        plugin_data {
            clusters = {
                "MyCluster" = {
                    service_account_allow_list = ["production:spire-agent"]
                    use_token_review_api_validation = true
                }
        }
    }

A sample configuration for SPIRE server running outside of a Kubernetes cluster and validating the service account token with the kubernetes token review API:

    NodeAttestor "k8s_sat" {
        plugin_data {
            clusters = {
                "MyCluster" = {
                    service_account_allow_list = ["production:spire-agent"]
                    use_token_review_api_validation = true
                    kube_config_file = "path/to/kubeconfig/file"
                }
        }
    }

In addition, this plugin generates the following selectors:

Selector Example Description
k8s_sat:cluster k8s_sat:cluster:MyCluster Name of the cluster (from the plugin config) used to verify the token signature
k8s_sat:agent_ns k8s_sat:agent_ns:production Namespace that the agent is running under
k8s_sat:agent_sa k8s_sat:agent_sa:spire-agent Service Account the agent is running under

Security Considerations

At this time, the service account token does not contain claims that could be used to strongly identify the node/daemonset/pod running the agent. This means that any container running in an allowed service account can masquerade as an agent, giving it access to any identity the agent is capable of issuing. It is STRONGLY recommended that agents run under a dedicated service account.

It should be noted that due to the fact that SPIRE can't positively identify a node using this method, it is not possible to directly authorize identities for a distinct node or sets of nodes. Instead, this must be accomplished indirectly using a service account and deployment that leverages node affinity or node selectors.