Open
Conversation
The goal here is to connect a public cloud DNS entry to virtual machines in my home lab. The configuration is derived from the Istio documentation (multi-network, single cluster, automatic worklaodentry creation) I am not sure why `run-curl.sh` doesn't complete. The virtual machines are added to the mesh: ``` sdake@a40x2:~$ istioctl proxy-status NAME CLUSTER CDS LDS EDS RDS ECDS ISTIOD VERSION a40x2.vllm cluster1 SYNCED SYNCED SYNCED SYNCED istiod-67f89ccbd9-5slrc 1.23.0 istio-eastwestgateway-6cb57b485f-f76pv.istio-ingress cluster1 SYNCED SYNCED SYNCED istiod-67f89ccbd9-5slrc 1.23.0 istio-ingress-7bd5b47574-zs548.istio-ingress cluster1 SYNCED SYNCED SYNCED SYNCED istiod-67f89ccbd9-5slrc 1.23.0 ``` The a40x2.vllm proxy should map to the DNS name vllm.vllm. I have another node not currently shown here (a30x2). This configuration doesn't quite setup automatic workload entry creation. to do that, some environment varibales need to be set. The workflow is: ``` bash generate-istio-manifests.sh kubectl apply -f istio-ns.yaml kubectl apply -f istio-base.yaml kubectl apply -f istio-istiod-mutli.yaml kubectl apply -f istio-gateway-mutli.yaml kubectl apply -f istio-gateway-eastwest-mutli.yaml kubectl apply -f meta.yaml kubectl apply -f expose-istiod.yaml bash install-vm-files.sh bash run-curl.sh ``` This run-curl.sh operation should generate some output, but currently fails. I am not sure if the failure is a misconfiguration, related to a problem with the eastwest gateway and ingress gateway routing, or a defect in istio.
Member
Author
|
One potential problem is the application of |
MostAwesomeDude
approved these changes
Aug 24, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal here is to connect a public cloud DNS entry to virtual machines in my home lab. The configuration is derived from the Istio documentation (multi-network, single cluster, automatic worklaodentry creation)
I am not sure why
run-curl.shdoesn't complete. The virtual machines are added to the mesh:The a40x2.vllm proxy should map to the DNS name vllm.vllm. I have another node not currently shown here (a30x2). This configuration doesn't quite setup automatic workload entry creation. to do that, some environment varibales need to be set.
The workflow is:
This run-curl.sh operation should generate some output, but currently fails. I am not sure if the failure is a misconfiguration, related to a problem with the eastwest gateway and ingress gateway routing, or a defect in istio.