Agent-level Secret references injected as run env (CRD-only, no UI)

Open
#131 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go, kubernetes

Research direction

Start by tracing the Agent CRD reference through the controller path that creates run pods, then inspect the existing E2E coverage and documentation for agent configuration. Done means an Agent-referenced Secret or ConfigMap is present as environment variables on the run pod in E2E, with the CRD-only pattern documented and no UI or prompt rendering involved.

Written by the indexing model from the issue text.

Description

An Agent may reference Secrets/ConfigMaps (envFrom-style) that the controller injects into run pods as env vars — the documented pattern for "my agent needs an API token" without putting the value in a param or a prompt. Scope fence for dev preview: CRD-level only. No UI surface, no Hub-credential integration, and secrets are never rendered into prompts.

Done when:

  • An Agent-referenced Secret appears as env on the run pod in E2E, and the pattern is documented.

Depends on: none.

Dominant language
Go
Stars
5
Forks
13
Avg merge
3d 11h
Merged PRs (30d)
41

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from konveyor/agentic-controller

All issues in konveyor/agentic-controller

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.