OpenEverest now lets you bring your own bootstrap credentials when creating an instance

OpenEverest now supports seeding an engine’s bootstrap credentials from a user-provided Kubernetes Secret when creating an instance.

Previously, credentials were always auto-generated by the provider, which worked for green-field deployments but made it hard to rotate to known passwords, integrate with existing credential stores, or meet compliance requirements that mandate externally managed secrets.

With Instance.spec.userSecretRef, you name a Secret in the same namespace and OpenEverest passes it through to the engine at creation time. The reference is immutable once set — it only applies at creation, so a later change cannot accidentally rotate credentials on a running instance. The provider still validates the Secret exists and contains the expected keys before proceeding.

This is available in OpenEverest v2.0.0 Developer Preview 3.