This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
Iroha Kubernetes #1697
Merged
Iroha Kubernetes #1697
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Artyom Bakhtin <a@bakhtin.net>
Signed-off-by: Artyom Bakhtin <a@bakhtin.net>
bakhtin
added
needs-review
igor-egorov
approved these changes
Aug 31, 2018
There was a problem hiding this comment.
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.
Probably I miss something, but why not generate such keys on the go?
There was a problem hiding this comment.
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.
Please put each sentence on its own line. That will make reviewing and commenting easier.
Currently, this comment relates to the whole paragraph.
tyvision
approved these changes
Sep 18, 2018
Signed-off-by: Artyom Bakhtin <a@bakhtin.net>
bakhtin
added a commit
that referenced
this pull request
Nov 2, 2018
* submodule Signed-off-by: Artyom Bakhtin <a@bakhtin.net> * add docs Signed-off-by: Artyom Bakhtin <a@bakhtin.net> * add to index Signed-off-by: Artyom Bakhtin <a@bakhtin.net> * fix grammar Signed-off-by: Artyom Bakhtin <a@bakhtin.net> * fix comments Signed-off-by: Artyom Bakhtin <a@bakhtin.net>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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