Problem is that rook should be able to manage this configmap itself - it is supposed to write all mon hosts into it.
I currently removed the error by manually re-creating the configmap
I tried using all hosts as mon endpoints earlier but rook didnt like it
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@eaas any clue why secrets were disabled with 79ebad673012aa750edf569915663415e8a847d2?
It's also weird the configMap has only pve90 in it.
Problem is that rook should be able to manage this configmap itself - it is supposed to write all mon hosts into it.
Have to think what would be a good solution.
rook-ceph secretspace disabled, configMapGenerator objects missing, mon-tools complainingto Rook / CEPH config deviation