Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Image Puller Operator is failing on large clusters #21899

Closed
Tracked by #21925
ibuziuk opened this issue Dec 22, 2022 · 1 comment
Closed
Tracked by #21925

Image Puller Operator is failing on large clusters #21899

ibuziuk opened this issue Dec 22, 2022 · 1 comment
Labels
area/image-puller Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Milestone
7.60

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Dec 22, 2022

Describe the bug

Image Puller Operator is failing on large clusters after installation

Che version

7.58@latest

Steps to reproduce

  1. Setup a cluster with 3K+ namespaces
  2. install the image puller operator
  3. ERROR: operator pod keeps restarting

Expected behavior

Image puller operator installs without problems on clusters with 5K namespaces

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Amazon

Eclipse Che Logs

container logs


I1220 11:33:26.732542 1 trace.go:205] Trace[1120032457]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.3/tools/cache/reflector.go:167 (20-Dec-2022 11:32:25.374) (total time: 61357ms):
Trace[1120032457]: [1m1.357796456s] [1m1.357796456s] END
E1220 11:33:26.732564 1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.3/tools/cache/reflector.go:167: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 329; INTERNAL_ERROR


### Additional context

_No response_
@ibuziuk ibuziuk added kind/bug Outline of a bug - must adhere to the bug report template. sprint/next severity/P1 Has a major impact to usage or development of the system. area/image-puller Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller labels Dec 22, 2022
@ibuziuk ibuziuk changed the title Image Puller Operator is failing on large clsuters Image Puller Operator is failing on large clusters Dec 22, 2022
@ibuziuk ibuziuk mentioned this issue Jan 10, 2023
Closed
60 tasks
@tolusha tolusha mentioned this issue Jan 16, 2023
Merged
@tolusha tolusha closed this as completed Jan 18, 2023
@tolusha
Copy link
Contributor

tolusha commented Jan 18, 2023 •
edited
Loading

Fixed for Kubernetes Image Puller 1.0.4

@tolusha tolusha added this to the 7.60 milestone Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/image-puller Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Milestone
7.60
Development

No branches or pull requests
2 participants
@ibuziuk @tolusha