Browsertrix install fails on OpenShift

Help! Browsertrix
1

Hello,

I tried to install Browsertrix-cloud on OpenShift and ran into multiple errors.

  • Error: rendered manifests contain a resource that already exists. Unable to continue with install: Namespace “browsertrix-cloud” in namespace “” exists and cannot be imported into the current release: invalid ownership metadata;
  • label validation error: missing key “app.kubernetes.io/managed-by”: must be set to “Helm”;
  • annotation validation error: missing key “meta.helm.sh/release-namespace”: must be set to “default”.

Any help to fix these helm issues would be appreciated.

Also is there a way to disable the creation of a namespace in the installer? I already have a namespace for the user who wants to use this.

2

Unfortunately, we don’t currently have support for OpenShift, as we don’t have an OpenShift environment in which to test. It’ll likely require some effort, as there’s additional security requirements and other restrictions (such as the namespace restrictions you mention).

I’ve opened a GH issue to keep track of this here: Supporting OpenShift · Issue #1090 · webrecorder/browsertrix-cloud · GitHub