Go Template good first issues

The `kubernetesAttributes` preset in the OpenTelemetry Collector is configured to request `container.image.tag`, but this attribute is no longer emitted by default in collector versions 0.161.0 and later due to feature gate changes. This causes a warning and the absence of image tag data. The issue proposes solutions for how the preset should handle the new plural `container.image.tags` attribute.

This issue requests the addition of dual-stack support to the OpenTelemetry Collector Helm chart. Currently, users must resort to hooks and manifest patching to configure `ipFamilies` and `ipFamilyPolicy` for the Service. The enhancement aims to directly incorporate this configuration option into the chart for easier management.

This issue requests an update to the `opentelemetry-kube-stack` Helm chart to include the latest `opentelemetry-operator` version (0.127.0). The user's deployment process relies on this update for automatic upstream release following. They are inquiring about the planned release schedule, the automation of dependency updates, and any potential blockers.

This issue requests the addition of the `metadata.labels` section to the `ClusterObservability` CRD definition. This is to ensure consistency with other CRDs in the same directory, which already include this standard metadata block. The change aims to rectify an inconsistency in the CRD manifests within the OpenTelemetry Helm charts.

CI jobs for Azure SIG are intermittently failing during `az login` authentication in the Azure environment. This issue seems to be transient, as retrying the job typically resolves the authentication problem. The error message indicates an inability to find the default Azure subscription.

The user is encountering an error when trying to use `existingPath` in a deeply nested Helm chart. The error message suggests that Helm is not correctly resolving the path to the `configMap.yaml` file, likely due to how `$.Template.BasePath` interacts with nested chart structures and the `include` function.

This is a feature request to add support for Kubernetes Network Policies to the fluentd Helm chart. Network Policies would allow users to control network traffic to and from fluentd pods for enhanced security, and would be disabled by default.

This issue requests the addition of a CI example to the operator's repository. The goal is to ensure that future releases correctly build an image for the target allocator, preventing issues like the one encountered in the 0.87.0 release.

The user wants to add the `app.kubernetes.io/version` label to Traefik's Kubernetes workload resources. This label is recommended by Kubernetes for tracking application versions and is currently missing in the Traefik Helm chart. The suggestion is to either directly add this label to the `traefik.labels` named template or allow for template logic in `deployment.labels` for user overrides.

The user encountered an issue where the `role` parameter for deploying a vector chart was case-sensitive, causing resources to not appear when using a lowercase `agent`. Changing the role to `Agent` (capitalized) resolved the problem. The user suggests making the `role` parameter case-insensitive or adding validation to error out on invalid input.

This issue proposes allowing the Traefik Helm chart to support the Gateway API in 'almost' namespaced setups. Currently, the chart enforces a strict block against this combination due to the cluster-scoped nature of GatewayClass resources. The user wants to enable scenarios where only GatewayClass is a cluster-scoped resource, while the rest of the setup remains namespaced.

The operator's metrics endpoint uses self-signed certificates that are not trusted by clients, requiring `insecureSkipVerify: true` in ServiceMonitor configurations. The Helm chart prevents mounting custom TLS certificates, and the user suggests adding support for extra volumes or integrating with cert-manager for a more robust solution.

The user wants to expose the GraphQL API of the GUAC chart via an Ingress so that the visualizer can access it. Currently, the GraphQL API is not accessible externally, preventing the visualizer from functioning correctly.

This issue proposes adding support for custom annotations to the GUAC Helm chart. Currently, users must manually patch Kubernetes resources to add annotations, and this feature would allow them to specify annotations that apply to all provisioned resources like deployments, services, and pods directly through the Helm chart.

This issue proposes adding support for `podAnnotations` to the GUAC Helm chart. This would allow users to specify annotations that should be applied to all pods created by the chart, which is useful for various integration and management purposes.

This issue requests the addition of a feature to the Helm chart for Guacamole services, allowing users to specify annotations directly for pods. Currently, only deployment/statefulset annotations are supported, and the lack of pod-specific annotation configuration necessitates less ideal patching methods.

