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

VirtualService not used by my k8s service #36839

Closed
politrons opened this issue Jan 14, 2022 · 3 comments
Closed

VirtualService not used by my k8s service #36839

politrons opened this issue Jan 14, 2022 · 3 comments
Labels
kind/need more info Need more info or followup from the issue reporter lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while

Comments

@politrons
Copy link

Hi I'm very newby in Istio/K8s, and I'm trying to make a service that I have test-service to use a new VirtualService that I've created.

Here the steps that I did

kubectl config set-context --current --namespace my-namespace
I create my VirtualService

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: test-service
  namespace: my-namespace
spec:
  hosts:
  - test-service
  http:
  - fault:
      delay:
        fixedDelay: 60s
        percentage:
          value: 100
    route:
    - destination:
        host: test-service
        port:
          number: 9100

Then I apply into K8s

kubectl apply -f test-service.yaml
But now when I invoke the test-service using gRPC I can reach the service, but the fault with the delay is not happening.

I dont know in which log I can see of this test-service is using the VirtualService that I created or not

@bianpengyuan
Copy link
Contributor

bianpengyuan commented Jan 14, 2022

Grep HTTPFault at the client proxy (the proxy at the workload which makes the grpc call, or the ingressgateway if you call from outside the mesh) config dump kubectl exec $POD -c istio-proxy -- curl 'localhost:15000/config_dump' > config_dump.json https://github.com/istio/istio/wiki/Troubleshooting-Istio#collecting-information-2

@bianpengyuan bianpengyuan added the kind/need more info Need more info or followup from the issue reporter label Jan 14, 2022
@zirain
Copy link
Member

zirain commented Jan 17, 2022

@politrons where did you start the grpc request? Is that pod injected?

@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Apr 17, 2022
@istio-policy-bot
Copy link

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2022-01-17. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.

@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/need more info Need more info or followup from the issue reporter lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while
Projects
None yet
Development

No branches or pull requests

4 participants