Add support for latest k8s versions#29575
Conversation
Signed-off-by: chrismark <chrismarkou92@gmail.com>
|
Pinging @elastic/integrations (Team:Integrations) |
|
This pull request does not have a backport label. Could you fix it @ChrsMark? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
|
/test |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
We can discuss this in a separate issue. But on the top of my head I believe we should drop support for k8s versions that kubernetes has also dropped support. |
What does this PR do?
This PR adds support for latest k8s versions, v1.22 and v1.23.
We also need to consider dropping support for older versions that k8s does not support based on https://endoflife.date/kubernetes and https://kubernetes.io/releases/.
@MichaelKatsoulis @tetianakravchenko @jsoriano I would love your thoughts on this one. I can create follow up issues for this to discuss it there instead of blocking this one.
This came up after dealing with failures at #29572 since the
CronjobAPI move tobatch/v1at 1.21 and hence tests are failing for k8s version pior to 1.20.elastic-package: elastic/elastic-package#634
integrations: elastic/integrations#2372