update doc for ssh key creation

[jichenjc]

ssh key is not needed anymore ...

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:

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jichenjc

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:

• OWNERS [jichenjc]

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

[jichenjc]

@sbueringer ,maybe you can add how to create CA in doc as well? how CA is created manually is something we need tell customer

[sbueringer]

@sbueringer ,maybe you can add how to create CA in doc as well? how CA is created manually is something we need tell customer

Yup I can document it. Just to clarify. In my opinion the easiest way to create a CA is:

• deploy Cluster CRD
• wait 1-2 minutes
• kubectl get cluster -o json | jq '.spec....CaCert' | base64 -d

Because the cluster actuator creates all CAs for us.

[jichenjc]

@sbueringer ,maybe you can add how to create CA in doc as well? how CA is created manually is something we need tell customer

Yup I can document it. Just to clarify. In my opinion the easiest way to create a CA is:

• deploy Cluster CRD
• wait 1-2 minutes
• kubectl get cluster -o json | jq '.spec....CaCert' | base64 -d

Because the cluster actuator creates all CAs for us.

fully agree, I don't know whether user want to use their own CA instead of created one... at least we can tell them auto create is preferred (??) and tell them how to create if they want... thanks

[sbueringer]

@sbueringer ,maybe you can add how to create CA in doc as well? how CA is created manually is something we need tell customer

Yup I can document it. Just to clarify. In my opinion the easiest way to create a CA is:

• deploy Cluster CRD
• wait 1-2 minutes
• kubectl get cluster -o json | jq '.spec....CaCert' | base64 -d

Because the cluster actuator creates all CAs for us.

fully agree, I don't know whether user want to use their own CA instead of created one... at least we can tell them auto create is preferred (??) and tell them how to create if they want... thanks

And with create your own you mean a few openssl commands to generate the ca and a private key and how to put them into the Cluster CRD, right?

[jichenjc]

yes,that's my asking about.. thanks

[sbueringer]

/lgtm

Okay no problem. I'll open a PR for the CA doc