You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 createdIn the tab
Automated WorkloadEntry Creation
A
WorkloadGroup
is createdThis 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 inAutomated WorkloadGroup
creation, but notDefault
.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.
The text was updated successfully, but these errors were encountered: