-
Notifications
You must be signed in to change notification settings - Fork 19
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
OpenEBS investigation #300
Conversation
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.
Just minor comments.
IMO We can later add one more paragraph at the end of this document to summarize the direction we went in (after tomorrow's discussion).
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 read this document on Friday and I forgot to give ✅ . Here it is 👍
Co-authored-by: Mateusz Szostok <mateusz@structsure.co>
Co-authored-by: Mateusz Szostok <mateusz@structsure.co>
Co-authored-by: Mateusz Szostok <mateusz@structsure.co>
Description
Changes proposed in this pull request:
I don't think there is a point to deploy the env again from the scratch. It requires
It easily can take a day
I have a running cluster if someone want to take a look:
Bastion IP, private key and kubeconfig can be found here:
https://eu-west-1.console.aws.amazon.com/systems-manager/parameters/?region=eu-west-1&tab=Table
There is installed Jira at https://jira.lukasz.cluster.projectvoltron.dev admin/admin