-
Notifications
You must be signed in to change notification settings - Fork 35
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
Cover GitOps friendly Kubernetes additions #1313
Conversation
run tests |
I've seen these OC failures today already, they are not related to changes. |
More specifically, I have seen same failures in run OC JVM run number 90, so I know |
@michalvavrik I will handle these changes here: #1314. |
Ok @fedinskiy but it looks like bug in Quarkus to me. I'm just trying to create standalone reproduce. If you already know where the problem is, I will stop. |
On second thought, I'm going to sleep. |
0c4331b
to
7b4161b
Compare
run tests |
Failure related |
7b4161b
to
3c55090
Compare
This is very a weird behavior, which I can not reproduce manually on the latest 999-SNASHOT run tests |
3c55090
to
3d41334
Compare
run tests |
Hmm, still there :-/ |
Quarkus 3 allows making K8s manifests more Git-friendly [1] We cover them with these changes, with a single exception[2] [1] quarkusio/quarkus#31373 [2] quarkusio/quarkus#34673
3d41334
to
c46a790
Compare
run tests |
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
Summary
Quarkus 3 allows making K8s manifests more Git-friendly [1]
We cover them with these changes, with a single exception[2]
[1] quarkusio/quarkus#31373
[2] quarkusio/quarkus#34673
Please select the relevant options.
run tests
phrase in comment)Checklist: