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

bugfix: Adds cluster role for otel daemonset deployment mode #991

Conversation

arunvthangaraj
Copy link
Contributor

Issue #, if available: 990

Description of changes: This PR adds the required cluster role for the daemonset template.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link
Collaborator

@elamaran11 elamaran11 left a comment

Choose a reason for hiding this comment

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

LGTM.

@elamaran11
Copy link
Collaborator

@shapirov103 Please approve and Merge. E2E is not required.

Copy link
Collaborator

@shapirov103 shapirov103 left a comment

Choose a reason for hiding this comment

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

LGTM

@shapirov103
Copy link
Collaborator

/do-e2e-tests

Copy link

@aws-ia-ci aws-ia-ci left a comment

Choose a reason for hiding this comment

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

end to end tests failed. A maintainer can provide more details.

@shapirov103
Copy link
Collaborator

/do-e2e-tests

Copy link

@aws-ia-ci aws-ia-ci left a comment

Choose a reason for hiding this comment

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

end to end tests failed. A maintainer can provide more details.

@shapirov103
Copy link
Collaborator

@shapirov103 Please approve and Merge. E2E is not required.

@elamaran11 aren't we deploying this addon in e2e, so if there is an error in the modified kubernetes manifest we should be able to catch it. Ideally, functional verification is also needed, e.g. similar to what we do in Conformitron. That will improve quality assurance and reduce issues from customers.

I will look into the e2e failure.

@elamaran11
Copy link
Collaborator

elamaran11 commented May 1, 2024

@shapirov103 Please approve and Merge. E2E is not required.

@elamaran11 aren't we deploying this addon in e2e, so if there is an error in the modified kubernetes manifest we should be able to catch it. Ideally, functional verification is also needed, e.g. similar to what we do in Conformitron. That will improve quality assurance and reduce issues from customers.

I will look into the e2e failure.

@shapirov103 We do have E2E for this addon already but the addon supports 4 different types of modes - deployment daemonset statefulset and sidecar we cant accomodate all of these in one e2e deployment. So our e2e deploys only deployment mode. We can alter it but we dont use daemonset approach in most situations as its an anti-pattern. Arun is working on a blog with daemonset so this was broken and this change is required. But e2e failure is not related to this change. So once e2e issues are fixed, we can merge this.

@elamaran11
Copy link
Collaborator

@shapirov103 Can this be merged?

@shapirov103 shapirov103 dismissed aws-ia-ci’s stale review May 17, 2024 14:31

Failure unrelated to the modified code (sporadic network connection issue)

@shapirov103
Copy link
Collaborator

Yes, the error on e2e was unrelated.

@shapirov103 shapirov103 merged commit ff31f6a into aws-quickstart:main May 17, 2024
1 check passed
@arunvthangaraj arunvthangaraj deleted the feature/add-cluster-role-for-otel branch May 17, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AddOns: Amp addon does not deploy the right cluster role when Daemonset deployment mode is used
4 participants