Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Fix the SAN for non-us-east-1 AWS regions #201

Merged
merged 1 commit into from Jan 6, 2017

Conversation

ankon
Copy link
Contributor

@ankon ankon commented Jan 5, 2017

@codecov-io
Copy link

codecov-io commented Jan 5, 2017

Current coverage is 68.99% (diff: 100%)

Merging #201 into master will not change coverage

@@             master       #201   diff @@
==========================================
  Files             4          4          
  Lines          1132       1132          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits            781        781          
  Misses          262        262          
  Partials         89         89          

Powered by Codecov. Last update 2b29fc3...1af3cce

@mumoshu
Copy link
Contributor

mumoshu commented Jan 6, 2017

Good catch! Thanks for your contribution @ankon 👍

For anyone interested, kube-aws does utilize these SANs in https://github.com/coreos/kube-aws/blob/master/config/config.go#L541-L547
This documentation fix will save users who wants to bring their own certs.

@mumoshu mumoshu merged commit 966390f into kubernetes-retired:master Jan 6, 2017
kylehodgetts pushed a commit to HotelsDotCom/kube-aws that referenced this pull request Mar 27, 2018
Fix the SAN for non-us-east-1 AWS regions
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants