Morning Craig, I've put a potential fix into the couchbase-partners repos.  Mind checking if it's working any better now?  I've not bumped the revision yet so you'll need to uninstall and reinstall the chart.

Hey Simon Murray,  I switched my cluster over to OpenShift 4.0 for another demo,  but the below command worked

helm install couchbase/couchbase-operator

and we can see the correct resources created.  When I try and deploy the cluster through helm I am getting a Context Deadline Exceeded as shown by this error from the operator log but no errors thrown by helm

error msg="Cluster setup failed: context deadline exceeded: Pod Creation error - error creating pod cbdemo-couchbase-cluster-0000" cluster-name=cbdemo-couchbase-cluster module=cluster

but was able to deploy by hand.

cb-example-0000                                                   1/1     Running   0          8m22s

cb-example-0001                                                   1/1     Running   0          5m59s

cb-example-0002                                                   1/1     Running   0          3m39s

tailored-umbrellabird-couchbase-admission-controller-75d56gk5x6   1/1     Running   0          23m

tailored-umbrellabird-couchbase-operator-57c45fcff8-jll6g         1/1     Running   0          23m

I will continue to look into this.

I'd not bother, RHEL is bloated and takes an age to download.  Our timeouts default to 5 minutes which is your issue.  You can override the operator CLI parameters and set it to something bigger e.g. 15m.  See https://docs.couchbase.com/operator/1.2/operator-config.html#command-line-arguments

This wasn't part of GA directly, but was already pushed to helm. Simon Murray is going to look at a couple more things here.

• Perms
• Version

After this Craig Kovar, we'd like you to verify further. Look out for the ping from Simon Murray.

Matt Ingenthron sure thing.  Just let me know and I can do some validation.

Follow ups in K8S-967

Craig Kovar: Updates are pushed to the repo, can you help validate?

https://github.com/couchbase-partners/helm-charts

Matt Ingenthron and Simon Murray

Hey,  I was testing this and did notice an issue with deploying on OpenShift 4.1.  Here are the steps I tested in EKS and OpenShift

EKS

helm install --values myvalues.yaml couchbase/couchbase-operator --namespace cbtesting --name cbtesting

Passed  (myvalues.yaml as below)

couchbaseOperator:

  commandArgs:

    create-crd: true

    pod-create-timeout: 10m

Then I ran

helm install --set couchbaseCluster.version=enterprise-5.5.3 --name cbcluster couchbase/couchbase-cluster --namespace cbtesting

Passed.   I also tried downgrading which the Admission Controller correctly caught as that is not supported.

OpenShift

oc new-project cbtesting

helm install --values myvalues.yaml couchbase/couchbase-operator --namespace cbtesting --name cbtesting

Passed

However,  when I now try to run

helm install --name cbcluster couchbase/couchbase-cluster --namespace cbtesting

Fail with the following error:

Error: validation failed: error validating "": error validating data: ValidationError(CouchbaseCluster.spec): unknown field "securityContext" in com.couchbase.v1.CouchbaseCluster.spec

I know OpenShift 4.1 is still in DP so this may not be a valid test

So while that field is correctly named, in the right place in the spec it's not in the CRD schema.  I'm assuming that helm is now validating what's in the chart matches what's advertised.  While technically this is ostensibly a packaging change to add a new CRD, it's also a point release, so we cannot fix until 1.2.1.

See comments

After some digging the change that caused the error was fixed in 2.14.1, so please upgrade helm/tiller and it will go away

As stated previously this is a bug in Helm that has been reverted, so closing... for now

Summary: Due to a known issue in Helm 2.14.0, attempting to install the Couchbase cluster would result in validation errors, even for correctly-configured charts.

Workaround: Use a version of Helm other than 2.14.0.