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 docs for N-1 EKS-A version support #8357

Merged
merged 1 commit into from
Aug 1, 2024

Conversation

abhay-krishna
Copy link
Member

Adding docs to reflect the N-1 EKS-A version support policy.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@eks-distro-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from abhay-krishna. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@eks-distro-bot eks-distro-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 20, 2024
@abhay-krishna abhay-krishna changed the title Add docs for N-1 EKS-A version support WIP: Add docs for N-1 EKS-A version support Jun 20, 2024
@abhay-krishna abhay-krishna changed the title WIP: Add docs for N-1 EKS-A version support Add docs for N-1 EKS-A version support Jul 31, 2024
You can find details about each EKS Anywhere releases in the [EKS Anywhere release manifest.](https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml) The release manifest contains references to the corresponding bundle manifest for each EKS Anywhere version. Within the bundle manifest, you will find the components included in a specific EKS Anywhere version. The images running in your deployment use the same URI values specified in the bundle manifest for that component. For example, see the [bundle manifest](https://anywhere-assets.eks.amazonaws.com/releases/bundles/59/manifest.yaml) for EKS Anywhere version `v0.18.7`.

Starting in 2024, EKS Anywhere follows a 4-month release cadence for minor versions. EKS Anywhere has a 2-week cadence for patch versions. Common vulnerabilities and exposures (CVE) patches and bug fixes, including those for the supported Kubernetes versions, are included in the latest EKS Anywhere minor version (version N). If you are interested in patch support for EKS Anywhere N-1 versions, please upvote or comment on [EKS Anywhere GitHub Issue #7397.](https://github.com/aws/eks-anywhere/issues/7397)
You can find details about each EKS Anywhere releases in the [EKS Anywhere release manifest](https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml). The release manifest contains references to the corresponding bundle manifest for each EKS Anywhere version. Within the bundle manifest, you will find the components included in a specific EKS Anywhere version. The images running in your deployment use the same URI values specified in the bundle manifest for that component. For example, see the [bundle manifest](https://anywhere-assets.eks.amazonaws.com/releases/bundles/59/manifest.yaml) for EKS Anywhere version `v0.18.7`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: "You can find details about each EKS Anywhere release" ... not "releases"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets update to the latest manifest while we're at it

Copy link
Member

@csplinter csplinter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple nits but lgtm

Copy link

codecov bot commented Jul 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.52%. Comparing base (925b425) to head (91f93f6).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8357   +/-   ##
=======================================
  Coverage   73.52%   73.52%           
=======================================
  Files         578      578           
  Lines       36552    36552           
=======================================
  Hits        26876    26876           
  Misses       7955     7955           
  Partials     1721     1721           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@eks-distro-bot
Copy link
Collaborator

New changes are detected. LGTM label has been removed.

@abhay-krishna abhay-krishna merged commit 9e365b8 into aws:main Aug 1, 2024
7 of 8 checks passed
@abhay-krishna
Copy link
Member Author

/cherrypick release-0.20
/cherrypick release-0.19

@eks-distro-pr-bot
Copy link
Contributor

@abhay-krishna: new pull request created: #8560

In response to this:

/cherrypick release-0.20
/cherrypick release-0.19

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 kubernetes/test-infra repository.

@abhay-krishna
Copy link
Member Author

/cherrypick release-0.19

@eks-distro-pr-bot
Copy link
Contributor

@abhay-krishna: new pull request created: #8561

In response to this:

/cherrypick release-0.19

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 kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Documentation documentation size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants