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

Update README.md #1978

Merged
merged 1 commit into from
Jul 29, 2024
Merged

Update README.md #1978

merged 1 commit into from
Jul 29, 2024

Conversation

deniseschannon
Copy link
Contributor

What issue type does this pull request address? (keep at least one, remove the others)

/kind documentation

What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible)
resolves #ENG-3390

Copy link

netlify bot commented Jul 23, 2024

Deploy Preview for vcluster-docs canceled.

Name Link
🔨 Latest commit a94a8e5
🔍 Latest deploy log https://app.netlify.com/sites/vcluster-docs/deploys/66a00643ae75750008320c08

@deniseschannon deniseschannon force-pushed the update-readme branch 3 times, most recently from 7b6c26c to 72be4cd Compare July 23, 2024 19:31
- **Strict isolation**: complete separate Kubernetes control plane and access point for each vcluster while still being able to share certain services of the underlying host cluster
- **Cluster Wide Permissions**: allow users to install apps which require cluster-wide permissions while being limited to actually just one namespace within the host cluster
- **Great for Testing**: allow you to test different Kubernetes versions inside a single host cluster which may have a different version than the virtual clusters
Virtual clusters are fully functional Kubernetes clusters nested inside a physical host cluster providing better isolation and flexibility to support multi-tenancy. Multiple teams can operate independently within the same physical infrastructure while minimizing conflicts, maximizing autonomy, and reducing costs.
Copy link
Contributor

Choose a reason for hiding this comment

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

Less a suggestion of I think you should do this. I'm just personally more likely to halt a quick scroll for a short bulleted list.

Suggested change
Virtual clusters are fully functional Kubernetes clusters nested inside a physical host cluster providing better isolation and flexibility to support multi-tenancy. Multiple teams can operate independently within the same physical infrastructure while minimizing conflicts, maximizing autonomy, and reducing costs.
Virtual clusters are fully functional Kubernetes clusters nested inside a physical host cluster providing better isolation and flexibility to support multi-tenancy. Multiple teams can operate independently within the same physical infrastructure while
* Minimizing conflicts
* Maximizing autonomy
* Reducing costs

curl -L -o vcluster "https://github.com/loft-sh/vcluster/releases/latest/download/vcluster-darwin-amd64" && sudo install -c -m 0755 vcluster /usr/local/bin
```
### Cost-effectiveness and reduced overhead
- **Lightweight Infrastructure:** Virtual clusters are significantly more lightweight than physical clusters, able to spin up in seconds, which contrasts sharply with the lengthy provisioning times often seen in environments like EKS (~45 minutes).
Copy link
Contributor

Choose a reason for hiding this comment

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

Take it or leave it, just an alternative.

Suggested change
- **Lightweight Infrastructure:** Virtual clusters are significantly more lightweight than physical clusters, able to spin up in seconds, which contrasts sharply with the lengthy provisioning times often seen in environments like EKS (~45 minutes).
- **Lightweight Infrastructure:** Virtual clusters are significantly lighter weight than physical clusters, able to spin up in seconds, which contrasts sharply with the lengthy provisioning times often seen in environments like EKS (~45 minutes).

Copy link
Contributor

@zerbitx zerbitx left a comment

Choose a reason for hiding this comment

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

LGTM. Minor suggestions that shouldn't impede merging.

@deniseschannon deniseschannon merged commit 04df2b6 into main Jul 29, 2024
8 checks passed
@deniseschannon deniseschannon deleted the update-readme branch July 29, 2024 03:28
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