We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No PTR records gets configured for floating IPs configured with module
Can be configured using parameter reverse_ptr
vshn-lbaas-cloudscale
The text was updated successfully, but these errors were encountered:
Suggestions for names:
api.${var.node_name_suffix}
cname.${var.node_name_suffix}
egress.${var.node_name_suffix}
Sorry, something went wrong.
Router VIP: cname.${var.node_name_suffix}
ingress.${var.node_name_suffix}?
ingress.${var.node_name_suffix}
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)
apps.${var.node_name_suffix}
Successfully merging a pull request may close this issue.
No PTR records gets configured for floating IPs configured with module
Can be configured using parameter reverse_ptr
Acceptance Criteria
vshn-lbaas-cloudscale
The text was updated successfully, but these errors were encountered: