Skip to content

feat(kubernetes): add Secret resource with Redacted data - #1509

Open
connyay wants to merge 1 commit into
alchemy-run:mainfrom
connyay:k8s-secret
Open

feat(kubernetes): add Secret resource with Redacted data#1509
connyay wants to merge 1 commit into
alchemy-run:mainfrom
connyay:k8s-secret

Conversation

@connyay

@connyay connyay commented Sep 5, 2026

Copy link
Copy Markdown
  • Kubernetes.Secret applies a v1/Secret via server-side apply; values stay Redacted through plan and state and are base64-encoded only at the API edge
  • hoist the shared isNotFound helper into internal/client.ts
  • cover the Secret lifecycle in the gated Deployment E2E suite

- `Kubernetes.Secret` applies a v1/Secret via server-side apply; values stay
  `Redacted` through plan and state and are base64-encoded only at the API edge
- hoist the shared `isNotFound` helper into `internal/client.ts`
- cover the Secret lifecycle in the gated Deployment E2E suite
@isakgustavsen

isakgustavsen commented Sep 8, 2026

Copy link
Copy Markdown

Could this be integrated with pr #1502? It should cover what you need in terms of importing secrets, and if there's anything missing it we could look at it now

@connyay

connyay commented Sep 8, 2026

Copy link
Copy Markdown
Author

Could this be integrated with pr #1502? It should cover what you need in terms of importing secrets, and if there's anything missing it we could look at it now

I don't fully grok what you mean by integrating these PRs. They are related, but not directly overlapping. I think the best would be maybe some doc/example improvements showing how they could be used together. Could be added to either PR after the other one lands.

Did you have something specific in mind?

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.

2 participants