docs: document collateral-proxy#2479
Conversation
Do the documentation changes need to be backported?Changes to
|
|
| To inspect the metrics, query the endpoint from inside the cluster, for example: | ||
|
|
||
| ```bash | ||
| kubectl exec statefulset/collateral-proxy -- wget -qO- http://127.0.0.1/metrics |
There was a problem hiding this comment.
Could also be done with port forwarding (since this is not a CC pod). The script would be more complicated in that case, but we could at least mention the possibility.
|
|
||
| Using the proxy requires deploying the proxy once per cluster, then pointing your Contrast components at it when generating your deployment. | ||
|
|
||
| ### Deploy the proxy |
There was a problem hiding this comment.
I'm not sure whether we should even document the server at this point.
- It's not going to stay in this repo for too long.
- k8s resource defs should be released.
Maybe shelve this section for now and focus on the client side and how Contrast handles this.
| - name: proxy | ||
| port: 80 | ||
| targetPort: 80 |
There was a problem hiding this comment.
We need a security considerations section that explains why port 80 is ok (answer: the libraries we use check all certificates against an embedded root cert).
2 participants
No description provided.