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

Add dynamic timewait in integ tests #82

Merged
merged 4 commits into from
Feb 14, 2024

Conversation

KlwntSingh
Copy link
Contributor

@KlwntSingh KlwntSingh commented Feb 7, 2024

Description of changes:

  1. Add dynamic wait times for deploying CW agent on Windows.
  2. Add both 2019 and 2022 Windows nodes as part of integ tests.
Screenshot 2024-02-08 at 8 02 35 AM

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

curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
chmod +x kubectl
./kubectl rollout status daemonset fluent-bit-windows -n amazon-cloudwatch --timeout 600s
./kubectl rollout status daemonset cloudwatch-agent-windows -n amazon-cloudwatch --timeout 600s
Copy link
Contributor

Choose a reason for hiding this comment

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

Is 2m always enough? any chance that we need to loop this?

@KlwntSingh KlwntSingh merged commit 134681f into aws:main-ciwindows Feb 14, 2024
1 check passed
KlwntSingh added a commit to KlwntSingh/amazon-cloudwatch-agent-operator that referenced this pull request Mar 2, 2024
* Add dynamic timewait in integ tests

* Added missed wait time

* Added windows integ tests as part of integ

1. Added instructions to run 2 integ for each windows os version

* Update pod count in tests
KlwntSingh added a commit to KlwntSingh/amazon-cloudwatch-agent-operator that referenced this pull request Mar 18, 2024
* Add dynamic timewait in integ tests

* Added missed wait time

* Added windows integ tests as part of integ

1. Added instructions to run 2 integ for each windows os version

* Update pod count in tests
KlwntSingh added a commit that referenced this pull request Mar 18, 2024
* Add dynamic timewait in integ tests

* Added missed wait time

* Added windows integ tests as part of integ

1. Added instructions to run 2 integ for each windows os version

* Update pod count in tests
KlwntSingh added a commit to KlwntSingh/amazon-cloudwatch-agent-operator that referenced this pull request Mar 18, 2024
* Add dynamic timewait in integ tests

* Added missed wait time

* Added windows integ tests as part of integ

1. Added instructions to run 2 integ for each windows os version

* Update pod count in tests
lisguo pushed a commit that referenced this pull request Mar 26, 2024
* Operator image and integ tests (#59)

* Add helm template for CW agent on Windows

1. Made change in operator to dynamically mutate operator
to add cwagentconfig MountVolume
2. Added github workflow to build and upload cwagent operator to internal ECR repo
3. Added integration tests against helm addon
4. Added terraform module to run test against EKS Windows cluster
5. Update go tests with linuxonly and Windows tags

* Fix: Change resource limit values to same as linux
# Conflicts:
#	helm/templates/_helpers.tpl
#	pkg/collector/container.go

# Conflicts:
#	helm/templates/_helpers.tpl
#	helm/values.yaml
#	integration-tests/eks/validateResources_test.go

* Run CW agent as host process container (#67)

* Fix issues in helm charts during e2e testing (#75)

* Update helm templates for CW agent and fluent bit on Windows

* Removing configuration about kubernetes from fluentbit

* Disable AppSignal on EKS Windows (#76)

# Problem
AppSignal is having issues around initializing k8s client on EKS Windows
when running it as Host process container. Similar issues existed for
CI Windows but workaround was implemented for CI, similar workaround is
required for AppSignal or We can upgrade container to 1.7 which solves this
issue.
# Conflicts:
#	helm/values.yaml

* Add dynamic timewait in integ tests (#82)

* Add dynamic timewait in integ tests

* Added missed wait time

* Added windows integ tests as part of integ

1. Added instructions to run 2 integ for each windows os version

* Update pod count in tests

* Change fluentbit configuration to use in-memory (#86)

Increased fluentbit request/limits according to public eks fluentbit blog

* Add todo to fix link to container image (#97)

1. Added todo's to fix link to CI
2. Change tag to fluentbit on Windows
# Conflicts:
#	helm/values.yaml

* Remove temporary changes for dev testing

# Conflicts:
#	helm/templates/_helpers.tpl

* 1. Remove customer configuration for CW agent on Windows

2. Change cpu, memory request limits when fluentbit log is disabled.

* Add region in deployment on Windows

* Add region in helm deployment

* Fix: windows service and daemonset is created irrespective of Windows node

# Conflicts:
#	integration-tests/eks/resourceCount_linuxonly_test.go

* Add comments and update version.txt

1. Added comments in resourcecount_test files
2. Update CW agent version in version.txt file

* Address comments

1. Update operation version to 1.2
2. renamed CW agent windows daemonset file name

* Address comments

1. Update helm chart versions
2. Add unit tests for Windows specific changes in operator

* Restructure deployments specific to Linux and Windows

* Fix relative to deployments

* Add nodeSelector for dcgm node selector

* Fix integ tests for Linux
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.

3 participants