Thousands of "Skipping cache lookup" messages

[gaelcrova]

Hi,

We are using the k8s plugin inside an ansible based openshift operator.

I detected that each usage of k8s plugin, to search, create, udpate, etc is always starting by lots of calls that are visible as following:

2020-09-25T15:15:08.179+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/api/v1","Verb":"get","APIPrefix":"","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:08.303+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/apiregistration.k8s.io/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:08.422+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/apps/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:08.542+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/authentication.k8s.io/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:08.661+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/authorization.k8s.io/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:08.780+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/autoscaling/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:08.900+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/batch/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
2020-09-25T15:15:09.020+0200	INFO	proxy	Skipping cache lookup	{"resource": {"IsResourceRequest":false,"Path":"/apis/networking.k8s.io/v1","Verb":"get","APIPrefix":"apis","APIGroup":"","APIVersion":"","Namespace":"","Resource":"","Subresource":"","Name":"","Parts":null}}
etc etc

When operator is located on cluster, this is not taking too long but for local development, it always takes from 3 to 10 seconds to complete for each k8s usage.
I tested the kubectl call directly through shell plugin and it's working faster.

Is there a way to configure the client from k8s plugin, or operator in order to fix this and improve operator performances?

Thanks
Gael

[gaelcrova]

BTW I tried to disable fact gathering by adding various environment variables or command line parameters. But it might be related to this defect operator-framework/operator-sdk#2358 fixed by this PR operator-framework/operator-sdk#3933

Then I'll wait for new release of operator and see

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.