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

Should only set istio route weight when seldon traffic field value > 0 #1658

Closed
anggao opened this issue Apr 3, 2020 · 3 comments
Closed
Labels
bug triage Needs to be triaged and prioritised accordingly

Comments

@anggao
Copy link
Contributor

anggao commented Apr 3, 2020

The following deployment will generate Istio virtualservice with route weight = 0

kind: SeldonDeployment
apiVersion: machinelearning.seldon.io/v1alpha2
metadata:
  name: iris
spec:
  name: iris
  predictors:
    - name: default
      graph:
        name: iris-default
        implementation: SKLEARN_SERVER
        modelUri: gs://seldon-models/sklearn/iris
      replicas: 1
    - name: shadow
      graph:
        name: iris-shadow
        implementation: SKLEARN_SERVER
        modelUri: gs://seldon-models/sklearn/iris
      replicas: 1
      shadow: true
      route:
        - destination:
            host: iris-iris-default
            port:
              number: 8000
            subset: default
          weight: 0

This feels like a bug to me, should only add weight field when user provide traffic field with value > 0

@anggao anggao added bug triage Needs to be triaged and prioritised accordingly labels Apr 3, 2020
@ukclivecox
Copy link
Contributor

Which version of seldon-core - master?

@anggao
Copy link
Contributor Author

anggao commented Apr 3, 2020

I am using v1.0.2

@anggao
Copy link
Contributor Author

anggao commented Apr 6, 2020

@cliveseldon Looks like the issue is fixed in master branch, I don't see it.

@anggao anggao closed this as completed Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

No branches or pull requests

2 participants