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

VMSS rolling update with Application Gateway #64

Open
dnetguru opened this issue Jun 24, 2019 · 5 comments
Open

VMSS rolling update with Application Gateway #64

dnetguru opened this issue Jun 24, 2019 · 5 comments

Comments

@dnetguru
Copy link

Is it possible to use rolling update policy with an Application Gateway instead of a load balancer?
It seems like the health probe in networkProfile has to be a load balancer health probe. Is there any way around this?

msrest.http_logger : {                                                                                                                                                           "error": {
    "details": [
      {
        "code": "InvalidJsonReferenceWrongType",
        "message": "Reference Id /subscriptions/xxxx-xxxxxx-xxxxx-xxxx-xxxxxx/resourceGroups/scaleset-test/providers/Microsoft.Network/applicationGateways/scaleset-test/probes/running-iis is referencing resource of a wrong type. The Id is expected to reference resources of type loadBalancers/probes. Path Properties.UpdateGroups[0].NetworkProfile.healthProbe."
      }
    ],
    "code": "InvalidRequestFormat",
    "message": "Cannot parse the request."
  }
}
@jonesbusy
Copy link

Hi,

We have the same use case here

A workaround could be to use an internal Load Balancer beween the Application Gateway and the VMSS. But the side effect of this is that we cannot use anymore the cookie based session affinit of the Application Gateway

Regards,

@Jedylemindee
Copy link

Hi, any update on this ?

@nocticdr
Copy link

Hi, this is really a blocker for us right now as we are using terraform for deployments. It's been many months now that we been using manual upgrade mode because of this. In our case, we have to use AGWs and can't use ALBs. Is there any way to use the healthRepairExtension ID?

@Dmitry1987
Copy link

It seems like at the moment there's no way to do a rolling deployment with graceful termination (lifecycle hook to instance that's about to be terminated), by native Azure means. I'm stuck at the same issue, and Azure support can't understand what I'm asking for, when I talk about rolling-deployments and graceful termination... If they're not aware of such features I guess they don't exist :((( .. been trying to replicate my AWS infra in Azure...

@Dmitry1987
Copy link

Using raw VMs and VMSS capacity to host our own Kubernetes on it, seems the optimal way to deploy and manage services the way we want. I would recommend that path.

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

No branches or pull requests

5 participants