Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Agent is taking too long to connect#16624

Unanswered
Cjkjvfnby asked this question inGeneral
Discussion options

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Agent is taking too long to connect when creating namespace when namespace mem/cpu quota is exceeded.

Looks exactly the same as:
#15867

Relevant Log Output

kubectl get eventscoder-37ac6d8f-b9fd-4b89-a33d-9b29201981ef-889d4ddd9-sh6wn” is forbidden: exceeded quota: resourcequota-name, requested: limits.memory=2Gi, used: limits.memory=16Gi, limited: limits.memory=16Gi

Expected Behavior

Human friendly message is shown to user.

Steps to Reproduce

  • set mem/cpu quota to the namespace where workspace will be run
  • create workspace with more resources when quota

Environment

Additional Context

The issue occurs consistently

You must be logged in to vote

Replies: 1 comment

Comment options

Hi@Cjkjvfnby, Thanks for the report. This is not a bug, but by design. The coder can not access the Kubernetes logs.
We do have a method that will allow you to stream these logs to the workspace page. Please checkhttps://coder.com/docs/admin/integrations/kubernetes-logs.

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
2 participants
@Cjkjvfnby@matifali
Converted from issue

This discussion was converted from issue #16622 on February 19, 2025 16:17.


[8]ページ先頭

©2009-2025 Movatter.jp