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
Currently, the Quickstart flow includes setting up a KinD cluster, and deploying Conjur to it.
The Quickstart flow should be adjusted to allow users to supply their own cluster
... in future work it would be nice if the KinD step became optional so that users could bring their own Kubernetes cluster. The requirement being that kubectl is already setup to communicate to their cluster of choice.
Current Quickstart flow
This would change the steps of the quickstart from:
Deployed Conjur OSS to a kind cluster
...
to:
Created a KinD cluster (optional)
Deployed Conjur OSS to a Kubernetes cluster
...
The text was updated successfully, but these errors were encountered:
Currently, the Quickstart flow includes setting up a KinD cluster, and deploying Conjur to it.
The Quickstart flow should be adjusted to allow users to supply their own cluster
Current Quickstart flow
This would change the steps of the quickstart from:
to:
The text was updated successfully, but these errors were encountered: