federation-reader/sender missing data volume

[ApolloDS]

Hello
I like your synapse helm chart very much.
But I cannot start it, I always get an error on the federation-sender and federation-reader pods:

("Error accessing file '/data/server_name.signing.key'", ('signing_key',))

In the deployment_federation_sender.yaml and deployment_federation_reader.yaml I see that you're not mounting the data volume.
I don't know how the pods above should start then.

[halkeye]

So its been a long while since I set this up... Looking at https://github.com/halkeye/helmfile/blob/master/namespaces/matrix/synapse-secret.yaml#L34 it looks like I copied my signing key into the extra data files, then reference it in the config https://github.com/halkeye/helmfile/blob/master/namespaces/matrix/synapse.yaml#L29

I'm open to PRs that don't break my setup

its late here, but if i get a chance tomorrow i'll poke at it more.

[ApolloDS]

Hi Gavin,
Whow you're fast in reply, thank you very much :-)
As a workaround I will try the same for now and put the signing key into the config.

Since I'm new to PR I need some time to study and how to proceed.

Thank you, I appreciate your work on the project!

[halkeye]

the quicker I reply the more likely i'm going to reply, so I try to do so when I can.

My guess is I was trying to make this setup diskless so it could scale easier.

I'm thinking one of two items:

1. Make signing key a top level config and make it manditory
2. Disable the federation replicasets so it just uses the single processs

[ApolloDS]

I would prefer single process but it's up to you then :-)

[joshuacox]

Just ran into this same issue, it certainly seems the chart is broken out of the box till this is resolved. Either route sounds acceptable,

1. Is there an example we can document for making a signing key a top level config?
2. in the case of turning off federation, it is not clear how to implement, can this be done by simply altering a values.yaml?

[halkeye]

I run 3 processes, one main, one reader, one writer. I don't know if its needed anymore, but i had trouble joining large rooms in the past.

I'm not planning on making any changes personally, the chart works for me. But I'm open to anything that doesn't majorly break my own stuff or other peoples stuff. I know it sounds harsh, but maintaing charts for scenarios i don't use is a lot of extra work for me.

[joshuacox]

Don't change anything that you are doing, but maybe document what needs to be done to make the chart work for others?

[artichoked1]

Hi, I'm also having this problem. Is there a fix for this yet?

[halkeye]

Nobody has submitted anything yet. As said, I'm open to PRs that don't break my own setup.
there's lots of other charts though.

[artichoked1]

i just forked the repository to mount the federation sender and reader to the same pvc the main deployment uses. I'll let you know how it goes...