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

feat: (IAC-687) Upgrade Ingress-nginx to v1.3.0 to support K8s 1.24 #288

Merged
merged 2 commits into from
Aug 29, 2022

Conversation

riragh
Copy link
Member

@riragh riragh commented Aug 26, 2022

Changes:

To support K8s 1.24, update Ingress NGINX Controller to v1.3.0 (Chart version 4.2.3)

Tests:

Verified following scenarios, see the internal ticket for details.

  1. Viya4 deployment with K8s v1.24.0
  2. Viya4 deployment with default K8s v1.23.8

@riragh riragh added the enhancement New feature or request label Aug 26, 2022
@riragh riragh self-assigned this Aug 26, 2022
@riragh riragh marked this pull request as ready for review August 27, 2022 01:50
Copy link
Member

@thpang thpang left a comment

Choose a reason for hiding this comment

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

LGTM

@thpang
Copy link
Member

thpang commented Aug 28, 2022

Added Changelog link for version validation.

Copy link
Member

@dhoucgitter dhoucgitter left a comment

Choose a reason for hiding this comment

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

lgtm

@riragh riragh merged commit 6a3725d into staging Aug 29, 2022
@riragh riragh deleted the IAC-687 branch August 29, 2022 14:27
riragh added a commit that referenced this pull request Aug 29, 2022
…288)

* feat: (IAC-687): Upgraded Ingress-nginx to v1.3.0 to support K8s 1.24

* feat: (IAC-687): reverting the K8s version back to default v1.23.8
@riragh riragh mentioned this pull request Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants