-
Notifications
You must be signed in to change notification settings - Fork 63
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 EKS 1.30 and 1.31 for testing #1736
Conversation
We probably will have to update the kubectllayer implementation. Once we have these clusters deployed as per next steps we can remove deprecated eks k8s version in follow up PR's. |
version: "1.31" | ||
launch_type: ec2 | ||
instance_type: "m5.large" | ||
- name: collector-ci-fargate-1-31 |
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.
we shall add the same for operator-ci-* and java-instrumentation-operator-*
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.
yeah I can.
where are java-instrumentation-operator-ci
and operator-ci
referenced? I tried looking for them but I didn't, so I didn't update
9197830
to
3effcd4
Compare
@@ -45,6 +45,28 @@ clusters: | |||
- name: collector-ci-fargate-1-27 | |||
version: "1.27" | |||
launch_type: fargate | |||
- name: collector-ci-arm64-1-30 | |||
version: "1.30" |
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.
updating test_config is probably the last change need
Description:
Adding EKS 1.30 and 1.31 for Kubernetes
Link to tracking Issue:
Testing:
Documentation:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.