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.

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

GKE upgrade v1.25 to v1.28 broke odigos daemonsets #1321

Closed
dirtyren opened this issue Jul 2, 2024 · 2 comments · Fixed by #1322
Closed

GKE upgrade v1.25 to v1.28 broke odigos daemonsets #1321

dirtyren opened this issue Jul 2, 2024 · 2 comments · Fixed by #1322

Comments

@dirtyren
Copy link

dirtyren commented Jul 2, 2024

Describe the bug
GKE update from v1.25 pra v1.28 broke odigos daemonsets

I am getting the following error:
Warning FailedCreate 2m5s (x85 over 8h) daemonset-controller Error creating: insufficient quota to match these scopes: [{PriorityClass In [system-node-critical system-cluster-critical]}]
Another problem is that, after update, due to the daemonsets not starting, the apps orchestrated by Odigos also did not start.

To Reproduce
Update GKE from v1.25 to v1.28

@edeNFed
Copy link
Contributor

edeNFed commented Jul 2, 2024

Thanks for reporting @dirtyren I will fix it asap

@edeNFed
Copy link
Contributor

edeNFed commented Jul 3, 2024

@dirtyren I am working on a fix for GKE that should be released soon.
As a workaround you can run the following commands before installing Odigos and it will work:
kubectl create namespace odigos-system
kubectl label namespace odigos-system odigos.io/system-object="true"

Apply the following YAML:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: odigos-quota
  namespace: odigos-system
spec:
  hard:
    pods: "10k"
  scopeSelector:
    matchExpressions:
    - operator: In
      scopeName: PriorityClass
      values:
      - system-node-critical

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants