Skip to content

Commit

Permalink
Merge pull request #266 from keeganwitt/markdown_fixes
Browse files Browse the repository at this point in the history 
Fix tables, format tables, and fix numbering
  • Loading branch information
@ajessup
ajessup committed Jan 30, 2023
2 parents bda7fc1 + c5fc4b8 commit f6e7584
Show file tree
Hide file tree
Showing 4 changed files with 22 additions and 22 deletions.
6 changes: 3 additions & 3 deletions content/docs/latest/deploying/install-agents.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -121,9 +121,9 @@ spire-server-0 1/1 Running 0 103m

When the agent deploys, it binds the volumes summarized in the following table:

| Volume | Description | Mount Location |
| :------ |:---------- | :------------- |
| **spire-config** | The spire-agent configmap created in the [Create Agent Configmap](#step-2-create-agent-configmap) step. | **/run/spire/config** |
| Volume | Description | Mount Location |
|:------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|
| **spire-config** | The spire-agent configmap created in the [Create Agent Configmap](#step-2-create-agent-configmap) step. | **/run/spire/config** |
| **spire-sockets** | The hostPath, which will be shared with all other pods running on the same worker host. It contains a UNIX domain socket that workloads use to communicate with the agent API. | **/run/spire/sockets** |

# Where next?
Expand Down
6 changes: 3 additions & 3 deletions content/docs/latest/deploying/install-server.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -181,10 +181,10 @@ When you deploy the server it automatically configures a livenessProbe on the SP

When the server deploys, it binds in the volumes summarized in the following table:

| Volume | Description | Mount Location |
| :------ |:---------- | :------------- |
| Volume | Description | Mount Location |
|:-----------------|:---------------------------------------------------------------------------|:----------------------|
| **spire-config** | A reference to the **spire-server** configmap created in the previous step | **/run/spire/config** |
| **spire-data** | The hostPath for the server's SQLite database and keys file | **/run/spire/data** |
| **spire-data** | The hostPath for the server's SQLite database and keys file | **/run/spire/data** |

### Create Server Service

Expand Down
20 changes: 10 additions & 10 deletions content/docs/latest/deploying/registering.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,11 +60,11 @@ A selector is a native property of a node or workload that SPIRE can verify befo

Different selectors are available depending on the platform or architecture on which the workload’s application is running.

| For a list of supported selectors for this platform | Go here |
| ---------------- | ----------- |
| **Kubernetes** | The [configuration reference page for the Kubernetes Node Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_nodeattestor_k8s_sat.md)
| **AWS** | The [configuration reference page for the AWS Node Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_nodeattestor_aws_iid.md)
| **Azure** | The [configuration reference page for the Azure Managed Service Identity Node Resolver](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_noderesolver_azure_msi.md)
| For a list of supported selectors for this platform | Go here |
|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Kubernetes** | The [configuration reference page for the Kubernetes Node Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_nodeattestor_k8s_sat.md) |
| **AWS** | The [configuration reference page for the AWS Node Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_nodeattestor_aws_iid.md) |
| **Azure** | The [configuration reference page for the Azure Managed Service Identity Node Resolver](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_noderesolver_azure_msi.md) |

## 2. Defining the SPIFFE ID of the Workload

Expand All @@ -79,11 +79,11 @@ spire-server entry create \
-selector unix:gid:1000
```

| For a list of supported selectors for this platform | Go here |
| ---------------- | ----------- |
| **Unix** | The [configuration reference page for the Unix Workload Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_agent_workloadattestor_unix.md)
| **Kubernetes** | The [configuration reference page for the Kubernetes Workload Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_agent_workloadattestor_k8s.md)
| **Docker** | The [configuration reference page for the Docker Workload Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_agent_workloadattestor_docker.md)
| For a list of supported selectors for this platform | Go here |
|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Unix** | The [configuration reference page for the Unix Workload Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_agent_workloadattestor_unix.md) |
| **Kubernetes** | The [configuration reference page for the Kubernetes Workload Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_agent_workloadattestor_k8s.md) |
| **Docker** | The [configuration reference page for the Docker Workload Attestor](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_agent_workloadattestor_docker.md) |

# How to list registration entries

Expand Down
12 changes: 6 additions & 6 deletions content/docs/latest/spire-about/spire-concepts.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -90,12 +90,12 @@ This bootstrap bundle is a default configuration, and should be replaced with cu
13. The server authenticates the agent using the agent's SVID. The agent, in turn, completes the mTLS handshake and authenticates the server using the bootstrap bundle.
14. The server then fetches all [authorized registration entries](#authorized-registration-entries) from its data store and sends them to the agent.
15. The agent then sends workload CSRs to the server which the server signs and returns as workload SVIDs to the client. The client puts them in cache.
15. Now fully bootstrapped, the agent starts listening on the Workload API socket.
16. A workload calls the Workload API to request a SVID.
17. The agent initiates the workload attestation process by calling its workload attestors, providing them with the process ID of the workload process.
18. Attestors use kernel and userspace calls to discover additional bits of information about the workload.
19. The attestors return the discovered information to the agent in the form of _workload_ selectors.
20. The agent determines the workload's identity by comparing the discovered workload selectors to registration entries, and returns the correct SVID (already in its cache).
16. Now fully bootstrapped, the agent starts listening on the Workload API socket.
17. A workload calls the Workload API to request a SVID.
18. The agent initiates the workload attestation process by calling its workload attestors, providing them with the process ID of the workload process.
19. Attestors use kernel and userspace calls to discover additional bits of information about the workload.
20. The attestors return the discovered information to the agent in the form of _workload_ selectors.
21. The agent determines the workload's identity by comparing the discovered workload selectors to registration entries, and returns the correct SVID (already in its cache).

## Authorized Registration Entries

Expand Down

0 comments on commit f6e7584

Please sign in to comment.