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

Kubernetes 1.29 compatibility #228

Closed
joebowbeer opened this issue Jan 17, 2024 · 8 comments
Closed

Kubernetes 1.29 compatibility #228

joebowbeer opened this issue Jan 17, 2024 · 8 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@joebowbeer
Copy link

According to the docs, lacework agent is not compatible with Kubernetes 1.29

https://docs.lacework.net/onboarding/deploy-on-kubernetes#supported-kubernetes-environments

The current version appears to be using the following APIs that were removed in 1.29:

  • /apis/flowcontrol.apiserver.k8s.io/v1beta2/flowschemas
  • /apis/flowcontrol.apiserver.k8s.io/v1beta2/prioritylevelconfigurations
@catz-lw
Copy link
Collaborator

catz-lw commented Jan 17, 2024

Hi Joe. Thanks for the report. I'm curious, how are you determining which deprecated APIs the agent is using?

@vglen
Copy link

vglen commented Jan 17, 2024

Hi Joe. Thanks for the report. I'm curious, how are you determining which deprecated APIs the agent is using?

It's listed in the EKS console under upgrade insights from 1.28 to 1.29. Basically the api moves to beta3. It's listed as a stop version serving in 1.29.

/apis/flowcontrol.apiserver.k8s.io/v1beta3/flowschemas
/apis/flowcontrol.apiserver.k8s.io/v1beta3/prioritylevelconfigurations

@treyhyde
Copy link

I'd hate to me-too this but it's everyone. Lacework is blocking our upgrade to 1.29 and this has been a warning for a while.

@vglen
Copy link

vglen commented Jan 24, 2024

I think the calls are from the app and not in the chart. I upgraded from 6.6 to 6.11 today and waiting for EKS insights checks. I'll report back.

@vglen
Copy link

vglen commented Jan 25, 2024

I think the calls are from the app and not in the chart. I upgraded from 6.6 to 6.11 today and waiting for EKS insights checks. I'll report back.

The checks did not clear and ran after upgrading to 6.11 on numerous 1.28 clusters.

@catz-lw
Copy link
Collaborator

catz-lw commented Feb 27, 2024

@vglen and @treyhyde It is safe to upgrade the cluster agent. The cluster agent will not use the removed APIs if running on k8s 1.29. Future versions of the cluster agent will exclude deprecated APIs from this scraping to avoid the warnings.

Details:

The agent doesn't require the use of the deprecated and removed APIs, but it will query whatever APIs are present in a given version of Kubernetes. The agent asks k8s "what APIs exist right now" and then queries all of them. The warnings are a heuristic, and do not mean "this product will break" but rather than "this product might break".

@catz-lw catz-lw pinned this issue Feb 27, 2024
@catz-lw catz-lw self-assigned this Feb 27, 2024
@catz-lw catz-lw added the documentation Improvements or additions to documentation label Feb 27, 2024
@catz-lw catz-lw closed this as completed Feb 27, 2024
@joebowbeer
Copy link
Author

@catz-lw Can you update the supported versions?

https://docs.lacework.net/onboarding/deploy-on-kubernetes

@catz-lw
Copy link
Collaborator

catz-lw commented Feb 27, 2024

@catz-lw Can you update the supported versions?

https://docs.lacework.net/onboarding/deploy-on-kubernetes

@joebowbeer Yes, sorry for the confusion, official documentation will land soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants