Skip to content

Commit

Permalink
Fix broken links
Browse files Browse the repository at this point in the history
Signed-off-by: George Vanburgh <[email protected]>
  • Loading branch information
georgevanburgh committed Apr 15, 2022
1 parent 6707894 commit d3d6a2b
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions content/docs/latest/deploying/registering.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ The server will send to the agent a list of all registration entries for workloa

During workload attestation, the agent discovers selectors and compares them to those in the cached registration entries to determine which SVIDs they should assign to the workload.

You register a workload either by issuing the `spire-server entry create` command at the command line or calling directly into the Registration API, as described in the [Registration API documentation](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/proto/spire/api/registration/registration.proto). Existing entries can be modified using the `spire-server entry update` command.
You register a workload either by issuing the `spire-server entry create` command at the command line or calling directly into the Entry API, as described in the [Entry API documentation](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/proto/spire/api/server/entry/v1/entry.proto). Existing entries can be modified using the `spire-server entry update` command.

{{< info >}}
When running on Kubernetes, a common way to invoke commands on the SPIRE Server is through the `kubectl exec` command on a pod running the SPIRE Server. For example:
Expand Down Expand Up @@ -63,7 +63,7 @@ Different selectors are available depending on the platform or architecture on w
| 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 Resolver](https://github.com/spiffe/spire/blob/{{< spire-latest "tag" >}}/doc/plugin_server_noderesolver_aws_iid.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 Down
4 changes: 2 additions & 2 deletions content/docs/latest/spiffe-about/get-involved.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,5 +36,5 @@ Day to day contributions are vetted by the project's maintainers. Overall projec

Find SPIFFE and SPIRE logos here:

* [SPIFFE](https://branding.cncf.io/projects/spiffe)
* [SPIRE](https://branding.cncf.io/projects/spire)
* [SPIFFE](https://branding.cncf.io/tree/master/projects/spiffe)
* [SPIRE](https://branding.cncf.io/tree/master/projects/spire)

0 comments on commit d3d6a2b

Please sign in to comment.