djpbessems/ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix typo in doc

Browse Source
This commit is contained in:
Ryan Richard 2021-12-03 09:17:17 -08:00
parent 3ea90467b7
commit 2736c3603a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/content/docs/reference/code-walkthrough.md
View File

@ -210,7 +210,7 @@ The Kubernetes API groups used by the Pinniped CRDs and the Concierge's aggregat
at install time. By default, everything is placed in the `*.pinniped.dev` group, at install time. By default, everything is placed in the `*.pinniped.dev` group,
for example one of the CRDs is `jwtauthenticators.authentication.concierge.pinniped.dev`. for example one of the CRDs is `jwtauthenticators.authentication.concierge.pinniped.dev`.
Making this group name configurable is not a common pattern in Kubernetes apps, but is yields several advantages. Making this group name configurable is not a common pattern in Kubernetes apps, but it yields several advantages.
A discussion of this feature, including its implementation details, can be found in the A discussion of this feature, including its implementation details, can be found in the
[blog post for release v0.5.0](https://pinniped.dev/posts/multiple-pinnipeds/). Similar to leader election, [blog post for release v0.5.0](https://pinniped.dev/posts/multiple-pinnipeds/). Similar to leader election,
much of this behavior is implemented in client middleware, and will not be obvious when reading the code. much of this behavior is implemented in client middleware, and will not be obvious when reading the code.