There are end-to-end tests for Kubernetes sidecars with Conjur OSS in Kubernetes

[izgeri]

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:

• Add a "front-end" Helm install of Conjur OSS before calling the scripts developed for Issue #239.
• Add a program loop into the reusable scripts created in Issue #239 to iterate through different authenticator types.

This can use either of the following as a test platform:

• Jenkins+GKE
• Github Actions + KinD

Dependencies

• Issue #228 (cluster prep Helm chart)
• Issue #237 (Namespace prep Helm chart)
• Issue #238 (sample application deployment Helm chart)
• Issue #239 (Reusable script for deploying applications and authenticators)
• Issue #247 (Add Secrets Provider support to sample application deployment Helm chart)

Required authenticators

This CI must include testing for the following authenticator types:

• authn-k8s sidecar
• ~Secretless Broker~
• Secrets Provider init container
• ~Secrets Provider standalone (or "app") container~

DoD

• [ ] CI is running and passing for all required authenticators

[izgeri]

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

[izgeri]

Closing as a duplicate of #239