AUTOSCALE-571: fix(karpenter): don't associate public IP addresses for the default OpenshiftEC2NodeClass#7853
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@joshbranham: This pull request references AUTOSCALE-571 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@joshbranham: This pull request references AUTOSCALE-571 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughRemoved a conditional block from the Karpenter controller that previously assigned the OpenshiftEC2NodeClass Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@joshbranham: This pull request references AUTOSCALE-571 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/test unit |
|
/test e2e-azure-self-managed |
|
/test security |
|
/verified by @joshbranham in e2e |
|
@joshbranham: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Now that #7933 is in, this should be able to come out since we're explicitly selecting private networks by default, a public one shouldn't be able to be in the list and need this. |
|
Scheduling tests matching the |
|
/test e2e-aws |
127840e to
7bdcca3
Compare
|
/test e2e-aws-autonode |
|
This aligns with hypershift/test/e2e/karpenter_test.go Line 54 in 4585fa1 We'll want to revaluate this to not degrade infra cost in presubmits. /approve |
|
/test e2e-aws-autonode |
|
/retest-required |
|
/verified by @joshbranham in e2e |
|
@joshbranham: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-aws-techpreview |
hey @joshbranham , I believe you will need the fix on #8037. The e2e-aws-techpreview will fail without that. |
…penshiftEC2NodeClass Previously, Karpenter would reconcile the default named OpenshiftEC2NodeClass to use public IPs if the annotation was set. This annotation was used for testing purposes, and was likely added as the initial e2e test suite had public subnets only. The default behavior for this OpenshiftEC2NodeClass should be that it works in private subnets. However, if you use a public subnet, you should not expect to get a public IP. If a user wants to use public subnets with a public IP for nodes, they should make their own OpenshiftEC2NodeClass and set `spec.AssociatePublicIPAddress: true` there.
7bdcca3 to
05d7dca
Compare
|
/approve |
|
@enxebre: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Scheduling tests matching the |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre, joshbranham The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-aks |
|
/retest-required |
|
/test e2e-aws-techpreview |
|
/hold cancel |
|
/retest-required |
|
/test e2e-aws-techpreview |
|
/test e2e-azure-self-managed |
|
/retest-required |
|
@joshbranham: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
39adbe6
into
openshift:main
What this PR does / why we need it:
Previously, Karpenter would reconcile the default named OpenshiftEC2NodeClass to use public IPs if the annotation was set. This annotation was used for testing purposes, and was likely added as the initial e2e test suite had public subnets only.
The default behavior for this OpenshiftEC2NodeClass should be that it works in private subnets. However, if you use a public subnet, you should not expect to get a public IP.
If a user wants to use public subnets with a public IP for nodes, they should make their own OpenshiftEC2NodeClass and set
spec.AssociatePublicIPAddress: truethere.Which issue(s) this PR fixes:
Fixes AUTOSCALE-571
Special notes for your reviewer:
Checklist:
Summary by CodeRabbit
AssociatePublicIPAddresssetting now defaults to unset during reconciliation, changing how public IP addresses are managed for EC2 nodes.