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 fallback instance types for security agent functional tests #16303

Merged
merged 2 commits into from
Mar 28, 2023

Conversation

paulcacheux
Copy link
Contributor

@paulcacheux paulcacheux commented Mar 28, 2023

What does this PR do?

We have been having some spot provisioning issues for the past few days, this PR fixes this issue by providing fallback instance types in case t3.medium is not available:

  • t2.xlarge was chosen because this is the instance type use by system probe functional tests on amazon linux
  • t3.xlarge was chosen because this is the default value, used by most regular kitchen tests

Documentation pointing to this way of providing fallbacks: https://kitchen.ci/docs/drivers/aws/#instance_type

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

  • If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
  • Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
  • A release note has been added or the changelog/no-changelog label has been applied.
  • Changed code has automated tests for its functionality.
  • Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
  • At least one team/.. label has been applied, indicating the team(s) that should QA this change.
  • If applicable, docs team has been notified or an issue has been opened on the documentation repo.
  • If applicable, the need-change/operator and need-change/helm labels have been applied.
  • If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
  • If applicable, the config template has been updated.

@paulcacheux paulcacheux added changelog/no-changelog [deprecated] qa/skip-qa - use other qa/ labels [DEPRECATED] Please use qa/done or qa/no-code-change to skip creating a QA card team/agent-security labels Mar 28, 2023
@paulcacheux paulcacheux added this to the 7.45.0 milestone Mar 28, 2023
@paulcacheux paulcacheux changed the title fallback on t2.xlarge for security agent functional tests add fallback instance types for security agent functional tests Mar 28, 2023
@paulcacheux paulcacheux marked this pull request as ready for review March 28, 2023 09:02
@paulcacheux paulcacheux requested review from a team as code owners March 28, 2023 09:02
@paulcacheux paulcacheux merged commit aaafc02 into main Mar 28, 2023
@paulcacheux paulcacheux deleted the paulcacheux/secagent-functests-inst-type branch March 28, 2023 11:48
truthbk pushed a commit that referenced this pull request Apr 14, 2023
* fallback on `t2.xlarge` for security agent functional tests

* even more fallbacks
truthbk added a commit that referenced this pull request Apr 15, 2023
* Update release.json and Go modules for 6/7.43.2-rc.1

* add fallback instance types for security agent functional tests (#16303)

* fallback on `t2.xlarge` for security agent functional tests

* even more fallbacks

---------

Co-authored-by: Paul Cacheux <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog [deprecated] qa/skip-qa - use other qa/ labels [DEPRECATED] Please use qa/done or qa/no-code-change to skip creating a QA card team/agent-security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants