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

virtual machine WorkloadEntry documentation unclear #15568

Open
sdake opened this issue Aug 15, 2024 · 2 comments
Open

virtual machine WorkloadEntry documentation unclear #15568

sdake opened this issue Aug 15, 2024 · 2 comments

Comments

@sdake
Copy link
Member

sdake commented Aug 15, 2024

Hello,

The istio.io website has had nice improvements since I last contributed. Great work all.

I am attempting to follow the howto for VMs. There is one part that may be in error, or may not be, I am not sure.

https://istio.io/latest/docs/setup/install/virtual-machine/#create-files-to-transfer-to-the-virtual-machine

In the tab Default:
A WorkloadGroup is created

In the tab Automated WorkloadEntry Creation
A WorkloadGroup is created
This WorkloadGroup custom resource is then applied with kubectl apply -f ...

A suggestion:
The WorkloadGroup is the same in either step. Is this intentional? If so, it may make sense to pull it out into its own step.

And a potentioal bug?:
Why is kubectl apply -f ... applied in Automated WorkloadGroup creation, but not Default.

This may just be an error with how the tabs are constructed. I am really not clear on whether a WorkloadGroup is required in the non-automated setup.

Thank you,
-steve

cc /@howardjohn as he has worked in this area in the past.

@sdake
Copy link
Member Author

sdake commented Aug 15, 2024

The reference here: https://istio.io/latest/docs/reference/config/networking/workload-group/ does not cover automated workload entry creation. Perhaps this would be a suggestion for an ehancement to the custom resource documentation.

@RicHincapie
Copy link
Contributor

There's also an issue regarding lack of clarity about the need to create WorkloadEntry and ServiceEntry if user is not onboarded in the yet experimental automated workload entry

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