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

Support AKS Application Gateway Ingress Controller #11357

Closed
ghost opened this issue Apr 16, 2021 · 6 comments · Fixed by #11984
Closed

Support AKS Application Gateway Ingress Controller #11357

ghost opened this issue Apr 16, 2021 · 6 comments · Fixed by #11984

Comments

@ghost
Copy link

ghost commented Apr 16, 2021

This issue was originally opened by @jkroepke as hashicorp/terraform#28418. It was migrated here as a result of the provider split. The original body of the issue is below.


https://docs.microsoft.com/en-us/azure/application-gateway/ingress-controller-overview

Hi,

recently it's possible to use an Application Gateway as Ingress Controller for AKS.

This functionally is available as aks addon called "ingress-azure". The Azure CLI expose multiple parameters around AGIC:

az aks create --help
...
Application Gateway Arguments
    --appgw-id                                : Resource Id of an existing Application Gateway to
                                                use with AGIC. Use with ingress-azure addon.
    --appgw-name                              : Name of the application gateway to create/use in the
                                                node resource group. Use with ingress-azure addon.
    --appgw-subnet-cidr                       : Subnet CIDR to use for a new subnet created to
                                                deploy the Application Gateway. Use with ingress-
                                                azure addon.
    --appgw-subnet-id                         : Resource Id of an existing Subnet used to deploy the
                                                Application Gateway. Use with ingress-azure addon.
    --appgw-watch-namespace                   : Specify the namespace, which AGIC should watch. This
                                                could be a single string value, or a comma-separated
                                                list of namespaces.

Please note, the AGIC is something different then the "HTTP Application Routing" option.

@jkroepke
Copy link
Contributor

This issue is a duplicate to #7384

@aristosvo
Copy link
Collaborator

This functionality is added in #11376, issue can be closed.

@naman
Copy link

naman commented May 27, 2021

Thanks! Can --appgw-name be supported through terraform? I read the documentation for 2.60.0 and it's currently not supported.

@aristosvo
Copy link
Collaborator

@naman I submitted PR #11984 to support your needs 🎉

The best way to ask for a feature would be in general to submit an issue with a feature request 😉

@mbfrahry mbfrahry added this to the v2.62.0 milestone Jun 1, 2021
@ghost
Copy link
Author

ghost commented Jun 4, 2021

This has been released in version 2.62.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.62.0"
}
# ... other configuration ...

@github-actions
Copy link

github-actions bot commented Jul 5, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants