-
Notifications
You must be signed in to change notification settings - Fork 84
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
Fix: Tetrate Istio Updates #254
Conversation
@@ -187,28 +187,3 @@ resource "aws_prometheus_rule_group_namespace" "alerting_rules" { | |||
for: 30m | |||
EOF | |||
} | |||
|
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.
why are we moving dashboards definition out of here?
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.
I ran into a few errors when the dashboard was kept there. I saw there were other dashboards in that file so aligned under there. Should I move it back?
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.
Yes if possible. We tried to separate add-ons dashbaords in their submodules, see java or nginx for example.
Dashboards included in the module don't have a separated submodule. this will help with consistency
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.
any updates @dms486?
This PR has been automatically marked as stale because it has been open 60 days |
Pull request closed due to inactivity. |
What does this PR do?
Updating the Tetrate Istio version and aligning with the EKS Blueprints Add-ons changes
Motivation
More
pre-commit run -a
with this PRNote: Not all the PRs required examples and docs.
For Moderators
Additional Notes