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.

Sign up for GitHub

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

Jump to bottom

Document that an AD realm must not be shared between multiple k8s clusters #406

Closed
2 tasks done
nightkr opened this issue Apr 22, 2024 · 2 comments · Fixed by #408
Closed
2 tasks done

Document that an AD realm must not be shared between multiple k8s clusters #406

nightkr opened this issue Apr 22, 2024 · 2 comments · Fixed by #408
Assignees
@nightkr

Comments

@nightkr
Copy link
Member

nightkr commented Apr 22, 2024 •
edited
Loading

Followup to #402.

  • Add note to docs about each K8s cluster requiring its own AD realm.
  • Detect conflicts during AD provisioning, and link to the docs above.
@nightkr nightkr moved this to Development: In Progress in Stackable Engineering Apr 22, 2024
@nightkr nightkr self-assigned this Apr 22, 2024
nightkr added a commit that referenced this issue Apr 22, 2024
@nightkr
Document AD isolation requirements
f90ee3d 
See #406
@nightkr nightkr mentioned this issue Apr 22, 2024
Merged
@nightkr nightkr moved this from Development: In Progress to Development: In Review in Stackable Engineering Apr 22, 2024
@nightkr nightkr moved this from Development: In Review to Development: Waiting for Review in Stackable Engineering Apr 22, 2024
github-merge-queue bot pushed a commit that referenced this issue Apr 23, 2024
@nightkr @maltesander
Document AD principal conflicts (#408)
2e5cfd7 
* Document AD isolation requirements

See #406

* Add AD conflict troubleshooting guide

* Link to the troubleshooting guide on LDAP user conflicts

* Detect UPN conflicts as user conflicts

* Fix link label

* Update docs/modules/secret-operator/pages/troubleshooting.adoc

Co-authored-by: Malte Sander <[email protected]>

---------

Co-authored-by: Malte Sander <[email protected]>
@sbernauer sbernauer moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Apr 26, 2024
@sbernauer sbernauer moved this from Development: In Review to Development: Done in Stackable Engineering Apr 29, 2024
@lfrancke lfrancke moved this from Development: Done to Acceptance: In Progress in Stackable Engineering Apr 30, 2024
@lfrancke
Copy link
Member

None of the two checkboxes are ticked. Are they done?

@nightkr
Copy link
Member Author

nightkr commented May 6, 2024

Yes, #408 covers both of them.

@lfrancke lfrancke moved this from Acceptance: In Progress to Done in Stackable Engineering May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nightkr nightkr

Labels
None yet
Projects
Stackable Engineering
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document AD principal conflicts stackabletech/secret-operator
2 participants
@lfrancke @nightkr