Travis Nielsen

The secret is in the format: ``` data: cinder: QVFCNUh3NWpXNzc5SnhBQVlsSHhyMTh1a3l0YllsazlJT2VzSVE9PQ== ``` Where in this example `cinder` is the clientID and the blob is the base64-encoded keyring. What more info are...

So you are creating the secrets used by the [storage class](https://github.com/rook/rook/blob/master/deploy/examples/csi/rbd/storageclass.yaml#L67-L72)? Those secrets have "userID" and "userKey" entries such as: ``` data: userID: Y3NpLXJiZC1ub2Rl userKey: QVFDd0VRMWpmaXo0TmhBQW9SWjhIYzh5blpBcWs1a1lFeS80Y3c9PQ== ``` What if the...

Sure, that seems simple enough just to write two more keys to the same secret [here](https://github.com/rook/rook/blob/master/pkg/operator/ceph/client/controller.go#L259).

The CRDs are updated by the helm chart during upgrade. There is discussion in #4037 and #6556 about the approach rook has implemented. Perhaps you hit some other issue than...

This doc update shouldn't be necessary, but please open an issue if you're still seeing the CRDs not updating.

To build on the new platform will certainly require some updates to the makefiles. For example, in the main Makefile there is a [PLATFORMS_TO_BUILD_FOR](https://github.com/rook/rook/blob/master/Makefile#L72), which later feeds into the [GO_STATIC_PACKAGES](https://github.com/rook/rook/blob/master/Makefile#L97).

Great to hear you have it building now. So if #10967 is updated with that change, it would just need to also disable the helm build on riscv64.

@ruckc Did you find a workaround? Not sure what we could do here other than document a workaround.

@taxilian Thanks for the verification!

#10190 is in progress