Ephemeral Environment

Аналитика рынка

Стек

Откликнуться

Загрузите резюме — мы свяжем вас с работодателем напрямую через нашу базу.

Описание

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]

Контакты работодателя (email/phone/telegram) скрыты из публичного превью — отправьте резюме, чтобы мы связали вас напрямую.