You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature? Type: Feature
Enter Task Name: HelmDeploy
Environment
Server - Azure Pipelines
Agent - Private
Issue Description
By default, private cluster have an public FQDN. Its possible to use the public fqdn by running --public-fqdn on aks az get-credentials. Currently, the HelmDeploy Task does not support this.
Our private runner is in a different subnet and the private dns zone is not connected.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Feature
Enter Task Name: HelmDeploy
Environment
Issue Description
By default, private cluster have an public FQDN. Its possible to use the public fqdn by running --public-fqdn on aks az get-credentials. Currently, the HelmDeploy Task does not support this.
Our private runner is in a different subnet and the private dns zone is not connected.
The text was updated successfully, but these errors were encountered: