Added sidecar #386
Reference in New Issue
Block a user
No description provided.
Delete Branch "sidecar"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the change
Be able to add additional containers (sidecars) to gitea pod. In my case I will use it for backup purpose as I can't create backups from its volume directly.
Benefits
Allow users to add additional containers on their behalf
Possible drawbacks
None. It won't render until
.Values.sidecars
has a values that renders more than a newlineApplicable issues
None. It won't render until
.Values.sidecars
has a values that renders more than a newline.Checklist
values.yaml
and added to theREADME.md
using readme-generator-for-helmREADME.md
Thanks!
I don't mind this change. Some comments:
sidecar
instead ofsidecars
- it is uncommon to use the plural form even if you can use list notation for a config itemvalues.yml
and maybe in the README to describe it's purpose and maybe add a short example. If you already have one yourself, maybe that's not much of a big deal for you? I.e. just showcasing your config as an example.All containers should take the security context into account.
@pat-s the chart is already using mostly plurals (extraVolumes, extraContainerVolumeMounts, ...).
this is also in accordance with k8s resources (example, a pod containers, initContainers, volumes, etc)
ref: https://gitea.com/gitea/helm-chart/src/branch/main/values.yaml#L224
@jouve OK I see, I've also found other charts that use the plural here. In general it looks like that it's more a wild mix than a clear consistency overall wether to use singular or plural.
There are several use cases. Imagine a container taking care of changes in a configuration file and sends requests via Gitea API to configure Gitea. Or another container that is tightly coupled with Gitea and receives a webhook to do something (not CI) and it is not necessary to have that endpoint accessible outside of Gitea.
Oh I was not questioning the use cases, just discussing singular/plural notation.
We still miss the sec context point you raised, Justus. Not sure though if OP is still active here.
@JSchlarb do you still want to continue this Pull Request? There are some unresolved topics and a conflict that should be resolved.
I am closing here for now as the PR seems stale, please comment if it should be reopened.
Pull request closed