Skip to content
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

Auto-alias all apiVersions rather than hardcoded set #828

Closed
lblackstone opened this issue Oct 4, 2019 · 2 comments · Fixed by #991
Closed

Auto-alias all apiVersions rather than hardcoded set #828

lblackstone opened this issue Oct 4, 2019 · 2 comments · Fixed by #991
Assignees
Labels
impact/reliability Something that feels unreliable or flaky
Milestone

Comments

@lblackstone
Copy link
Member

lblackstone commented Oct 4, 2019

Followup from #798 (comment)

It should be possible to generate the list apiVersions for each resource for auto-aliasing purposes. This would be more robust against future API changes in k8s.

Update:
The upstream API reference docs are generated from the OpenAPI spec, so we should do the same. Note that we'll need to merge in older version of the spec to avoid losing deprecated + removed apiVersions.

@lblackstone lblackstone added the impact/reliability Something that feels unreliable or flaky label Oct 4, 2019
@lblackstone lblackstone self-assigned this Oct 4, 2019
@redbaron
Copy link

redbaron commented Oct 5, 2019

@hausdorff
Copy link
Contributor

It would be very nice to get CRDs in this cut, but I'm not confident we understand enough of the subtlety to do this correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/reliability Something that feels unreliable or flaky
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants