openstack/magnum
Code Issues Proposed changes

Update ca related magnum comands to osc

Browse Source 
After merging https://review.openstack.org/#/c/503952
update the according documentation to walk towards
deprecation of the magnum client
In addition, update old reference to bay in cluster commands.

Change-Id: Idf316f93dbc897ea0558da9b26a349644d4b98cf
Partially-Implements: blueprint deprecate-magnum-client
This commit is contained in:
Daniel Abad 2018-02-23 15:09:36 +00:00
parent f4267405cc
commit a015193025
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/user/index.rst
View File

@ -1792,7 +1792,7 @@ And the artifacts are placed in the directory specified::
You can now use the native client to interact with the COE.
The variables and artifacts are unique to the cluster.
The parameters for 'bay-config' are as follows:
The parameters for 'coe cluster config' are as follows:
--dir \<dirname\>
Directory to save the certificate and config files.
@ -1866,20 +1866,20 @@ Signed Certificate
Now that you have your client CSR, you can use the Magnum CLI to
send it off to Magnum to get it signed::
magnum ca-sign --cluster secure-k8s-cluster --csr client.csr > cert.pem
openstack coe ca sign secure-k8s-cluster client.csr > cert.pem
Certificate Authority
The final artifact you need to retrieve is the CA certificate for
the cluster. This is used by your native client to ensure you are only
communicating with hosts that Magnum set up::
magnum ca-show --cluster secure-k8s-cluster > ca.pem
openstack coe ca show secure-k8s-cluster > ca.pem
Rotate Certificate
To rotate the CA certificate for a cluster and invalidate all user
certificates, you can use the following command::
magnum ca-rotate --cluster secure-k8s-cluster
openstack coe ca rotate secure-k8s-cluster
User Examples
-------------