You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CI automation is required to perform E2E testing the deployment of Kubernetes authenticator sidecars using Conjur OSS that has been deployed via Conjur OSS Helm chart.
Almost all of the scripting to support this CI is covered in Issue #239. There will be a small, incremental amount of scripting to:
izgeri
changed the title
There are end-to-end tests for Kubernetes sidecars with Conjur OSS
There are end-to-end tests for Kubernetes sidecars with Conjur OSS in Kubernetes
Mar 15, 2021
Is #247 really required for this? I'm wondering if we can prioritize getting this running e2e without it, which would mean e2e tests with authn-k8s client sidecar
getting the e2e flow running with the SP subchart could be a follow-on activity
Overview
CI automation is required to perform E2E testing the deployment of Kubernetes authenticator sidecars using Conjur OSS that has been deployed via Conjur OSS Helm chart.
Almost all of the scripting to support this CI is covered in Issue #239. There will be a small, incremental amount of scripting to:
This can use either of the following as a test platform:
Dependencies
Required authenticators
This CI must include testing for the following authenticator types:
Secretless BrokerSecrets Provider standalone (or "app") containerDoD
The text was updated successfully, but these errors were encountered: