forked from kubernetes-sigs/cluster-api
-
Notifications
You must be signed in to change notification settings - Fork 6
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
CAPI 1.9.4 for EKS-A #35
Open
2ez4szliu
wants to merge
4,932
commits into
abhay-krishna:main
Choose a base branch
from
2ez4szliu:eks-a-release-1.9
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
…rading twice (kubernetes-sigs#11351) * fix: considers objects in kube-system for cert-manager to avoid upgrading twice * fix: removes use of slices.DeleteFunc because it zeros the elements and doesn't remove those from obj list * fix: do not reassign slice as it is used in different methods
…v1beta2-kcp-available-condition 🌱 Refine v1beta2 Available condition in KCP
…ion annotations Right now, the `oldest` and `newest` deletion policies prioritize machines that have the `cluster.x-k8s.io/delete-machine` annotation over unhealthy machines when deciding which machines need to be deleted. This wasn't the case with the `random` deletion policy. This change aligns the latter to the rest, making it honor the deletion annotation.
Signed-off-by: Stefan Büringer [email protected]
…v1beta2-aggregation-object-order 🌱 Refine v1beta2 object sort for aggregation
…2-conditions 🌱 Add v1beta2 conditions to ClusterClass
Signed-off-by: Stefan Büringer [email protected]
…ignore-new-machines 🌱 Ignore new Machines when calculating MachinesUpToDate condition
…v1beta2-scalingup-conditions 🌱 Refine v1beta2 ScalingUp conditions
* Use namespace of the reference on Get Signed-off-by: Danil-Grigorev <[email protected]> * Updating tests Signed-off-by: Danil-Grigorev <[email protected]> * Update references usage across the code Signed-off-by: Danil-Grigorev <[email protected]> * Ensure refrence namespace is populated in MD Signed-off-by: Danil-Grigorev <[email protected]> * Use kref for logging Signed-off-by: Danil-Grigorev <[email protected]> * Ensure ref NS in MS is set, and ignored in hash Signed-off-by: Danil-Grigorev <[email protected]> * Double-check and populate ns for MS and MD template Signed-off-by: Danil-Grigorev <[email protected]> * Review: log messages Signed-off-by: Danil-Grigorev <[email protected]> --------- Signed-off-by: Danil-Grigorev <[email protected]>
Signed-off-by: Stefan Büringer [email protected]
Signed-off-by: Stefan Büringer [email protected]
… 4 updates Bumps the all-go-mod-patch-and-minor group with 2 updates in the / directory: [go.etcd.io/etcd/api/v3](https://github.com/etcd-io/etcd) and [go.etcd.io/etcd/client/v3](https://github.com/etcd-io/etcd). Bumps the all-go-mod-patch-and-minor group with 2 updates in the /hack/tools directory: [cloud.google.com/go/storage](https://github.com/googleapis/google-cloud-go) and [google.golang.org/api](https://github.com/googleapis/google-api-go-client). Bumps the all-go-mod-patch-and-minor group with 2 updates in the /test directory: [go.etcd.io/etcd/api/v3](https://github.com/etcd-io/etcd) and [go.etcd.io/etcd/client/v3](https://github.com/etcd-io/etcd). Updates `go.etcd.io/etcd/api/v3` from 3.5.16 to 3.5.17 - [Release notes](https://github.com/etcd-io/etcd/releases) - [Commits](etcd-io/etcd@v3.5.16...v3.5.17) Updates `go.etcd.io/etcd/client/v3` from 3.5.16 to 3.5.17 - [Release notes](https://github.com/etcd-io/etcd/releases) - [Commits](etcd-io/etcd@v3.5.16...v3.5.17) Updates `cloud.google.com/go/storage` from 1.46.0 to 1.47.0 - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/CHANGES.md) - [Commits](googleapis/google-cloud-go@spanner/v1.46.0...spanner/v1.47.0) Updates `google.golang.org/api` from 0.205.0 to 0.206.0 - [Release notes](https://github.com/googleapis/google-api-go-client/releases) - [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md) - [Commits](googleapis/google-api-go-client@v0.205.0...v0.206.0) Updates `go.etcd.io/etcd/api/v3` from 3.5.16 to 3.5.17 - [Release notes](https://github.com/etcd-io/etcd/releases) - [Commits](etcd-io/etcd@v3.5.16...v3.5.17) Updates `go.etcd.io/etcd/client/v3` from 3.5.16 to 3.5.17 - [Release notes](https://github.com/etcd-io/etcd/releases) - [Commits](etcd-io/etcd@v3.5.16...v3.5.17) --- updated-dependencies: - dependency-name: go.etcd.io/etcd/api/v3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-go-mod-patch-and-minor - dependency-name: go.etcd.io/etcd/client/v3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-go-mod-patch-and-minor - dependency-name: cloud.google.com/go/storage dependency-type: direct:production update-type: version-update:semver-minor dependency-group: all-go-mod-patch-and-minor - dependency-name: google.golang.org/api dependency-type: direct:production update-type: version-update:semver-minor dependency-group: all-go-mod-patch-and-minor - dependency-name: go.etcd.io/etcd/api/v3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-go-mod-patch-and-minor - dependency-name: go.etcd.io/etcd/client/v3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-go-mod-patch-and-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…bot/go_modules/all-go-mod-patch-and-minor-2c1c9845b1 🌱 Bump the all-go-mod-patch-and-minor group across 3 directories with 4 updates
🌱 Fix messages of conditions used for summaries and aggregations
…t-reconcile-delete 🌱 Rate-limit entire reconcileDelete
Signed-off-by: Stefan Büringer [email protected]
…v1beta2-machine-ready 🌱 Refine v1beta2 machine ready
…v1beta2-stale-deletion-messages 🌱 Refine v1beta2 stale deletion messages
Signed-off-by: Stefan Büringer [email protected]
…v1beta2-controlplanehealthy-condition 🌱 Refine v1beta2 ControlPlaneHealthy condition
…ait-timeout 🌱 Improve cluster deletion timeout message in e2e test framework
seperate taints template into its own template add parse taints method for converting taints config to toml add taints to BottlerocketSettingsInput add template parsing to node userdata generation account for multiple value:effect mappings in each taint key
Signed-off-by: Michael Chu <[email protected]>
Once the first etcd member is initialized, the machine controller has to update the secret with the address of the machine, so it can be used by other members to join during cluster creation. The etcdadm-bootstrap-provider changes this address into an etcd client URL before passing it in to the join command. Recent changes in etcdadm, and etcdadm-controller will allow passing in client URLs of all etcd members. So this commit changes the format of stored address for the first machine from an IP address to the etcd client URL. NOTE: This only happens once initially during cluster creation. We need to keep this Secret because after clusterctl move, the etcdCluster's Initialized condition needs to be set based on the existence of this Secret.
Signed-off-by: Vignesh Goutham Ganesh <[email protected]>
Host containers are a feature within BR that allows us to pull images without the need of having to bootstrap kuberentes. Such containers can be superpowered and user-data can be attached to each one of them. As such, this commit creates the `BottlerocketHostContainer` struct to allow the user to customize the those fields. Users can specify an arbitrary number of host containers in the `AdditionalHostContainers` field. This commit also does some refactoring around the templating system BR has to generate the TOML files. It generifies the host-container template to be reused as much as a user wants to. SIM: https://i.amazon.com/P66557529 cr: https://code.amazon.com/reviews/CR-71408825
…pdatable in webhook
…cd machine ready label
Signed-off-by: Ahree Hong <[email protected]>
Signed-off-by: Abhinav <[email protected]>
Signed-off-by: Ahree Hong <[email protected]>
Signed-off-by: Abhinav Pandey <[email protected]>
Signed-off-by: Ahree Hong <[email protected]>
Signed-off-by: Ahree Hong <[email protected]>
EKS-A uses haproxy 2.5 which errors if the maxconn value requires more FDs than allowed by the ulimit setting of docker. 100k maxconn is too high for the default ulimit on an al2 node.
* add support for custom cert bundles br * take in non base-64 encoded data for cert Signed-off-by: Ahree Hong <[email protected]>
Signed-off-by: Vignesh Goutham Ganesh <[email protected]>
Signed-off-by: Vignesh Goutham Ganesh <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #