Hi everyone,
I'm currently deploying Solr 9.8.1 on Amazon EKS using the Solr Helm chart 
along with the Solr Operator. I need to modify the default jetty.xml file to 
update the Content Security Policy (CSP)—specifically, I want to remove 
'unsafe-inline' from the CSP settings.
I’ve tried the following approach:

  *   Created a ConfigMap containing my custom jetty.xml.
  *   Mounted this ConfigMap to the Solr container at the path: 
/opt/solr-9.8.1/server/etc.

However, this doesn’t seem to apply the changes as expected. I suspect the Helm 
chart or the Solr Operator might be overwriting or ignoring the mounted file.
Has anyone successfully customized jetty.xml in a similar setup? I’d really 
appreciate any guidance or best practices on how to:

  *   Properly override jetty.xml using Helm and/or the Solr Operator.
  *   Ensure the custom file is used during Solr startup.

Thanks in advance for your help!


Invesco Asset Management Limited, Company No. 949417, Firm Reference No. 122674
Invesco Fund Managers Limited, Company No. 898166, Firm Reference No. 119298
Invesco Pensions Limited, Company No. 3507379, Firm Reference No. 188249
Invesco UK Services Limited, Company No. 06649814
Invesco UK Limited, Company No. 3004959 

The first two listed companies are authorised and regulated by the Financial 
Conduct Authority. The third company is authorised by the Prudential Regulation 
Authority and regulated by the Financial Conduct Authority and the Prudential 
Regulation Authority. All companies are registered in England and Wales with 
their registered offices at Perpetual Park, Perpetual Park Drive, 
Henley-on-Thames, Oxfordshire, RG9 1HH, United Kingdom. UK Group VAT No. 245 
055 771.

****************************************************************
Confidentiality Note: The information contained in this 
message, and any attachments, may contain confidential 
and/or privileged material. It is intended solely for the 
person(s) or entity to which it is addressed. Any review, 
retransmission, dissemination, or taking of any action in
reliance upon this information by persons or entities other 
than the intended recipient(s) is prohibited. If you received 
this in error, please contact the sender and delete the 
material from any device.
****************************************************************

Reply via email to