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

fix(scaleway): only use absolute CNAMEs #1859

Merged
merged 1 commit into from
Jan 28, 2021

Conversation

Sh4d1
Copy link
Member

@Sh4d1 Sh4d1 commented Nov 9, 2020

Signed-off-by: Patrik Cyvoct patrik@ptrk.io

Description

Scaleway DNS allow "relative" CNAME without a trailing dot, this PR ensures we only uses absolute CNAMEs

Checklist

  • Unit tests updated
  • [NA] End user documentation updated

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 9, 2020
@Sh4d1
Copy link
Member Author

Sh4d1 commented Nov 10, 2020

/assign @njuettner

@seanmalloy
Copy link
Member

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 12, 2020
Copy link
Contributor

@Raffo Raffo left a comment

Choose a reason for hiding this comment

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

Code looks good, apart two comments that IMO need to be dropped.

I'm not sure about how scaleway works though, so any 👍 that the community would be good to get an understanding if this works.

provider/scaleway/scaleway.go Outdated Show resolved Hide resolved
provider/scaleway/scaleway.go Outdated Show resolved Hide resolved
@Sh4d1
Copy link
Member Author

Sh4d1 commented Jan 7, 2021

@Raffo sorry completely missed your comments 😅 comments removed, tested works all good! Could we merge this? I also need to bump the API version used, which I'd prefer to do once this one is merged 😄

@Raffo
Copy link
Contributor

Raffo commented Jan 27, 2021

@Sh4d1 yes we can merge that! Can you resolve the conflicts?

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 27, 2021
Signed-off-by: Patrik Cyvoct <patrik@ptrk.io>
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 28, 2021
@Sh4d1
Copy link
Member Author

Sh4d1 commented Jan 28, 2021

@Raffo done 😄

@Raffo
Copy link
Contributor

Raffo commented Jan 28, 2021

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 28, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Raffo, Sh4d1

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 28, 2021
@k8s-ci-robot k8s-ci-robot merged commit ae10545 into kubernetes-sigs:master Jan 28, 2021
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants