WIP to Rebase v1.6.1 #8353
Closed
WIP to Rebase v1.6.1 #8353
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These files are needed to make the openshift fork work with ci and release processes. Files: * OWNERS * OWNERS_ALIASES * openshift/Containerfile.rhel * .ci-operator.yaml
Co-authored-by: Vighnesh Maheshwari <[email protected]>
PODAUTO-308: Add openshift stuff
PODAUTO-308: add vendor folder
…fetched (aws#7877) (aws#7885) Co-authored-by: Jonathan Innis <[email protected]>
Upstream has an entrypoint specified in their containerfile, hypershift was hard coded to use an upstream image, but we need to use our shipping one now, and we'd prefer not to have to change the args based on which one we're using. This just adds the entrypoint so the upstream/downstream image usages are interchangeable (at least until we skew on args or something with carry patches someday).
AUTOSCALE-193: Add entrypoint to aws provider containerfile to match upstream behavior
These files are needed to make the openshift fork work with ci and release processes. Files: * OWNERS * OWNERS_ALIASES * openshift/Containerfile.rhel * .ci-operator.yaml
Upstream has an entrypoint specified in their containerfile, hypershift was hard coded to use an upstream image, but we need to use our shipping one now, and we'd prefer not to have to change the args based on which one we're using. This just adds the entrypoint so the upstream/downstream image usages are interchangeable (at least until we skew on args or something with carry patches someday).
AUTOSCALE-193: Rebase on upstream 1.2.3, cherry-pick "build target" commit
AUTOSCALE-193: temporarily apply operator label for inclusion in release
… dependency Signed-off-by: Max Cao <[email protected]>
AUTOSCALE-259: migrate upstream karpenter-core dependency to downstream
…t-4.20-aws-karpenter-provider-aws OCPBUGS-57717: Updating aws-karpenter-provider-aws-container image to be consistent with ART for 4.20
These files are needed to make the openshift fork work with ci and release processes. Files: * OWNERS * OWNERS_ALIASES * openshift/Containerfile.rhel * .ci-operator.yaml
Upstream has an entrypoint specified in their containerfile, hypershift was hard coded to use an upstream image, but we need to use our shipping one now, and we'd prefer not to have to change the args based on which one we're using. This just adds the entrypoint so the upstream/downstream image usages are interchangeable (at least until we skew on args or something with carry patches someday).
… dependency Signed-off-by: Max Cao <[email protected]>
…release Necessary until hypershift includes image-references.
…o be consistent with ART for 4.20 Reconciling with https://github.com/openshift/ocp-build-data/tree/dfb5c7d531490cfdc61a3b88bc533702b9624997/images/aws-karpenter-provider-aws.yml
✅ Deploy Preview for karpenter-docs-prod ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #CNTRLPLANE-1261
Description
As part of the rebase to Kubernetes 1.33, we need to bump Karpenter to 1.6.1
How was this change tested?
No tests run on this yet
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.