Skip to content

Allow k8s administrators to override ZNode path #681

Closed

Description

@nightkr

This is currently not allowed because it would let users escalate "Is allowed to create sandboxed ZNodes" to "Is allowed to take ownership of any named ZNode".

However, this is preventing users from restoring failed clusters from backups, since there is no way to influence the UID generation at all. One possible compromise would be to introduce a new field ZookeeperZnode.status.znodePath, which defaults to /{uid}. This would let administrators status-patch the object to override the path, while regular users are typically prohibited (by K8s) from editing the status subresource.

Activity

  1. self-assigned this
    on Mar 25, 2024
  2. moved this to Development: In Progress in Stackable Engineeringon Mar 25, 2024
  3. sbernauer commented on Apr 5, 2024

    @sbernauer
    Member

    LGTM

  4. nightkr commented on Apr 10, 2024

    @nightkr
    ContributorAuthor

    Moving this into the voting phase.

  5. nightkr commented on Apr 17, 2024

    @nightkr
    ContributorAuthor

    No dissent, considering this accepted.

  6. moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineeringon Apr 26, 2024
  7. moved this from Development: Waiting for Review to Development: Done in Stackable Engineeringon May 2, 2024
  8. lfrancke commented on May 6, 2024

    @lfrancke
    Member

    Is this anything we documented?

  9. moved this from Development: Done to Acceptance: In Progress in Stackable Engineeringon May 6, 2024
  10. sbernauer commented on May 6, 2024

    @sbernauer
    Member

    Is this already implemented? #799 looks like the implementation and is not merged yet

  11. lfrancke commented on May 6, 2024

    @lfrancke
    Member

    I don't know. I found this in the Done column

  12. nightkr commented on May 16, 2024

    @nightkr
    ContributorAuthor

    Not sure how this got moved to done, #799 has indeed not been reviewed yet.

    Is this anything we documented?

    It's documented in the PR, but since that still hasn't been merged...

  13. moved this from Acceptance: In Progress to Development: Waiting for Review in Stackable Engineeringon May 16, 2024
  14. moved this from Development: Waiting for Review to Development: In Review in Stackable Engineeringon May 27, 2024
  15. moved this from Development: In Review to Development: Done in Stackable Engineeringon Jun 21, 2024
  16. lfrancke commented on Jun 26, 2024

    @lfrancke
    Member

    As this has been merged now, can you please include a link to the generated docs?

  17. moved this from Development: Done to Acceptance: In Progress in Stackable Engineeringon Jun 26, 2024
  18. moved this from Acceptance: In Progress to Done in Stackable Engineeringon Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions