feat: Add SINGLE_NAMESPACE_MODE support to operator #16
Conversation
Implements comprehensive single-namespace mode support to enable deployment in MPP environments where cluster-wide permissions are not available. Changes: - Add SINGLE_NAMESPACE_MODE and STORAGE_CLASS environment variables - Conditionally disable namespace watcher in single-namespace mode - Add namespace filtering to watchAgenticSessions() and watchProjectSettings() - Add StorageClass parameter to PVC creation (defaults to gp3-csi) - Add pod security contexts to Job and content service deployments - Bootstrap namespace resources on startup in single-namespace mode Resolves critical issues: - Operator watching all namespaces without filter - Namespace watcher cannot be disabled - Missing StorageClass parameter - Missing pod security contexts Resolves #2 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Jeremy Eder <jeremyeder@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
| // Get storage class from environment or use default | ||
| storageClass = os.Getenv("STORAGE_CLASS") | ||
| if storageClass == "" { | ||
| storageClass = "gp3-csi" | ||
| } | ||
|
|
There was a problem hiding this comment.
The new single‑namespace flow always assigns storageClass to "gp3-csi" when STORAGE_CLASS is unset (lines 81‑85) and ensureProjectWorkspacePVC uses that value for StorageClassName when creating the PVC. On clusters that do not define a gp3-csi storage class (GKE, kind, many on‑prem installs), the PVC create call fails with storageclass ... not found; in single‑namespace mode this error triggers the log.Fatalf at startup and the operator never comes up, whereas the previous code allowed Kubernetes to pick the default class. Consider leaving the field nil unless the environment variable is explicitly provided or verifying the class exists before defaulting.
Useful? React with 👍 / 👎.
…numbers Add sequence numbering to RFE Council workflow diagram
…ema-format feat: add new agent personas in agent schema format
Description
Implements comprehensive single-namespace mode support to enable deployment in MPP environments where cluster-wide permissions are not available.
Changes
Resolves
Closes #2
Critical Issues Addressed
Generated with Claude Code