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

MIssing resources for policy loadbalancers (profiles and monitors) #1240

Open
martinrohrbach opened this issue Jun 26, 2024 · 3 comments
Open
Assignees
Milestone

Comments

@martinrohrbach
Copy link
Contributor

Is your feature request related to a problem? Please describe.

In order to provision loadbalancers in policy mode there are still a number of resources missing and can only be imported after manually creating them:

nsxt_policy_lb_app_profile
nsxt_policy_lb_client_ssl_profile
nsxt_policy_lb_monitor
nsxt_policy_lb_persistence_profile
nsxt_policy_lb_server_ssl_profile

Since the migration to policy gets more and more urgent, are there any plans to add those soon?

Describe the solution you'd like

Resources for loadbalancer profiles and monitors.

Describe alternatives you've considered

No response

Additional context

No response

@2ez4szliu
Copy link
Contributor

Hi @martinrohrbach
For the resources that you mentioned in the issue, the ones that have been implemented are:
nsxt_policy_lb_http_application_profile
nsxt_policy_lb_client_ssl_profile
nsxt_policy_lb_udp_monitor_profile(also for tcp, http, https, icmp, passive)

We still need to implement policy resource for lb_persistence_profile, lb_server_ssl_profile

@martinrohrbach
Copy link
Contributor Author

@2ez4szliu
My bad, I wasn't checking the "Beta" section, sorry :(

@salv-orlando salv-orlando added this to the v3.7.0 milestone Aug 9, 2024
@salv-orlando
Copy link
Member

Adding this issue to 3.7.0 milestone to cover the missing LB resources.

@salv-orlando salv-orlando self-assigned this Aug 9, 2024
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

3 participants