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

Changes to the wording around Resource increase auto-approval #4613

Open
funtigr opened this issue Jan 8, 2025 · 3 comments
Open

Changes to the wording around Resource increase auto-approval #4613

funtigr opened this issue Jan 8, 2025 · 3 comments
Assignees

Comments

@funtigr
Copy link
Collaborator

funtigr commented Jan 8, 2025

Description:
There were changes made to the resource increase auto-approval. This task is to change wording to reflect the changes.

I will list all the previous change descriptions for reference, will delete them later after writing a full description for this iteration of the task.

The comment from me:
Everything looks good except couple of things:

  1. On Resource Page maybe we would change requests to request in the column names.
    Because we have only one request value for the namespace. Using plural can be confusing for the user.

image.png

  1. Also the wording in the Quota section of Product page:
    2.1 The phrase Your namespace’s resource utilization rate is at least 35%. sounds a bit unclear. Maybe we could add details, e.g. Your namespace average resource utilization rate during last 2 weeks exceeds 35% of the current resource request
    2.2 The phrase Starts from a minimum of 1 core for CPU and 2GB for memory, or. As far as I understand now we have a minimum value of 1, so if a User tries to go from 0.5 to 1 it will be auto-approved even without meeting any of the conditions. So maybe we would write a separate explanation for that or just not mention it?
    2.3 The phrase Is 32GB or less, or Does not exceed a 50% increase in the current capacity. As far as I understand there should be and, not or, and everything that is above 32Gb would be reviewed by Billy even if it meets other conditions.

image.png

The comment from Alex:
Do we need to be capitalizing storage and memory? We don't in our documentation so we should here - keep CPU as its an acronym.

Increasing your quota requires the Platform Services Team’s approval, and must have supporting information as per our quota adjustment documentation. Any quota increases without supporting information WILL NOT be processed.

Your request for additional CPU, memory, and storage will be automatically approved if ALL of the following conditions are met.

For CPU and memory:

  • Your namespace’s resource utilization rate is at least 35%.
  • The adjustment satisfies one of the following: starts from a minimum of 1 core for CPU and 2GB for memory, OR does not exceed a 50% increase in the quota.

For storage:

  • Your namespace’s current usage exceeds 80% of its requested capacity.
  • The adjustment satisfies one of the following: is 32GB or less, OR does not exceed a 50% increase in the current capacity.
@funtigr funtigr self-assigned this Jan 8, 2025
@Kolezhanchik
Copy link
Collaborator

@funtigr it is already request no requests image.png

@Kolezhanchik
Copy link
Collaborator

and I may I see the final version of the text?

@funtigr
Copy link
Collaborator Author

funtigr commented Jan 8, 2025

Additional data:
Billy approved that OR wording for Storage is right:
image.png

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

No branches or pull requests

2 participants