-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
When using Secrets, config functionality should be auto enabled #11748
Conversation
ketoketo
commented
Aug 31, 2020
- is related to When using Secrets, config functionality should be auto enabled #11258
Thanks for this! Can you please check the output of CI? Something is failing |
The relevant CI failure is:
|
Thanks for the review. I'll try to fix it. |
Can you please squash the commits? |
5c46c06
to
9bad2c9
Compare
There is one thing I don't like: With the current approach, having |
I thought that being able to read configMap when |
Sorry, I meant that when enabling secrets, then config maps are enabled - that is what I am saying is a little weird |
...ntime/src/main/java/io/quarkus/kubernetes/client/runtime/KubernetesConfigSourceProvider.java
Show resolved
Hide resolved
import io.fabric8.kubernetes.api.model.ConfigMapBuilder; | ||
import io.fabric8.kubernetes.api.model.ConfigMapList; | ||
import io.fabric8.kubernetes.api.model.DoneableConfigMap; | ||
import io.fabric8.kubernetes.api.model.*; |
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.
Minor nitpick: Please avoid using start imports
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.
Fixed it
fix integration test fix log fix import
ad4a2c0
to
f350ec7
Compare
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.
LGTM, thanks a lot!