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

[Improvement] feedback from Sealos #3637

Closed
3 of 8 tasks
sakcer opened this issue Jun 8, 2023 · 7 comments
Closed
3 of 8 tasks

[Improvement] feedback from Sealos #3637

sakcer opened this issue Jun 8, 2023 · 7 comments
Assignees
Labels
kind/enhancement New feature or request Stale

Comments

@sakcer
Copy link

sakcer commented Jun 8, 2023

  • The service crashed when the Pg connection number and QPS were high.
  • The cluster status and pod status are inconsistent. clusters can terminate faster than pods.
  • The minimum value of storage. It is easy to crash if it is too small, and it is troublesome for multi-tenant services if it is too large.
  • A unified change operation that can modify multiple parameter values at once is needed. Currently, we achieve this by modifying the YAML file.
  • There is a quota problem, no default resource limits are set for containers such as metrics.
  • Don't want the database to allow login without a password.
  • There are restrictions on the database specifications which we hope to remove.
  • PVC usage cannot be viewed.
@sakcer sakcer added the kind/enhancement New feature or request label Jun 8, 2023
@ruijun2002
Copy link

There are too few logs, which makes troubleshooting difficult. For this, could you please describe in detail which logs are required. @sakcer

@nashtsai
Copy link
Contributor

nashtsai commented Jun 9, 2023

"There is a quota problem, no default resource limits are set for containers such as metrics." is tracked by #2738

@ruijun2002
Copy link

"There are restrictions on the database specifications which we hope to remove." the instance class restrictions has been removed and a new issue for resource constraints by #3642

@sakcer
Copy link
Author

sakcer commented Jun 9, 2023

There are too few logs, which makes troubleshooting difficult. For this, could you please describe in detail which logs are required. @sakcer

I'll cancel this issue for now, and will provide concrete requirements in the future. Thanks

@ldming
Copy link
Collaborator

ldming commented Jun 9, 2023

"Don't want the database to allow login without a password." and "The service crashed when the Pg connection number and QPS were high." already fixed by #3638

@yimeisun
Copy link
Contributor

yimeisun commented Jun 9, 2023

"PVC usage cannot be viewed" is tracked by #3691

@github-actions
Copy link

This issue has been marked as stale because it has been open for 30 days with no activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

6 participants