Data and AI struggles

1,730 problems · 342 companies

DevOps and infra

Kubernetes is too complex to run well

8 posts from 8 people7d activeFading, +0 this week

Posts per day

Posts per day8 posts, Sep 7 to Nov 9

The posts behind it

GitHub issuesBerriAI/litellm · Const-antineOct 19

[Bug]: generic_api logger drops a full-queue batch when the logging worker times it out

### Description When the generic API logger's queue reaches `batch_size`, the success (or failure) callback that added the last event sends the batch itself and waits for it. That callback runs inside the logging worker, which cancels any callback after...

3 reactions
GitHub issuesmlflow/mlflow · DrTuupOct 19

[FR] Add optional autoscaling capability to helm chart

...them idle is expensive in terms of CPU and Memory requests. > #### Why is it currently difficult to achieve this use case? Deploy an HPA next to the MLFlow deployment is possible, but keeping this matching such as labelselectors on two places can become quite a headache....

3 replies
GitHub issuesapache/airflow · devgonvarunOct 16

Multiple Dag Processors via Helm Chart

### Under which category would you file this issue? Helm chart ### Apache Airflow version 3.3.2 ### What happened and how to reproduce it? The current values in the helm chart support setting replicas for a single dag processor applying the same configurations across all...

GitHub issuesBerriAI/litellm · yhtMinceraft1010XOct 14

[Bug]: Admin UI settings cannot be edited if STORE_MODEL_IN_DB is false

### Description Action: As a proxy admin, change UI Settings, Internal User Page Visibility and Team Admin editable fields under Admin Settings, regardless of whether STORE_MODEL_IN_DB is true or false Expected Result: Settings can be changed Actual Result: Setting changes are...

1 replies
GitHub issuesapache/airflow · bcanvuralOct 12

Helm chart: default Celery worker Service selects KubernetesExecutor task pods when running multiple executors

### Under which category would you file this issue? Helm chart ### Apache Airflow version 3.3.0 ### What happened and how to reproduce it? With an executor string that contains both `KubernetesExecutor` and `CeleryExecutor`, the chart's headless worker Service (` -worker`, port...

2 replies
Stack OverflowStack Overflow [kubernetes] · DocSep 22

What's an elegant way to check prerequisites in a Helm chart - and fail the installation, if it's not met?

For adding initContainers and env variables to K8s deployments, I wrote a configurable webhook which relies on cert-manager for cluster-internal self-generated certificates. For an easy installation on Kubernetes, I started writing a Helm chart in which I'm trying to check if...

2 votes1 replies
GitHub issuesairbytehq/airbyte · FutureFutureToSep 17

[Helm 2.3.0] Digest-pinned orchestrator image becomes invalid 64-character Pod label

### Helm Chart Version Chart 2.3.0; appVersion 2.3.0; official Helm V2 chart. Kubernetes (K3s v1.35.8+k3s1), linux/amd64. ### What step the error happened? During the Sync ### Relevant information We need a supported correction for Airbyte Core 2.3.0 on Helm V2 and Kubernetes,...

GitHub issuesmlflow/mlflow · aqeelatSep 7

[BUG] Helm chart 0.1.1 shipped in the v3.16.0 tag but never published to ghcr

> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. - [x] I have read and...

1 reactions

Companies and products named

8 posts
3 posts
2 posts
2 posts
1 post
About this problem

Evidence

8 posts from 8 people in 5 places, about 1 a week over 43 days. Mostly on mlflow/mlflow, apache/airflow, BerriAI/litellm. Tools named alongside: GitHub, MLflow, Docker, Apache Airflow.

Frustration Frustration 0 of 3· Seen on GitHub issues, Stack Overflow

How it was grouped

Posts that state a pain and match the "k8s-complexity" rule about Kubernetes. First post Sep 7, 2026, latest Oct 19, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

Apache Airflow is too complex to run well

34 posts from 32 people on GitHub issues.

Kubernetes is too complex for most teams

13 posts from 13 people on GitHub issues, Reddit.

Claude Code is too complex to run well

5 posts from 4 people on GitHub issues.

Airbyte is too complex to run well

4 posts from 4 people on GitHub issues.

Google Cloud is too complex to run well

2 posts from 2 people on Reddit. Unverified.

Other Kubernetes problems

Kubernetes upgrades break working setups

23 posts from 19 people on GitHub issues, Hacker News, Stack Overflow.

Kubernetes lock-in makes switching costly

13 posts from 10 people on GitHub issues.

Trouble with Kubernetes test

Top post: "HugepageAwareMemoryReporting [Feature:HugePages] with feature gate enabled should subtract hugepage capacity", one of 10 posts from 9 people on GitHub issues.

Kubernetes permissions are confusing and error-prone

9 posts from 5 people on Mastodon, Bluesky, Reddit.

Trouble with Kubernetes list

Top post: "MutatingAdmissionPolicy: a JSON patch value holding an Object initializer inside a list panics the apiserver", one of 4 posts from 4 people on GitHub issues, Stack Overflow.

Trouble with Kubernetes kubelet

Top post: "Node Declared Features: allow a feature to opt out of re-admission enforcement after kubelet restart", one of 4 posts from 4 people on GitHub issues.

Kubernetes rate limits and usage caps block work

4 posts from 4 people on GitHub issues, Reddit.

Kubernetes outages and slowdowns disrupt work

3 posts from 3 people on GitHub issues.

Trouble with Kubernetes preemption

Top post: "Delete preempted gang PodGroups and CompositePodGroups (DisruptionMode: All) during scheduler preemption", one of 3 posts from 3 people on GitHub issues.

Kubernetes deprecations force unplanned migrations

3 posts from 3 people on GitHub issues.

Kubernetes vulnerabilities are hard to triage and patch

3 posts from 1 person on GitHub issues. Unverified.

Kubernetes agents loop, stall or fail midway

2 posts from 2 people on DEV, GitHub issues. Unverified.

History

Momentum went from steady to fading.

Oct 26, 2026

Momentum went from fading to steady.

Oct 25, 2026

Momentum went from steady to fading.

Oct 23, 2026

Momentum went from rising to steady.

Oct 21, 2026

Momentum went from steady to rising.

Oct 20, 2026

Momentum went from rising to steady.

Oct 19, 2026

Momentum went from fading to rising.

Oct 18, 2026

Momentum went from steady to fading.

Oct 2, 2026

First seen with 3 posts.

Sep 25, 2026