-
Notifications
You must be signed in to change notification settings - Fork 3
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
Integration tests are missing for volume's workload #29
Comments
Does this still stand? I see that there are some disabled tests in main but do we need them? Although, not 100% relevant, we agreed in canonical/bundle-kubeflow#621 to test web apps using their unit/k8s-svc IP instead of going through Istio's ingress gateway. Thus, if we decide to keep those, we could change this too. |
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5272.
|
This is still relevant. There are no integration tests for the charm's workload. |
Instead of creating a new task, when tackling this one we should also take into account that during canonical/bundle-kubeflow#621, it was agreed to test web apps charms by using the unit/k8s-svc IP directly instead of going through istio's ingressgateway. Thus, we should remove istio charms from integration tests. By removing istio, tests will also be independent of istio charms' failures. |
See #27, #28
The text was updated successfully, but these errors were encountered: