📜 Document allowed-origins and session key-pairs#56
Merged
Conversation
- Add allowed-origins option to dashboard reference and ingress guide - Replace session.secret with session.key-pairs in dashboard reference - Remove obsolete csrf config from dashboard and cluster-api references - Simplify installation page; link to Ingress guide for exposure options Signed-off-by: Andres Morey <andres@kubetail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the dashboard reference and ingress guide to reflect recent configuration changes: a new
allowed-originsoption for proxied deployments, the replacement ofsession.secretwith rotatablesession.key-pairs, and removal of the obsoletecsrfconfig block. Also tightens the installation guide.Key Changes
allowed-originsto the dashboard reference and a matching tip in the ingress guidesession.secretwithsession.key-pairsin the dashboard referencecsrfconfig from dashboard and cluster-api referenceskubectl proxyexample from installation; link to the Ingress guide for exposure optionsChecklist