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

Check ingress_controller fileset compatibility with newer versions #21198

Closed
andresrc opened this issue Sep 21, 2020 · 2 comments · Fixed by #21209
Closed

Check ingress_controller fileset compatibility with newer versions #21198

andresrc opened this issue Sep 21, 2020 · 2 comments · Fixed by #21209
Labels
Team:Platforms Label for the Integrations - Platforms team

Comments

@andresrc
Copy link
Contributor

According to the documentation, the ingress_controller fileset has been tested with version 0.28.0 of ingress-nginx.

However, there have been multiple additional releases (up to 3.x). We should check whether the fileset works with newer versions and document it.

@andresrc andresrc added the Team:Platforms Label for the Integrations - Platforms team label Sep 21, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@ChrsMark
Copy link
Member

ChrsMark commented Sep 22, 2020

Thanks for opening this @andresrc . The thing here is that versioning is a little bit tricky. Note that there is versions like 3.x named ingress-nginx-3.2.0 and versions like v0.35.0 named controller-v0.35.0.
3.2.0 is the helm chart version, in that chart is running ingress controller version 0.35.0.

The version we are interested in is just the controller version.
So we tested the fileset with 0.28.0 and now the latest version of the service is 0.35.0 means that we have not diverge so much. I will verify with this latest version and update the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Platforms Label for the Integrations - Platforms team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants