Cluster-api-provider-aws: Running clusterctl with existing infra generates a bad kubeconfig

Created on 31 Oct 2018 · 7Comments · Source: kubernetes-sigs/cluster-api-provider-aws

/kind bug

What steps did you take and what happened:
I created a cluster and then created another cluster. The kubeconfig gave me this error:

Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes")

What did you expect to happen:
I expected kubeconfig to connect to my new cluster

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

Cluster-api-provider-aws version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

kinbug prioritimportant-longterm

Source

chuckha

Most helpful comment

@randomvariable sounds good, there is a temporary workaround to move the cert/key to config rather than status, but I think SSM provides a better long term story here.

detiber on 5 Nov 2018

👍2

All 7 comments

it does however reuse my old vpc but creates a new machine. Maybe this is expected but it doesn't behave very well.

chuckha on 31 Oct 2018

I suspect part of this may be because we are storing the cert material in the status, which is wiped when the cluster-api components are pivoted.

detiber on 31 Oct 2018

Yup. Should I complete the SSM Parameter store proposal? I think the implementation was pretty trivial when I last did it.

randomvariable on 5 Nov 2018

@randomvariable sounds good, there is a temporary workaround to move the cert/key to config rather than status, but I think SSM provides a better long term story here.

detiber on 5 Nov 2018

👍2

Is this fixed now that #355 is merged?

vincepri on 9 Nov 2018

Closing this as it should be fixed in #355, feel free to reopen if not.
/close

vincepri on 19 Nov 2018

@vincepri: Closing this issue.

In response to this:

Closing this as it should be fixed in #355, feel free to reopen if not.
/close

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.