-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix operator panic when spec.hashiCorpVault.credential.serviceAccount is not set #5180
Fix operator panic when spec.hashiCorpVault.credential.serviceAccount is not set #5180
Conversation
Thank you for your contribution! 🙏 We will review your PR as soon as possible. While you are waiting, make sure to:
Learn more about: |
I noticed the ci failure. Will take a look at it tmr when I have time |
8d1b4d1
to
760befb
Compare
/run-e2e internal |
/run-e2e internal |
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg>
Head branch was pushed to by a user without write access
3d7fdd1
to
0159b94
Compare
@zroubalik I have just rebased the PR. When you are free, could you help to run the e2e test again ? 🙏 |
/run-e2e internal |
… is not set (kedacore#5180) Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg> Signed-off-by: Yoon Park <yoongon.park@gmail.com>
… is not set (kedacore#5180) Signed-off-by: dttung2905 <ttdao.2015@accountancy.smu.edu.sg> Signed-off-by: anton.lysina <alysina@gmail.com>
Hi team,
This PR fixes the issue where the operator panics when
spec.hashiCorpVault.credential.serviceAccount
is not setThere are two ways we can fix this:
spec.hashiCorpVault.credential.serviceAccount=/var/run/secrets/kubernetes.io/serviceaccount/token
Personally I prefer the second option. Please let me know your preference so that I can make changes to the documentation repo accordingly.
Checklist
Fixes #4964