Kubernetes Admission Controller logging

We have couchbase 6.6.0 running in kubernetes with the autonomous operator.

The Admission Controller logs to err and spams if full of following messages. The same message is printed multiple times per second. The admission controller is couchbase/admission-controller:2.0.3

Few questions:

  1. Is this typical behaviour?
  2. How do I turn this logging off? Any values on stderrthreshold or v does not seem to help

I1203 22:37:09.160066 1 admission.go:296] couchbase-operator-admission 2.0.3 (build 115) (release)
I1203 22:37:10.344309 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:10.348778 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:10.939366 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:10.943203 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:11.539409 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:11.542789 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:11.939006 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:11.942200 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:12.539095 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:12.542345 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:13.139289 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:13.143822 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:13.539504 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:13.542824 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:14.138915 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:14.142281 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:14.739033 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:14.742571 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:15.138898 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:15.142680 1 admission.go:137] Validating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster
I1203 22:37:15.739525 1 admission.go:185] Mutating resource: UPDATE couchbase.com/v2, Kind=CouchbaseCluster production/app-couchbase-cluster

Those are info level logs and cannot be disabled, unless you want to remove -logtostderr altogether :wink: However this is critical to being able to support the product as it proves it’s working or not, so shouldn’t be disabled.

The DAC is called for every update to any Couchbase resource, as such this will fire on every status update. Operator 2.1 fixes quite a few unnecessary updates caused by non-deterministic ordering and the like.

Shouldn’t it only log errors? Or log once per minute that there were 100 successful calls?

And what is being updated multiple times per second???

Hi @Teppo_Kauppinen

I understand your concerns over the logging, but that’s by design. I will recommend you read more about using admission controller documentation on Kubernetes.io, which explains how it works. As @simon.murray explained, those info-level logs are critical to support the product and cannot get turned off. There is a reason why this product is called “Autonomous” :slight_smile: The operator is always running behind the scene monitoring Couchbase resources.

Read more about Couchbase Admission Controller.

We have made some enhancements and bug-fixes for the admission-controller in the upcoming Couchbase Autonomous Operator (CAO) 2.1 release. I recommend upgrading to CAO 2.1 release when it gets released in the next couple of weeks.

I hope that helps!