-
Notifications
You must be signed in to change notification settings - Fork 344
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
Builder annotation support #5104
Conversation
I am struggling to find any place to insert test for this enhancement. Could anyone chime in? |
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.
Please, open separate PRs in order to discuss each different topic separately. Regarding this specific feature, LGTM. For testing, please, have a look at this example:
camel-k/pkg/trait/builder_test.go
Line 466 in 1db0f57
func TestBuilderWithNodeSelector(t *testing.T) { |
✔️ Unit test coverage report - coverage increased from 34.8% to 35.3% (+0.5%) |
f194d9a
to
477d438
Compare
✔️ Unit test coverage report - coverage increased from 34.8% to 35.3% (+0.5%) |
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.
+1 for the controller test. That's the way to improve quality! Thanks!
✔️ Unit test coverage report - coverage increased from 34.8% to 35.6% (+0.8%) |
This PR proposes to add the possibility to configure annotation on the build pod.
This was required to allow build pods to properly execute in the context of using Buildah in an AppArmor enabled Kubernetes cluster.
Also included are a few tweak encountered while running the operator out of cluster.
Release Note
Fixes #5106