-
Notifications
You must be signed in to change notification settings - Fork 54
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
Beginning notes on how to reconfigure for keystone in 1.29 #845
Merged
addyess
merged 10 commits into
akd/prepare-release-notes-/1.29-ck2
from
KU-997/keystone-management-deprecated
Jun 14, 2024
Merged
Beginning notes on how to reconfigure for keystone in 1.29 #845
addyess
merged 10 commits into
akd/prepare-release-notes-/1.29-ck2
from
KU-997/keystone-management-deprecated
Jun 14, 2024
Conversation
This file contains 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
addyess
force-pushed
the
KU-997/keystone-management-deprecated
branch
from
June 13, 2024 17:59
a9f3d99
to
1ff17b5
Compare
evilnick
reviewed
Jun 13, 2024
evilnick
reviewed
Jun 13, 2024
evilnick
reviewed
Jun 14, 2024
evilnick
reviewed
Jun 14, 2024
evilnick
reviewed
Jun 14, 2024
evilnick
reviewed
Jun 14, 2024
evilnick
approved these changes
Jun 14, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see MM chat
evilnick
added a commit
that referenced
this pull request
Jun 25, 2024
* Prepare release notes for 1.29+ck2, update generator templates * insert a line feed so as to not break web renderer * Beginning notes on how to reconfigure for keystone in 1.29 (#845) * Correct command mistakes in keystone upgrade nodes, add Day2 Ops section * Add installation instructions to use LDAP or Keystone Auth for fresh installations * Applied review comments from Nick --------- Co-authored-by: Nick Veitch <[email protected]> Co-authored-by: Kevin W Monroe <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Provide updated documentation on integration with external authn and authz endpoints for charmed-kubernetes. These changes adjust the
upgrade-notes.md
to explain revision specific upgrade concerns and changes to theldap.md
docs for fresh deployments.Details
Upgrades:
I've adjusting the
upgrade-notes.md
which covers ALL versions of charmed-kubernetes but is linked from the1.29/upgrading.md
page. Is this enough? Should these notes be in that page instead?The upgrade notes provide example situations where the charm may "block" in the event of an upgrade with keystone-credentials enabled and how the user should adjust the charm config in order to continue using the authn and authz endpoints.
Fresh Install Instructions:
These changes include a rewrite of the LDAP page which details how to use new charm config options to setup keystone for use in kubernetes authn and authz