problem with SSL redirection in AGIC in a AKS

Question

problem with SSL redirection in AGIC in a AKS

Anonymous

I have problem with SSL redirection in AGIC in a AKS. I have same setup for dev and qa but qa wont work. i get this error in the ingress pod for qa: E0102 14:19:26.569393 1 requestroutingrules.go:272] Will not attach default redirect to rule; SSL Redirect does not exist: and for dev i get this: I0102 14:19:26.565614 1 redirects.go:44] Created redirection configuration sslr-fl-5c04e9370b9642cdf7ba97c7ce4c0b8a for ([hostname],443); not yet linked to a routing rule.
Anyone has an idea?

Cristian Gatjens 716 Reputation points Microsoft Employee

2023-01-09T15:16:55.43+00:00

Hello @Anonymous ,

Thank you for reaching out & I hope you are doing well.

This might require additional details to fully understand what is causing our issue:

What version of AGIC are you using? You can run "kubectl describe <ingress-pod>"
Is the same version of AGIC running on DEV and QA?
Can you please provide the spec section of your Ingress resource?

As a troubleshooting step, please restart the AGIC pod by scaling down and up the deployment and check if issue is gone.

Thanks!
srbhatta-MSFT 8,586 Reputation points Microsoft Employee

2023-01-16T13:17:46.9333333+00:00

Hello @Anonymous

Just checking in if below answer helped. If it did, then please don't forget to Accept as answer and Upvote so that it can help others in the community looking for help on similar queries. For any queries, feel free to reach back to us.

What is the importance of accepting answers in case they helped you:-

You as original poster by accepting answers will be helping other community members in finding the appropriate solutions in an effective way.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 answer

Your answer

Cristian Gatjens 716 Reputation points Microsoft Employee

2023-01-09T15:16:55.43+00:00

Hello @Anonymous ,

Thank you for reaching out & I hope you are doing well.

This might require additional details to fully understand what is causing our issue:

What version of AGIC are you using? You can run "kubectl describe <ingress-pod>"
Is the same version of AGIC running on DEV and QA?
Can you please provide the spec section of your Ingress resource?

As a troubleshooting step, please restart the AGIC pod by scaling down and up the deployment and check if issue is gone.

Thanks!
srbhatta-MSFT 8,586 Reputation points Microsoft Employee

2023-01-16T13:17:46.9333333+00:00

Hello @Anonymous

Just checking in if below answer helped. If it did, then please don't forget to Accept as answer and Upvote so that it can help others in the community looking for help on similar queries. For any queries, feel free to reach back to us.

What is the importance of accepting answers in case they helped you:-

You as original poster by accepting answers will be helping other community members in finding the appropriate solutions in an effective way.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Hello @Anonymous , Welcome to Microsoft QnA.

The issue you're experiencing with SSL redirection in Azure Application Gateway Ingress Controller (AGIC) in an Azure Kubernetes Service (AKS) cluster seems to be related to the configuration of your SSL redirect.

The first error message you provided, "Will not attach default redirect to rule; SSL Redirect does not exist," suggests that AGIC is unable to find an SSL redirect configuration for the ingress rule in question. This could be because the SSL redirect configuration is not present or is not properly configured.

The second error message "Created redirection configuration sslr-fl-5c04e9370b9642cdf7ba97c7ce4c0b8a for ([hostname],443); not yet linked to a routing rule." indicates that it has created the redirection configuration, but it is not yet linked to a routing rule.

It might be the case that the setup of the QA environment is different from the Dev environment and that's why the SSL redirection is not working. To debug this further, you can check and compare the AGIC configuration between the dev and qa environment. Specifically you should look at the configmap, check the values of the variables. Also verify the ingress configuration, that the same annotations and rules are being used for dev and qa. Additionally, you can check the Application Gateway and the listener for ssl redirections

Another possibility is that, you may have configure SSL Redirect different in dev and qa, try to verify that you are configuring ssl redirect in the same way for dev and qa.

Please let me know if you have any questions or need more information on this. You could also share the YAML manifests so that we can check and help you further.

Please accept as answer and upvote if the above information is helpful.

Share via

problem with SSL redirection in AGIC in a AKS

1 answer

Your answer