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.

Sign up for GitHub

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

Jump to bottom

[TKO vSphere] Recommend network per boundary not cluster #19

Open
z4ce opened this issue Nov 10, 2021 · 1 comment
Open

[TKO vSphere] Recommend network per boundary not cluster #19

z4ce opened this issue Nov 10, 2021 · 1 comment
Assignees
@manishjha86
Labels
enhancement New feature or request
Milestone
TKO RA 1.6

Comments

@z4ce
Copy link
Contributor

z4ce commented Nov 10, 2021

Per conversations with field, we should stop recommending a network per cluster for TKG. Instead, we should recommend a network per boundary. For example, a network for general internal apps, PCI apps, DMZ apps, etc
@ghost ghost assigned nithink-vmw and unassigned JefeDavis Jan 7, 2022
@craigtracey craigtracey transferred this issue from another repository Jan 18, 2022
@manishjha86 manishjha86 added the RA-3 RA 3.0 Release Targeted Tickets label Jun 1, 2022
@manishjha86
Copy link
Contributor

This will be addressed in RA 3.0

@srivar srivar added this to the TKO RA 1.6 milestone Jun 6, 2022
@srivar srivar removed the RA-3 RA 3.0 Release Targeted Tickets label Jun 6, 2022
@smuthukumar-vmw smuthukumar-vmw added the enhancement New feature or request label Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manishjha86 manishjha86

Labels
enhancement New feature or request
Projects
None yet
Milestone
TKO RA 1.6
Development

No branches or pull requests
6 participants
@z4ce @srivar @JefeDavis @manishjha86 @nithink-vmw @smuthukumar-vmw