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 PTR records for cloudscale floating IPs #12

Closed
54nd20 opened this issue Oct 29, 2021 · 3 comments · Fixed by #21
Closed

Missing PTR records for cloudscale floating IPs #12

54nd20 opened this issue Oct 29, 2021 · 3 comments · Fixed by #21
Labels
enhancement New feature or request

Comments

@54nd20
Copy link
Member

54nd20 commented Oct 29, 2021

No PTR records gets configured for floating IPs configured with module

Can be configured using parameter reverse_ptr

Acceptance Criteria

@simu simu added the enhancement New feature or request label Oct 29, 2021
@simu
Copy link
Member

simu commented Dec 2, 2021

Suggestions for names:

  • API VIP: api.${var.node_name_suffix}
  • Router VIP: cname.${var.node_name_suffix}
  • NAT VIP: egress.${var.node_name_suffix}

@tobru
Copy link
Member

tobru commented Dec 2, 2021

Router VIP: cname.${var.node_name_suffix}

ingress.${var.node_name_suffix}?

@simu
Copy link
Member

simu commented Dec 2, 2021

Router VIP: cname.${var.node_name_suffix}

ingress.${var.node_name_suffix}?

or apps.${var.node_name_suffix} so it matches an existing DNS record, depends a bit on what we choose to do in OCP-301 (internal)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants