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

Update k8s Ingress to v1 and add optional ingressClassName #675

Merged
merged 4 commits into from
Apr 8, 2022

Conversation

andytson-inviqa
Copy link
Contributor

Needed for k8s 1.22, supported since 1.19, and requires ArgoCD > 1.8

@andytson-inviqa andytson-inviqa added enhancement New feature or request harness-all Changes required to all harness directories labels Apr 1, 2022
@andytson-inviqa andytson-inviqa added this to the 1.3.0 milestone Apr 1, 2022
@andytson-inviqa andytson-inviqa changed the title Update k8s Ingress to v1 Update k8s Ingress to v1 and add optional ingressClassName Apr 6, 2022
kierenevans
kierenevans previously approved these changes Apr 8, 2022
@andytson-inviqa
Copy link
Contributor Author

Fixed the upgrade notes conflict in rebase

@andytson-inviqa andytson-inviqa merged commit b0fef09 into 1.3.x Apr 8, 2022
@andytson-inviqa andytson-inviqa deleted the feature/ingress-v1 branch April 8, 2022 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request harness-all Changes required to all harness directories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants