Skip to content

fix(secrets): regenerate SealedSecrets with current controller key#6

Closed
justgithubaccount wants to merge 1 commit into
mainfrom
fix/update-sealed-secrets
Closed

fix(secrets): regenerate SealedSecrets with current controller key#6
justgithubaccount wants to merge 1 commit into
mainfrom
fix/update-sealed-secrets

Conversation

@justgithubaccount

Copy link
Copy Markdown
Owner

Summary

Regenerate sealed secrets for chat-api with the current SealedSecrets controller key.

Previous secrets were encrypted with a different controller key and could not be decrypted.

Changes

  • chat-openrouter (namespace: chat-api)

    • OPENROUTER_API_KEY - OpenRouter LLM API
    • OPENAI_API_KEY - OpenAI API
    • HF_TOKEN - HuggingFace token
  • chat-github (namespace: argocd)

    • url, username, password - GitHub credentials for Argo Image Updater
    • Label: argocd.argoproj.io/secret-type: repository

Test plan

  • Merge PR
  • Wait for ArgoCD sync
  • Verify SealedSecrets unseal successfully
  • Check chat-api pods start correctly

🤖 Generated with Claude Code

Regenerate sealed secrets for chat-api:
- chat-openrouter: OPENROUTER_API_KEY, OPENAI_API_KEY, HF_TOKEN
- chat-github: ArgoCD repository credentials for Image Updater

Previous secrets were encrypted with different controller key.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@justgithubaccount justgithubaccount deleted the fix/update-sealed-secrets branch December 6, 2025 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant