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

Updates to fix DNS error for compact cluster worker nodes #3425

Merged

Conversation

varungur
Copy link
Contributor

@varungur varungur commented Apr 7, 2020

@sdodson - Please review these changes.

@sdodson
Copy link
Member

sdodson commented Apr 7, 2020

/test e2e-metal

@@ -184,7 +184,20 @@ resource "aws_route53_record" "ctrlp_int" {
records = ["${local.ctrp_records}"]
}

resource "aws_route53_record" "apps" {
resource "aws_route53_record" "apps_noworker" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something we might want to look at, is

  • making sure all the nodes, control-plane + compute become part of the *.app DNS
  • use route53 health checks to make sure only active nodes with ingress routers become active as DNS response.

Copy link
Contributor Author

@varungur varungur Apr 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll talk to you on Monday to understand your comments and resolve it. I'm able to successfully bring up a cluster which has both control plane and workers running on the same hosts.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The suggestion was only a recommendation. this is not important and only for future work

/approve

@sdodson
Copy link
Member

sdodson commented Apr 8, 2020

/test e2e-metal

1 similar comment
@sdodson
Copy link
Member

sdodson commented Apr 10, 2020

/test e2e-metal

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 13, 2020
@varungur
Copy link
Contributor Author

/test e2e-metal

@abhinavdahiya
Copy link
Contributor

/retest

@sdodson
Copy link
Member

sdodson commented Apr 14, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

@varungur: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-openstack 74d049f link /test e2e-openstack
ci/prow/e2e-aws-scaleup-rhel7 74d049f link /test e2e-aws-scaleup-rhel7

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 1f9fd8e into openshift:master Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants