Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add first draft of code walk-through doc #903

Merged
merged 5 commits into from
Dec 3, 2021
Merged

Conversation

cfryanr
Copy link
Member

@cfryanr cfryanr commented Dec 3, 2021

Release note:

None, doc-only changes.

NONE

@codecov
Copy link

codecov bot commented Dec 3, 2021

Codecov Report

Merging #903 (aa361a7) into main (6830274) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #903   +/-   ##
=======================================
  Coverage   79.01%   79.01%           
=======================================
  Files         133      133           
  Lines        9716     9716           
=======================================
  Hits         7677     7677           
  Misses       1779     1779           
  Partials      260      260           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6830274...aa361a7. Read the comment docs.


## Supervisor API endpoints

The Supervisor's endpoints are:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would be helpful to link to the OIDC spec here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated!

at runtime as a separate Deployment. It exists as a separate binary in the same container image as the other
Pinniped server components. When needed, the Concierge will exec into the Deployment's pods to invoke the cert agent
binary to query for data. This is to support the Token Credential Request API strategy described in the
[Supported Cluster Types document]({{< ref "../reference/supported-clusters" >}}).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph is a little vague. Maybe something like, "when needed, the concierge will exec into the kube-cert-agent deployment's pods to query for the keypair used to sign user credentials." rather than just "data" would make it clearer.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated!

@cfryanr cfryanr merged commit edd3547 into main Dec 3, 2021
@cfryanr cfryanr deleted the code-walkthrough-doc branch December 3, 2021 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants