Mukul SharmaandClaude Opus 5
73ddfd8534
Gitea refused every push notification with "webhook can only call allowed HTTP servers": toolshed builds an app's webhook target from the hostname the dashboard was browsed on, so an app registered through the public URL gets a public target, and this cluster's allowlist only permitted private ranges. Adding that one hostname rather than reverting to the homelab's "*". The difference matters: "*" would also permit the node metadata server, which is why it was narrowed in the first place. This permits exactly one host, our own load balancer. It is a stopgap and labelled as one in the file. The callback now hairpins out to the load balancer and back in, which is precisely what the cluster-DNS rule exists to avoid. The real fix is a configurable webhook base URL in toolshed pointing at toolshed-api.toolshed.svc.cluster.local:8080; this entry should be removed when that lands. Verified in the render: the value reaches Gitea's inline config, and Recreate, standard-rwo, sqlite and disabled registration are untouched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N
devops-infra-helm-charts
This branch (main) is part of the restructuring process for the gcp-devops-admin repository, aimed at organizing helmcharts of all infrastructure tools and their corresponding value files. The purpose of this repository is to centralize and manage these resources efficiently.
Directory Structure
helm-templates
This directory is intended for caching or forking helm charts locally. If there's a need to modify or customize any helm chart, it can be done here. Otherwise, the charts will be used directly from the provider.
helm-overrides
The helm-overrides folder stores custom values files for helm charts. These files can be used to override the default values provided by the helm charts, whether they are forked or used directly from the provider.
cluster_name
Each tool within the repository may have different values based on the specific clusters. This directory is used to manage configurations and values tailored to different clusters.
manifests
The manifests directory contains manifest files that need to be applied only once. Examples include service-to-service configurations, storage classes, and any other manifest-related files necessary for the operation of the infrastructure tools.
Additional Notes
Please ensure that all changes made to this branch align with the restructuring objectives and follow the best practices for managing helm charts and infrastructure-related configurations.
For any questions or concerns, please reach out to the designated repository maintainers.