-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce the number of manager flags to the bare minimum #1122
Comments
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
This issue has been automatically closed due to the lack of recent activity. |
New flags: flag.BoolVar(&enableV1Beta1LogPipelines, "enable-v1beta1-log-pipelines", false, "Enable v1beta1 log pipelines CRD")
flag.StringVar(&certDir, "cert-dir", ".", "Webhook TLS certificate directory")
flag.StringVar(&highPriorityClassName, "high-priority-class-name", "", "High priority class name used by managed DaemonSets")
flag.StringVar(&normalPriorityClassName, "normal-priority-class-name", "", "Normal priority class name used by managed Deployments")
flag.StringVar(&fluentBitExporterImage, "fluent-bit-exporter-image", defaultFluentBitExporterImage, "Image for exporting fluent bit filesystem usage")
flag.StringVar(&fluentBitImage, "fluent-bit-image", defaultFluentBitImage, "Image for fluent-bit")
flag.StringVar(&otelCollectorImage, "otel-collector-image", defaultOTelCollectorImage, "Image for OpenTelemetry Collector")
flag.StringVar(&selfMonitorImage, "self-monitor-image", defaultSelfMonitorImage, "Image for self-monitor") |
Description
Reduce the number of manager CLI flags to the bare minimum: images, priority classes, manager namespace, feature flags (if any), etc.
Reasons
Due to historical reasons, we have been maintaining an extensive list of CLI flags, most of which we rarely use. This makes it difficult to locate important settings such as memory and CPU limits and requests, as they are often situated far from the code where they are applied. Additionally, these flags need to be passed between multiple types, complicating the process further.
Some of those flag names don't even make sense:
trace-collector-pipelines
metric-gateway-pipelines
trace-collector-pipelines
(instead of
max-log-pipelines
,max-metric-pipelines
,max-trace-pipelines
)Attachments
Release Notes
The text was updated successfully, but these errors were encountered: