-
Notifications
You must be signed in to change notification settings - Fork 68
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
GoogleKms encryption fails on 0.6.2.0 (0.6.1.0 works) #455
Comments
Thanks for filing the issue! Can you please share encryptor logs? Looking on the changelog, there is nothing significantly changed between 6.1.0 to 6.2.0, so I'll be curious to see why it crash :) Also, if you could file an issue on the chart repo I'll be happy to look into that! |
I can provide some logs, since I am running into the same issue. I am experimenting with kamus for our clusters on GKE, and when I use the 0.6.1.0 tagged docker images, it works, but if I switch to 0.6.2.0 or 0.6.3.0 it will give the Here are the logs from the encryptor container (v0.6.2.0):
|
That's interesting, look like a timeout - but no errors on the controller. Are you using ingress to access the encryptor? Can you try using port forward? |
I am using port-forward. Don't have airbag deployed, and obviously don't want to expose the encryptor without auth ;) |
Can you try reaching the liveness endpoint? Also, can you please try with default (AES) KMS? |
Liveness endpoint works:
I will try with AES and get back to you with the results. |
Hey @omerlh. Sorry for the late reply. AES works, I've tried it when I was looking for a working alternative to GKE KMS. I am trying to bump the version back to 0.6.2.0 in order to reproduce the problem and provide more information but the controller won't start. I think the problem is that I already have two KamusSecrets created with 0.6.1.0:
I had to delete the secrets to test (fyi, I removed the healthcheck, they were creating too much noise in logs):
Nothing interesting in controller:
|
Wait, I'm not sure we're talking about the same issue here - does the issue with the controller or the encryptor? I just tested the latest encryptor version locally on my mac and it's working, so it's either docker-related issue (which will not surprise me) or something else. |
I have the same issue on 6.2.0 with Google Cloud KMS. Going back to 6.1.0 is working for me as well. |
Sorry for the confusion. Is the same issue as I described in the beginning. Controller might fail because of the encryptor. I will test encryptor with latest version to check that as well. |
I was able to reproduce the issue and fix it, there is something bad happening with alpine - switch to buster seems to fix it. We'll release the new version tomorrow, stay tuned! |
Thanks for solving this @omerlh . Really interesting issue. |
You welcome! Can you please confirm the issue is resolved?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: lebenitza <notifications@github.com>
Sent: Sunday, March 8, 2020 12:39:15 PM
To: Soluto/kamus <kamus@noreply.github.com>
Cc: Omer Levi Hevroni <omerl@soluto.com>; Mention <mention@noreply.github.com>
Subject: Re: [Soluto/kamus] GoogleKms encryption fails on 0.6.2.0 (0.6.1.0 works) (#455)
Thanks for solving this @omerlh<https://github.com/omerlh> . Really interesting issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#455?email_source=notifications&email_token=ABTLGWFX5MDZFZ25O6GHC63RGNYVHA5CNFSM4K4MHLKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOESL4A#issuecomment-596190704>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABTLGWBYVTMS5OSQHG27O73RGNYVHANCNFSM4K4MHLKA>.
|
Is indeed fixed, I upgraded last night to 0.6.4.0. |
Happy to hear so! |
Describe the bug
Using version 0.6.2.0 with GoogleKms causes the encryptor to fail without an apparent reason when trying to encrypt values with kamus-cli. Same settings work with 0.6.1.0. Tested with 0.6.3.0 as well, same behavior. Feels like it's because of some changes between 0.6.1.0 and 0.6.2.0.
Note: 0.6.3.0 controller fails to start with the current version of the chart but that might be something for another issue :) I'll look more into it when I'll have time
Versions used
Kamus (API images): 0.6.2.0
Kamus CLI: 0.3.0
Chart version: 0.4.6
KMS provider: GoogleKms
Kubernetes flavour and version: v1.15.7-gke.23
To Reproduce
Steps to reproduce the behavior:
Expected behavior
kamus-cli calls returns the encrypted value after creating the required key in the keyring (as it is working on 0.6.1.0)
If you need any help let me know, curious how C# is lately :)
The text was updated successfully, but these errors were encountered: