-
Notifications
You must be signed in to change notification settings - Fork 296
Conversation
Signed-off-by: Artyom Bakhtin <[email protected]>
Signed-off-by: Artyom Bakhtin <[email protected]>
Signed-off-by: Artyom Bakhtin <[email protected]>
Signed-off-by: Artyom Bakhtin <[email protected]>
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.
Cool! Not tested. I would be glad to see a presentation of the feature via zoom or using any other convenient way.
Docs demo can be seen here https://html-vzfklvxpvt.now.sh/guides/k8s-deployment
@@ -0,0 +1 @@ | |||
aff50dae4ce7e0474c9f9fdf943744bebd4a1c66bb3bb76a8cc9218b431668e9 |
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.
Probably I miss something, but why not generate such keys on the go?
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.
That is to provide a set of pregenerated keys ready to be deployed on a cluster. Similar to ones we have in example
directory
|
||
Preparation | ||
^^^^^^^^^^^ | ||
You need to obtain AWS key for managing resources. We recommend to create a separate IAM user for that. Go to your AWS console, head to "My Security Credentials" menu and create a user in "Users" section. Assign "AmazonEC2FullAccess" and "AmazonVPCFullAccess" policies to that user. Click "Create access key" on Security credentials tab. Take a note for values of Access key ID and Secret key. Set these values as environment variables in your console: |
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.
Please put each sentence on its own line. That will make reviewing and commenting easier.
Currently, this comment relates to the whole paragraph.
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.
Everything is ok. Great work!
Signed-off-by: Artyom Bakhtin <[email protected]>
* submodule Signed-off-by: Artyom Bakhtin <[email protected]> * add docs Signed-off-by: Artyom Bakhtin <[email protected]> * add to index Signed-off-by: Artyom Bakhtin <[email protected]> * fix grammar Signed-off-by: Artyom Bakhtin <[email protected]> * fix comments Signed-off-by: Artyom Bakhtin <[email protected]>
Description of the Change
This PR introduces support for deploying Iroha on Kubernetes cluster. PR consists of two major components that configure instances and run Iroha service:
Pod specification file can also be used for manual deployment. Terraform modules are ready for manual deployment as well if one needs it.
For more info regarding the structure and internals see README file in iroha-k8s Ansible role
There is also Deployment manual that describes the steps required for deploying k8s cluster from scratch and running Iroha service on it.
Benefits
Iroha can be deployed on Kubernetes cluster
Possible Drawbacks
None