-
Notifications
You must be signed in to change notification settings - Fork 0
Pr implement reconcile certs #1
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
Conversation
This patch adds MachineDeployment template as in cluster-api-provider-aws.
per discussion , deployment has sideeffect such as potential race condition, so need switch to statefulset.
centos generate has some issue, missed commands=>files changes
| type KeyPair struct { | ||
| // base64 encoded cert and key | ||
| Cert []byte `json:"cert"` | ||
| Key []byte `json:"key"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consider to add omitempty here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
|
||
| // ReconcileCertificates generate certificates if none exists. | ||
| func (s *Service) ReconcileCertificates(clusterName string, clusterProviderSpec *v1alpha1.OpenstackClusterProviderSpec) error { | ||
| if !clusterProviderSpec.CAKeyPair.HasCertAndKey() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from code, looks like you are trying to generate those keys? if it's generated, then how do you store them and reuse? looks to me the Spec are the desired state but if you didn't give key at beginning, it's not desired state?? just curious ..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll move this PR and your comment over to the kubernetes-sigs repo now that the first PR is merged :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
upgrade klog from 0.1 to 0.3 to avoid no log issue
* factored out services These changes are heavily inspired by CAPA. They should improve the structure of the code for the upcoming addition of multi-node control plane support. * fix tests
This is heavily inspired bei CAPA. We now reconcile and store certificates in the Cluster CRD. Thus it's possible to distribute the same CAs over all control plane nodes (as soon as multi-node control plane supported is implemented). We also don't have to ssh on the/a control plane node to get a valid kubeconfig. We now can just generate one from the CA.
… controllerClient This enables us to run the controller outside the Workload Cluster, e.g. in a Management Cluster.
Now it's possible to use a local userdata folder. This is mostly useful for development to avoid updating the user data Secrets all the time.
bb70c66 to
d0bb419
Compare
|
Moved to kubernetes-sigs#394 |
* Makefile: add GOPROXY to docker-build build-arg * add go version for running go env GOPROXY in Makefile * add caas owners, simplify PR template * use caas specific version for GIT_VERSION * use mirrored golang image * add kore team as owners * update README * use Go 1.15.8 from Harbor registry
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: