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 for AKS HTTP Application Routing #1276

Closed
rlucioni opened this issue May 22, 2018 · 9 comments
Closed

Support for AKS HTTP Application Routing #1276

rlucioni opened this issue May 22, 2018 · 9 comments

Comments

@rlucioni
Copy link

The HTTP Application Routing add-on can be enabled through the Azure portal when deploying an AKS cluster. It would be great if enabling this was an option when creating new azurerm_kubernetes_cluster resources (e.g., via a Boolean argument like enable_http_application_routing).

@tombuildsstuff tombuildsstuff added enhancement upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR service/kubernetes-cluster labels May 22, 2018
@tombuildsstuff tombuildsstuff added this to the Future milestone May 22, 2018
@tombuildsstuff
Copy link
Contributor

hey @rlucioni

Thanks for opening this issue :)

We took a look into this recently and this is available in the new version of the AKS API - however there's no matching Swagger for that at this time. @dcaro was following up internally about getting this available - once that's done and a new version of the Azure SDK for Go is available - we can take a look at support this.

Thanks!

@rlucioni
Copy link
Author

Great, thanks @tombuildsstuff. Looking forward to seeing this supported.

@tombuildsstuff
Copy link
Contributor

To provide an update here, the Swagger for this has been merged: Azure/azure-rest-api-specs#3131

@rlucioni
Copy link
Author

rlucioni commented Jun 1, 2018

Thanks for the update @tombuildsstuff.

@TechyMatt
Copy link
Contributor

It looks like they've also now introduced the ability to get the name of the nodeResourceGroup (Azure/azure-rest-api-specs#3203). This would be incredibly useful as we can build a dependency and then go and configure permissions and tags post build. Any chance this can get implemented at the same time?

@lfshr
Copy link
Contributor

lfshr commented Jul 3, 2018

Related to #1434

@mb290 nodeResourceGroup addition is a much simpler one. @tombuildsstuff I can bundle up the nodeResourceGroup with #1479 if you like, it's a relatively small change.

@lfshr
Copy link
Contributor

lfshr commented Jul 5, 2018

@tombuildsstuff this functionality is provided by addonProfiles. I think we should move this alongside #1434

@tombuildsstuff
Copy link
Contributor

@lfshr 👍 closing this in favour of #1434

@tombuildsstuff tombuildsstuff removed the upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR label Jul 6, 2018
@tombuildsstuff tombuildsstuff modified the milestones: Future, Being Sorted Oct 25, 2018
@ghost
Copy link

ghost commented Mar 6, 2019

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants