Ephemeral Environment

Market insights

Stack

Apply

Upload your CV — we will connect you with the employer directly through our pool.

Description

Ephemeral Environment Really looking for advice or tips on how others have handled this setup. We need to spin up ephemeral environments whenever a release PR is opened (specifically from UAT → master). Our goal is to run end to end tests in these environments as part of release validation, plus also support manual testing and nightly runs. And perform cleanup after tests. Our current stack looks like this: Jenkins Kubernetes ArgoCD Kustomize Gitea One major constraint is that I don’t have full cluster access we’re restricted to a single namespace only. Has anyone implemented something similar under these limitations? How did you structure your ephemeral environments, especially with ArgoCD + limited Kubernetes permissions? Any patterns, tooling approaches, or lessons learned would really help. [link] [handle]

Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.