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

Ingress Class: Align to upstream. #377

Merged
merged 2 commits into from
Nov 10, 2022

Conversation

Gacko
Copy link
Member

@Gacko Gacko commented Nov 10, 2022

Tests on workload clusters (not always required)

For changes in the chart, chart templates, and ingress controller container images, I executed the following tests
to verify them working in live enviromnents:

Test / Provider AWS Azure KVM
Upgrade from previous version
Existing Ingress resources are reconciled correctly
Fresh install
Fresh Ingress resources are reconciled correctly

Testing was done using hello-world-app.

Hint for KVM:

kubectl port-forward -n kube-system svc/nginx-ingress-controller-app 8080:80
ingress_domain=host.configured.in.ingress; curl --connect-to "$ingress_domain:80:127.0.0.1:8080" "http://$ingress_domain" -v

@Gacko Gacko requested a review from a team as a code owner November 10, 2022 15:40
@Gacko Gacko force-pushed the feature/upstream-alignment/ingress-class branch from 00d5e96 to 099acf1 Compare November 10, 2022 15:44
@Gacko Gacko enabled auto-merge (squash) November 10, 2022 15:48
@Gacko Gacko disabled auto-merge November 10, 2022 16:36
@Gacko Gacko merged commit 2b976c7 into main Nov 10, 2022
@Gacko Gacko deleted the feature/upstream-alignment/ingress-class branch November 10, 2022 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant