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

[Hubs] Clarify address space is for private networking only #1343

Open
flanakin opened this issue Feb 25, 2025 · 0 comments
Open

[Hubs] Clarify address space is for private networking only #1343

flanakin opened this issue Feb 25, 2025 · 0 comments
Labels
OKR: 2.3 Feedback Issues that are based on the top voted customer feedback Tool: FinOps hubs Data pipeline solution

Comments

@flanakin
Copy link
Collaborator

⚠️ Problem

Original comment:

Hi all. This option stopped my deployment, as under no circumstances would I want this template deploying vnets etc.

The .8 behaviour is not very clear during the deployment as the prefix is mandatory whether you select public or private.

The only message being "Address space for the workload. A /26 is required for the workload." - which isn't quite true if you select public.

Originally posted by @psilantropy in #1183

🛠️ Solution

Clarify that the address space is only applicable for private networking. Make it hidden when public is specified, if possible.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.
@flanakin flanakin added the Tool: FinOps hubs Data pipeline solution label Feb 25, 2025
@flanakin flanakin added this to the 2025-03 - March milestone Feb 25, 2025
@flanakin flanakin added the OKR: 2.3 Feedback Issues that are based on the top voted customer feedback label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OKR: 2.3 Feedback Issues that are based on the top voted customer feedback Tool: FinOps hubs Data pipeline solution
Projects
None yet
Development

No branches or pull requests

1 participant