Issue checklist
Discussion: https://discord.com/channels/796665978481803304/1463911019272339607/1466094766784774155
Users cannot add CAs to git sync commands by means of managed fields.
The documentation is slightly confusing because the examples use a /tmp/ca-cert folder without mentioning where it is supposed to come from.
I thought it comes from customComponentsGitsync.[*].credentialsSecret but this is not the case.
The work-around is to :
- Add a new
spec.clusterConfig.extraVolumes entry that points to a secret/configmap with the CA.
- Add pod overrides to mount that volume in the init container for git sync.
- Same as above for the main container.
This overly complicated, hard to maintain and exposes too much product internals.
Issue checklist
Discussion: https://discord.com/channels/796665978481803304/1463911019272339607/1466094766784774155
Users cannot add CAs to git sync commands by means of managed fields.
The documentation is slightly confusing because the examples use a
/tmp/ca-certfolder without mentioning where it is supposed to come from.I thought it comes from
customComponentsGitsync.[*].credentialsSecretbut this is not the case.The work-around is to :
spec.clusterConfig.extraVolumesentry that points to a secret/configmap with the CA.This overly complicated, hard to maintain and exposes too much product internals.