Open paloma-rebuelta opened 1 year ago
@paloma-rebuelta I was not able to replicate your problem using your kustomization file (I removed the pvc patch because I could not create a pv with this storageClassName -- I used a kind cluster). The controller started without any errors for me. Inspection of the error suggests the config file could not be found. The pod configuration (kubectl -n iter8 get po -o yaml
) should show that comes from the configmap iter8
.
That said, mirroring was not available in this version. Inspection of the helm chart shows that it was stubbed out. No tutorials were provided. We would appreciate a contribution of this capacity :). In the latest version of Iter8, the templates of the release
chart would need to be updated.
Describe the bug
I am working on the mirroring trafic use case for modelmesh. I have deployed the traffic controller v0.17.1 as there is no mirroring usecase in the iter8 docs for later versions. The controller resources get created, the pod spins up, but I get error logs relating to the metrics and A/B?n service and BadgerDB:
This doesn't kill the pod, its status is "Running". When I deploy a candidate model and use the mirroring traffic template, the virtual service remains intact, it does not get altered based on the weights configmaps.
To Reproduce the controller was deployed using this kustomization file:
Expected behavior When I deploy a candidate model and the mirroring traffic templates, I would expect traffic to be mirrored to the second model. This does not happen as the virtual service does not get updated with the weights.
Desktop (please complete the following information):
iter8 version
command: irrelevant as using controllerAdditional context Add any other context about the problem here.