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

Fix: Tetrate Istio Updates #254

Closed
wants to merge 5 commits into from
Closed

Conversation

dms486
Copy link
Contributor

@dms486 dms486 commented Jan 12, 2024

What does this PR do?

Updating the Tetrate Istio version and aligning with the EKS Blueprints Add-ons changes

Motivation

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Yes, I ran pre-commit run -a with this PR
  • Yes, I have added a new example under examples to support my PR (when applicable)
  • Yes, I have updated the Pages for this feature

Note: Not all the PRs required examples and docs.

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@@ -187,28 +187,3 @@ resource "aws_prometheus_rule_group_namespace" "alerting_rules" {
for: 30m
EOF
}

Copy link
Member

@bonclay7 bonclay7 Jan 12, 2024

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?

Copy link
Contributor Author

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?

Copy link
Member

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any updates @dms486?

Copy link

This PR has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Mar 20, 2024
Copy link

Pull request closed due to inactivity.

@github-actions github-actions bot closed this Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants