-
Notifications
You must be signed in to change notification settings - Fork 1
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
Configure envoy-operator for CKF 1.8 #56
Conversation
Updates tox.ini's `update-requirements` as described in canonical/argo-operators#100. Ref canonical/kubeflow-ci#59
Modify some values in order to follow upstream configuration from file `third_party/metadata_envoy/envoy.yaml` in pipelines repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @orfeas-k, some comments.
- Use constant for mlmd charm name. - Use latest/edge channel for mlmd. - Use latest/stable channel for other charms. - Remove redundant assertion and add `idle_period` to the one left.
Remove assertion that doesn't make sense anymore. This PR changed the relations between charms resulting in different result from Prometheus endpoint.
Pushed also a commit to remove one assertion in the Prometheus integration test. We still have other assertions after this one that assert the request's data. I think the GET request to Prometheus endpoint returns different results due to the fact that the PR changed the relations and bumped charms to newer version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @orfeas-k
update-requirements
as described inchange tox for update dependencies argo-operators#100.
third_party/metadata_envoy/envoy.yaml in pipelines repo