This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@JaydipGabani Could you share more about the scope / audience of this doc? For example, is it for users or developers (or both)? I ask because I found a handful of flags that aren't exposed as chart values and are not applied to the underlying deployments:

--log-level-key
--log-level-encoder
--metrics-addr
--host
--cert-dir
--enable-pprof
--pprof-port
--cert-service-name
--api-cache-dir
--debug-use-fake-pod
--otlp-endpoint
--otlp-metric-interval
--stackdriver-only-when-available
--stackdriver-metric-interval
--readiness-retries
--disable-enforcementaction-validation
--client-ca-name
--client-cn-name

@ianstanton I think this is for both. I recall someone not being able to find information about a flag and incompatible behavior because it was hidden in documentation as warning for two imcompatible flags. As oppose to that, if all the flags are in one place then it might be useful to get the information on what the flag does easily. And then if users want to know more, they can read through respective feature documentation.

@JaydipGabani Cool, thanks for clarifying! So any flag could be passed when running the binary, but I think we should also add those missing flags I mentioned in #3358 (comment) to the chart as part of this unless there's a reason they're not exposed.

My thought is users should be able to set any available flag via the helm chart as well, and it doesn't look like they can at the moment. We could add the missing flags as individual helm values, or add a extraArgs section where they could be passed in and applied to their respective deployments. WDYT?

I can keep this simple for now and add a docs page with a table for each flag.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.