Skip to content
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

Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Add ability to auto-unseal using AWS KMS key. Add Ability to Use Pre-Created Self-Signed Certs. Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Fix Ingress over TLS. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. #49

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

Xtigyro
Copy link
Contributor

@Xtigyro Xtigyro commented Jun 7, 2019

  • Add ability to use AWS S3 as Vault's Data Storage ("storage") and Consul only as Vault's High Availability Storage ("ha_storage").
  • Add ability to auto-unseal using AWS KMS key
  • Add ability to use manually pre-created self-signed certs.
  • Address Helm v2.14 New Validation Rules - fix(helm): Fix manifest validation helm/helm#5576.
  • Use "Soft" AntiAffinities to allow deployment to single node services such as microK8s or Minikube.
  • Fix Consul's backup procedure - Backing up Consul - Broken #50.
  • Fix Ingress over TLS.
  • Bumped Vault to v1.2.2 and Consul to v1.6.0.
  • Fix GitHub's Chart URL in README.md.

v0.2.1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
* Address Helm v2.14 New Validation Rules (helm/helm#5576)
* Use "Soft" AntiAffinities to allow deployment to single node services such as microK8s or Minikube
* Bumped Vault to 1.1.1 and Consul to 1.5.1
@Xtigyro

This comment has been minimized.

@Xtigyro Xtigyro changed the title v0.2.1 v0.2.5 Jun 12, 2019
@Xtigyro Xtigyro changed the title v0.2.5 Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Jun 12, 2019
@Xtigyro Xtigyro changed the title Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Fix Consul Backup. Jun 15, 2019
@Xtigyro
Copy link
Contributor Author

Xtigyro commented Jun 21, 2019

@bartlettc22
Hi Chris - I think I'm done with this PR.
If any changes are desired - please let me know.

@Xtigyro Xtigyro changed the title Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Fix Consul Backup. Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Jul 3, 2019
@Xtigyro
Copy link
Contributor Author

Xtigyro commented Jul 3, 2019

I noticed that the URL of the chart in GitHub was still pointing to ReadyTalk instead of PremiereGlobal - fixed.

Verified

This commit was signed with the committer’s verified signature.
b1ek blek!
Bump Vault to v1.1.3

Bump Vault to v1.1.3

Revert Vault to v1.1.2

Revert Vault to v1.1.2

Add AWS S3 Only as "storage" Option
@Xtigyro
Copy link
Contributor Author

Xtigyro commented Jul 6, 2019

Did a rebase - so the commits are less in number and clearer.

@Xtigyro
Copy link
Contributor Author

Xtigyro commented Aug 27, 2019

@bartlettc22 Added ability to auto-unseal using AWS KMS key as well, in the meantime.

@Xtigyro Xtigyro changed the title Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Add ability to auto-unseal using AWS KMS key. Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Aug 27, 2019
@Xtigyro Xtigyro changed the title Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Add ability to auto-unseal using AWS KMS key. Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Add ability to auto-unseal using AWS KMS key. Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Fix Ingress over TLS. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Sep 7, 2019
@Xtigyro
Copy link
Contributor Author

Xtigyro commented Sep 7, 2019

@bartlettc22
Fixed the Vault's Ingress over TLS.
Added ability to use manually pre-created self-signed certs.

@Xtigyro Xtigyro changed the title Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Add ability to auto-unseal using AWS KMS key. Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Fix Ingress over TLS. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Ability to Use AWS S3 as "storage" and Consul only as "ha_storage". Add ability to auto-unseal using AWS KMS key. Add Ability to Use Pre-Created Self-Signed Certs. Address Helm v2.14 New Validation Rules. Use "soft" AntiAffinities. Fix Ingress over TLS. Bump Vault and Consul Versions. Fix Consul Backup. Fix GitHub's Chart URL in README. Sep 7, 2019
@Xtigyro
Copy link
Contributor Author

Xtigyro commented Feb 9, 2020

@bartlettc22
Hey Chris - what are the plans? Are we going to merge this PR? It's been quite a while.

@Xtigyro Xtigyro requested a review from bartlettc22 February 9, 2020 10:31
@Xtigyro
Copy link
Contributor Author

Xtigyro commented May 24, 2020

@bartlettc22 Hey Chris - can we merge this please?

@Xtigyro
Copy link
Contributor Author

Xtigyro commented Sep 10, 2020

@bartlettc22 @hyperbolist @AprilElizabeth @gyoza @benoram

Hey guys - can we merge this please? If not - I'm gonna delete my fork because it has been waiting for too long. Let me know please, I'll wait a few more days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant