-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: add ai-navigator-app #1514
Conversation
This repo has @d2iq-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@d2iq-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.For help using mergebot, please refer to the README file here: https://github.com/mesosphere/mergebot/blob/main/README.md |
Pull Request Test Coverage Report for Build 6023072203
💛 - Coveralls |
4168b79
to
ab1b448
Compare
1bd1688
to
e9e2f41
Compare
420cec0
to
63bbca5
Compare
e50743a
to
730ae56
Compare
56b08bf
to
f581ab6
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.
looks good! it would be nice to have tickets for the follow up work just so we don't forget about them. (we should at least set the limits/requests prior to releasing)
I've created them yesterday 😇 |
@mstruebing can we backport this to 2.6 as-is? |
@cbuto yes we can! :) |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
@mstruebing looks like we'll have to manually create the backport by cherry-picking the commit(s) 😞 |
* feat: add ai-navigator-app * Closes D2IQ-98636 * chore: use `${releaseNamespace}` instead of hardcoded namespace * chore: allow to read licenses and secrets * chore: allow to read licenses and secrets * chore: add liveness and readiness probes * chore: update description * feat: specifiy security context * chore: use correct logo * chore: indent securityContext * chore: add period * chore: use correct version
* feat: Introduce empty kustomization of ai-navigation-app (#1547) * feat: Introduce empty kustomization of ai-navigation-app Signed-off-by: Mikołaj Baranowski <[email protected]> * build: Updated .github/service-labeler.yaml --------- Signed-off-by: Mikołaj Baranowski <[email protected]> Co-authored-by: d2iq-mergebot <[email protected]> * feat: add ai-navigator-app (#1514) * feat: add ai-navigator-app * Closes D2IQ-98636 * chore: use `${releaseNamespace}` instead of hardcoded namespace * chore: allow to read licenses and secrets * chore: allow to read licenses and secrets * chore: add liveness and readiness probes * chore: update description * feat: specifiy security context * chore: use correct logo * chore: indent securityContext * chore: add period * chore: use correct version --------- Signed-off-by: Mikołaj Baranowski <[email protected]> Co-authored-by: Mikołaj Baranowski <[email protected]> Co-authored-by: d2iq-mergebot <[email protected]>
What problem does this PR solve?:
This PR adds the ai-navitgator-app to our
kommander-applications
catalog.Which issue(s) does this PR fix?:
https://d2iq.atlassian.net/browse/D2IQ-98636
Special notes for your reviewer:
This PR is a WIP.We need to change the description and the icon.I've applied these resources to the daily and get:What do I need to do so that the service would be able to read licenses and the corresponding secret?Also, is it okay to hardcode the namespace tokommander
? (this application should always be deployed in this namespace)Should I split these resources into multiple files or is it okay to have them in one?I think this needs to be merged into the 2.6 branch to be available in 2.6.1.
I'm not sure how commit messages come into play here, but should I change it to
fix
?Is there a way to apply the catalog from this branch on a cluster? Right now I simply applied theDeployment
andService
definition, but for a real test I would like to use it like it would be used in reality.Does this PR introduce a user-facing change?:
Checklist