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

Aws advanced filters doc 1650 #4816

Open
wants to merge 33 commits into
base: master
Choose a base branch
from
Open

Conversation

rickshar
Copy link
Collaborator

This is the default pull request template. You can customize it by adding a pull_request_template.md at the root of your repo or inside the .github folder.

Jira Ticket

Include a link to your Jira Ticket
Example: JIRAISS-1234

Demo

Please add a recording of the feature/bug fix in work. if you added new routes, the recording should show the request and response for each new/changed route

Checklist:

  • I have filled relevant self assessment (NodeJS, Frontend, Backend)
  • I have run ESlint on my changes and fixed all warnings and errors (NodeJS & Frontend Services)
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have validated all the requirements in the Jira task were answered
  • I have all neccessary approvals for the design/mini design of this task
  • I have approved the API changes and granular permission patterns (documentation subtask) (For public services only)


Cloud service provider relevance: AWS Kubernetes and EKS

This topic describes how to work with Virtual Mode Groups for AWS Kubernetes.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rickshar Spelling issue - Virtual Mode Group

# Manage Virtual Node Groups
# Manage AWS Virtual Node Groups

Cloud service provider relevance: AWS Kubernetes and EKS
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rickshar You can remove EKS, it's under AWS K8s

1. In the console, go to Ocean/Cloud Clusters and click the Ocean Cluster you want to add a VNG to.
2. Click the Virtual Node Groups tab.
* ID: The identification code of the VNG.
* Name: The user-defined name of the VNG. (If a VNG was defined without a time, it will appear in this column as Unnamed Virtual Node Group.)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rickshar Without a name, not a time

2. Click the Virtual Node Groups tab.
* ID: The identification code of the VNG.
* Name: The user-defined name of the VNG. (If a VNG was defined without a time, it will appear in this column as Unnamed Virtual Node Group.)
* Resource Allocation: Percent of defined resources (CPU, Memory, and GPU) currently used by the VNG.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rickshar It's incorrect to say 'used' by the VNG. Maybe you can change it to '..currently running on Nodes from this VNG.

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 this pull request may close these issues.

2 participants