helm (Go) fails TLS through Cortex proxy on macOS — CA not in System keychain

已关闭
  • 哪里不对？
#1,348 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #1357 来自 @huang195 —— 已合并
  • #1358 来自 @huang195 —— 已合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
18/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, helm, macos, shell
领域
cli, devops, security

调研方向

The payload names no source files, only install.sh and the agentop CLI, plus the ~/.cortex/ca/bundle.crt path the env vars point at. Start by reading how install.sh and agentop set HTTPS_PROXY and the CA variables, and reproduce with helm repo update behind the proxy. Done means a maintainer has chosen between the keychain change, a proxy bypass, or another supported CA path, and the chosen approach is implemented.

由索引模型根据 Issue 内容生成。

描述

Summary

Go-based CLI tools (here: helm) fail TLS verification when their traffic is routed through the Cortex proxy on macOS, because they do not consult the *_CA_BUNDLE / SSL_CERT_FILE environment variables Cortex sets, and the Cortex bridge CA is not in the macOS System keychain that Go verifies against.

Filed as a blank issue per the Laptop-feedback template's guidance ("a Helm or platform problem — open a blank issue instead"). Raised with a Cortex maintainer, who suggested filing with details.

Where it fails

On the local machine, not the cluster. A Python CLI shells out to the local helm binary, which fetches public Helm chart repos (e.g. https://llm-d-incubation.github.io/llm-d-infra/) over the internet via the local Cortex proxy. The cluster API path (kubectl/oc) is unaffected.

Symptom

helm repo update llmDInfra
Get "https://llm-d-incubation.github.io/llm-d-infra/index.yaml":
  tls: failed to verify certificate: x509: certificate signed by unknown authority

Reproduces both inside the CLI and when helm repo update is run standalone in the same shell.

Works vs. doesn't

  • curl -sSI https://llm-d-incubation.github.io/llm-d-infra/index.yaml → HTTP/2 200 (curl honors CURL_CA_BUNDLE).
  • helm repo update → TLS failure.

Root cause (hypothesis)

Cortex sets HTTPS_PROXY=http://127.0.0.1:47600 plus CURL_CA_BUNDLE / REQUESTS_CA_BUNDLE / SSL_CERT_FILE → ~/.cortex/ca/bundle.crt (valid, 129 certs). curl- and Python-based tools trust the bridge CA via those vars. Go-based tools (helm, and likely oc/kubectl plugins, gh in some builds) do not read *_CA_BUNDLE, and on macOS Go verifies against the System keychain rather than SSL_CERT_FILE — where the Cortex CA is absent. So any Go tool doing outbound TLS through the proxy fails.

Options considered (none applied)

  1. Add the Cortex CA to the macOS System keychain (security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ~/.cortex/ca/bundle.crt) — fixes all Go tools, but is a sudo, machine-wide trust change.
  2. Bypass the proxy for the helm step (env -u HTTPS_PROXY ...) — loses Cortex token visibility for those calls.

Questions

  1. Is adding the bridge CA to the macOS System keychain the intended/supported fix for Go tools, and if so should install.sh / agentop do it (or offer it)?
  2. Is there a supported way for Go/helm to pick up the CA without a system-wide keychain change?
  3. Is per-tool proxy bypass acceptable to Cortex's accounting model?

Environment

  • OS: Darwin arm64
  • Cortex: agentop v0.8.0
  • agentop service status: healthy; TLS bridge CA ~/.cortex/ca/ca.crt (minted 2026-09-14), env vars point at ~/.cortex/ca/bundle.crt
  • helm: v4.2.3+g43e8b7f (Go go1.25.1 darwin/arm64)
  • Agent: Claude Code, claude-opus-4-8
主要语言
Go
星标
23
派生
44
平均合并
16 小时 8 分钟
30 天内合并 PR
234

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

rossoctl/cortex 的其他 Issue

查看 rossoctl/cortex 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。