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
Support for kube collections #19052
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
kube
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
StanEgo
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jun 29, 2023
@umohnani8 WDYT? |
A friendly reminder that this issue had no activity for 30 days. |
@ygalblum WDYT? |
I don't see a reason why not to support this. Especially since the code already handles a list of documents. It will just need to be adjusted to a document that is a list. |
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Nov 27, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
kube
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Feature request description
It would be nice to have a support for https://kubernetes.io/docs/reference/using-api/api-concepts/#collections. Nothing sophisticated, just looks like a resource with "kind: List", but this greatly simplifies to play kube manifest in JSON with multiple resources. Right now code below results in "Error: playing YAML file: YAML document does not contain any supported kube kind" message:
Suggest potential solution
A clear and concise description of what you want to happen.
Have you considered any alternatives?
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: