-
Story
-
Resolution: Unresolved
-
Major
-
None
-
Quality / Stability / Reliability
-
2
-
False
-
-
False
-
NEW
-
NEW
-
Enhancement
-
-
-
Logging - Sprint 277
Story
- As an administrator of ClusterLogForwarder,
I want kube-api caching to always be enbled
So the requests to the API server are minimized - As an administrator of ClusterLogForwarder,
I want to configure the collector pods rollout strategy
So the requests to the API server are minimized
Acceptance Criteria
- Verify the kube-api cache configuration is enabled when application or infrastructure container sources are spec'd
- Verify the daemonset specifies a maxUnavailable of 100% when not spec'd on ClusterLogForwarder
- Verify the daemonset specifies a maxUnavailable equal to the spec'd value on ClusterLogForwarder when spec'd
- Update upstream and feature docs
Notes & Questions
- Are there available collector metrics to identify improvements to submitting the api requests?
- informs
-
LOG-7570 Test kubeapi at scale
-
- To Do
-
- is caused by
-
LOG-7342 [release-6.2]Backport enabling kube-apiserver caching and maxUnavailable rollout strategy
-
- New
-
-
LOG-7597 The collectors (Vector) restart impacts in the KubeAPI making it unavailable (GA)
-
- New
-
-
LOG-7196 The collectors (Vector) restart impacts in the KubeAPI making it unavailable
-
- Closed
-
- links to
(1 links to)