This issue reports a bug in the `opentelemetry-kube-stack` Helm chart where attributes defined in `resourceAttributes` within `values.yaml` are not being correctly passed to the OpenTelemetry Collector's resource attributes. Instead, the collector is incorrectly reporting `k8s.cluster.name=unknown_k8s_cluster`.

This issue highlights a discrepancy in the documentation regarding Nexus plugin configuration. The administration documentation (`plugins.md`) lacks specific details about Nexus, while the external services guide (`external-services.md`) covers its project-level configuration. The task is to investigate if this is a documentation oversight or actual console behavior and update the administration documentation accordingly.

The issue describes a bug where setting the Prometheus storage size to a value like '10GB' fails during the apply phase with an invalid format error. The expected behavior is for the configuration to be validated earlier by `furyctl` to prevent apply-time failures.

The `loki.process.cluster_events` component in the k8s-monitoring Helm chart incorrectly sets and then removes the 'node' label for Node events. This is due to a conflict where the 'node' label is added and then subsequently removed when it's also configured as structured metadata, leading to confusion and unintended behavior.

This issue proposes adding Quay.io as a secondary OCI registry for publishing Helm charts, in addition to the existing GitHub Container Registry (GHCR). This change aims to improve availability and reduce reliance on a single registry by mirroring practices of other CNCF projects. The implementation involves creating a Quay.io robot account, storing credentials as secrets, updating release workflows to push to Quay.io, and updating documentation to reflect the new target.

The opentelemetry-operator chart hardcodes the metrics server bind address to IPv4 (0.0.0.0), making it unreachable on IPv6 or dual-stack clusters. This prevents metrics scraping without any explicit error. The proposed solution is to remove the host from the bind address, allowing Go to default to dual-stack listening.

This issue proposes removing the `required` keyword from the `values.schema.json` file for the opentelemetry-operator Helm chart. The current use of `required` causes validation errors in editors, even though Helm itself handles value merging correctly. Removing `required` would improve the user experience in editors without significantly impacting validation, as required fields can be enforced in chart templates.

The user is reporting that the `insecure: true` parameter in Loki's AWS configuration is not preventing TLS certificate verification errors when connecting to a MinIO instance. Despite setting it to true, Loki is still encountering an 'x509: certificate signed by unknown authority' error, indicating a potential issue with how the `insecure` flag is being interpreted or applied in the AWS client configuration.

This issue requires aligning the current repository with the established llm-d organization's repository template. It involves adding various governance documents, linting configurations, GitHub metadata files, and CI/CD workflow files to ensure consistency across projects.

The `kubelet_scrape_configs.yaml` example file is missing from the packaged `opentelemetry-kube-stack` Helm chart. This prevents users from configuring the chart to use this specific example configuration out-of-the-box, as the referenced file is not included in the downloaded chart package.

Argo CD is unable to pull the OpenTelemetry Collector Helm chart, returning a TLS error and potentially a 404 from the repository URL. The user suspects the issue might be due to GitHub Pages not being properly configured for the repository, preventing the `repoURL` from resolving correctly. They suggest adding a basic content file to the `gh-pages` branch as a potential fix.

Users are encountering a deprecation warning related to the legacy `service.telemetry.resource` inline map format in the OpenTelemetry Collector Helm chart. This warning appears during pod startup and, while not currently causing functional issues, is concerning for production environments. The user is requesting a fix within the Helm chart to address this.

The Traefik Helm chart version 39.0.9 incorrectly defaults the PodDisruptionBudget API version to `policy/v1beta1` when using `helm template`. This occurs because the chart relies on `.Capabilities.APIVersions.Has`, which is unavailable during templating without a cluster context. The user suggests using `.Capabilities.KubeVersion.GitVersion` or defaulting to `policy/v1` as `policy/v1beta1` is deprecated in supported Kubernetes versions.

When deploying Valkey with a single replica and persistence enabled, the default rolling update strategy causes deployment failures. This is because the old pod retains the persistent volume, preventing the new pod from starting. The issue suggests either changing the deployment strategy to 'recreate' or using a StatefulSet when persistence is enabled.