Skip to content

Conversation

@uri-weisman
Copy link
Contributor

@uri-weisman uri-weisman commented Mar 14, 2024

We encountered an SDH ticket where a customer upgraded their EKS cluster to v1.25 and lost all their Pod Security Policy (PSP) findings because PSPs were removed in this version.
I don't believe we can claim to support all available EKS versions because our benchmark is not being updated, and we are likely to miss relevant findings.
It seems logical to tie our EKS support to the Kubernetes version we officially support. What do you think, @tinnytintin10?

Preview: KSPM FAQ

@uri-weisman uri-weisman requested a review from a team as a code owner March 14, 2024 08:03
@github-actions
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@mergify
Copy link
Contributor

mergify bot commented Mar 14, 2024

This pull request does not have a backport label. Could you fix it @uri-weisman? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • v7.x is the label to automatically backport to the 7.x branch.
  • v7./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@smriti0321
Copy link

@uri-weisman Thanks for starting this conversation, I agree to call out the specific versions we support in our docs, to help get this update could you please highlight the exact Kubernetes versions for our EKS support? cc @benironside

@uri-weisman
Copy link
Contributor Author

@smriti0321

could you please highlight the exact Kubernetes versions for our EKS support?

This problem arises from the CIS EKS benchmark v1.0.1, which does not specify the EKS versions to which the benchmark is applicable. For example, in the mentioned benchmark version, they refer to k8s resources (PSP) that are already being removed in the current version (v1.25).

The EKS benchmark implementation includes data collectors that are specific to the cloud provider and some that are shared with self-managed k8s, supporting v1.23.
Therefore, I suggest that we align our support with this version.

This means that we will publish that our supported EKS version is v1.23.The newer versions may work, but they might result in lost findings.

cc @tehilashn

Copy link
Contributor

@joepeeples joepeeples left a comment

Choose a reason for hiding this comment

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

🏝️

@benironside benironside merged commit 55e1037 into main Apr 11, 2024
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

# Conflicts:
#	docs/cloud-native-security/cspm-faq.asciidoc
#	docs/cloud-native-security/kspm-faq.asciidoc
mergify bot pushed a commit that referenced this pull request Apr 11, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

# Conflicts:
#	docs/cloud-native-security/cspm-faq.asciidoc
#	docs/cloud-native-security/kspm-faq.asciidoc
@uri-weisman uri-weisman deleted the docs_update branch April 14, 2024 05:11
benironside pushed a commit that referenced this pull request Apr 15, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
benironside pushed a commit that referenced this pull request Apr 15, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
benironside pushed a commit that referenced this pull request Apr 15, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
benironside pushed a commit that referenced this pull request Apr 15, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
benironside pushed a commit that referenced this pull request Apr 15, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
benironside pushed a commit that referenced this pull request Apr 15, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
benironside added a commit that referenced this pull request Apr 16, 2024
* update supported k8s version for eks

* applies update in other location

---------

Co-authored-by: Benjamin Ironside Goldstein <benjamin.ironside@elastic.co>
(cherry picked from commit 55e1037)

Co-authored-by: Uri Weisman <68195305+uri-weisman@users.noreply.github.com>
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants