k-space/kube
12
1
Fork 3
Code Issues 64 Pull Requests Wiki Activity

rook-ceph secretspace disabled, configMapGenerator objects missing, mon-tools complaining #126

New Issue
Open
opened 2025-12-28 23:30:01 +00:00 by rasmus · 3 comments
rasmus commented 2025-12-28 23:30:01 +00:00
Owner
Copy Link

image.png
image.png
image.png
image.png

![image.png](/attachments/0f4ef871-94c4-404d-9ec1-4e7269efc1f1) ![image.png](/attachments/88da138d-e573-4410-b0f9-dbad72ec220b) ![image.png](/attachments/7173790f-3961-4f09-bdf2-f973eb025eb4) ![image.png](/attachments/927e1fb8-6de0-4f7d-ad13-d50b07563b86)
image.png
18 KiB
image.png
33 KiB
image.png
20 KiB
image.png
51 KiB
rasmus added the upkeep label 2025-12-28 23:30:01 +00:00
eaas was assigned by rasmus 2025-12-28 23:30:01 +00:00
rasmus commented 2025-12-28 23:31:09 +00:00
Author
Owner
Copy Link

@eaas any clue why secrets were disabled with 79ebad673012aa750edf569915663415e8a847d2?

@eaas any clue why secrets were disabled with 79ebad673012aa750edf569915663415e8a847d2?
rasmus commented 2025-12-28 23:32:28 +00:00
Author
Owner
Copy Link

It's also weird the configMap has only pve90 in it.

image.png

It's also weird the configMap has only pve90 in it. ![image.png](/attachments/66b88932-1b5d-4634-bcd5-148befd270d9)
image.png
90 KiB
eaas commented 2025-12-29 09:01:21 +00:00
Owner
Copy Link

Problem is that rook should be able to manage this configmap itself - it is supposed to write all mon hosts into it.

  1. I currently removed the error by manually re-creating the configmap
  2. I tried using all hosts as mon endpoints earlier but rook didnt like it
  3. I disabled the secrets as Argo and Rook both contending to update those caused issues

Have to think what would be a good solution.

Problem is that rook should be able to manage this configmap itself - it is supposed to write all mon hosts into it. 1. I currently removed the error by manually re-creating the configmap 2. I tried using all hosts as mon endpoints earlier but rook didnt like it 3. I disabled the secrets as Argo and Rook both contending to update those caused issues Have to think what would be a good solution.
😕 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
new app
shiny
bounty
10€
probably needs most of a visit dedicated to the task https://wiki.k-space.ee/en/about/task-bounties
bounty
20€
about a whole day or two to the task https://wiki.k-space.ee/en/about/task-bounties
bounty
5€
https://wiki.k-space.ee/en/about/task-bounties
bounty
package
See milestone, bounty for completing all issues.
disposal
Liability in safety, usability, space, or upkeep. It doesn't provide enough meaningful historical value (museum) nor personal interest.
 enchancement
Improving the existing
 greenlit
The stars have aligned: Orders have arrived, plan has been laid, only hands are needed. Just do it!
upkeep
Subjects of maintenance
No Label upkeep
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
akpall arti artur dos4dev eaas erki kkuusk lauri madis plaes rasmus sander savva
No Assignees eaas
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: k-space/kube#126
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?