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

HelmDeploy@0: Public FQDN #17818

Open
jkroepke opened this issue Feb 24, 2023 · 4 comments
Open

HelmDeploy@0: Public FQDN #17818

jkroepke opened this issue Feb 24, 2023 · 4 comments

Comments

@jkroepke
Copy link

jkroepke commented Feb 24, 2023

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

  • 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.

@github-actions
Copy link

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

@github-actions github-actions bot added the stale label Aug 23, 2023
@jkroepke
Copy link
Author

Hello

@github-actions github-actions bot removed the stale label Aug 23, 2023
Copy link

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

@github-actions github-actions bot added the stale label Feb 19, 2024
@jkroepke
Copy link
Author

Hello

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants