Open VardyNg opened 3 weeks ago
Bug Description
Steps to Reproduce
Expected Behavior
Should direct to the correct page in Kubernetes Document
Actual Behavior
Redirected to 404 Page not found
Regression Was the functionality working correctly in a previous version ? [Yes / No] If yes, specify the last version where it worked as expected
Current Workarounds
No workarounds available
Environment
helm ls -A | grep -i aws-load-balancer-controller
helm -n <controllernamespace> get values <helmreleasename>
kubectl -n <controllernamespace> describe deployment aws-load-balancer-controller
kubectl describe ingressclasses
kubectl -n <appnamespace> describe ingress <ingressname>
kubectl -n <appnamespace> describe svc <servicename>
Possible Solution (Optional)
Contribution Intention (Optional)
Additional Context
Thank you for reporting the broken link. I see you are willing to submit a PR. We welcome community contributions!
Bug Description
Steps to Reproduce
Expected Behavior
Should direct to the correct page in Kubernetes Document
Actual Behavior
Redirected to 404 Page not found
Regression Was the functionality working correctly in a previous version ? [Yes / No] If yes, specify the last version where it worked as expected
Current Workarounds
No workarounds available
Environment
helm ls -A | grep -i aws-load-balancer-controller
helm -n <controllernamespace> get values <helmreleasename>
kubectl -n <controllernamespace> describe deployment aws-load-balancer-controller
kubectl describe ingressclasses
kubectl -n <appnamespace> describe ingress <ingressname>
kubectl -n <appnamespace> describe svc <servicename>
Possible Solution (Optional)
Contribution Intention (Optional)
Additional Context