Add note that "default" namespace deployments are not supported #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: thepetk <thepetk@gmail.com>
thepetk
force-pushed
the
feat/add-default-namespace-note
branch
from
d88d1d9 to
65baabb
Compare
johnmcollier
approved these changes
Nov 6, 2024
thepetk
added a commit
to thepetk/ai-lab-template
that referenced
this pull request
Nov 6, 2024
Signed-off-by: thepetk <thepetk@gmail.com>
2 tasks
thepetk
added a commit
that referenced
this pull request
Nov 7, 2024
[release-v0.9.x] Add note for default namespace (#56)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?:
Simply adds a note in troubleshooting for the usage of "Default" namespace for AI Software template apps deployment.
Which issue(s) this PR fixes:
https://issues.redhat.com/browse/DEVAI-234
PR acceptance criteria:
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened and linked to this PR, if they are not in the PR scope due to various constraints.
Tested and Verified
Documentation (READMEs, Product Docs, Blogs, Education Modules, etc.)
How to test changes / Special notes to the reviewer: