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

Define & document policy for which Kubernetes versions and features we support #596

Closed
ncdc opened this issue Jun 25, 2018 · 3 comments
Closed

Comments

@ncdc
Copy link
Contributor

ncdc commented Jun 25, 2018

Define & document a policy for which Kubernetes versions and features we support:

  1. What is our minimum required Kubernetes version
  2. Do we attempt to do graceful degradation for older Kubernetes versions?
    1. json-schema validation
    2. /status subresources for CRDs
    3. CRD field defaulting
@Bradamant3
Copy link
Contributor

Can we get started on this one for 0.10.0? Maybe say something about 0.9.1 for backward compatibility, at least? Changing milestone provisionally.

@Bradamant3 Bradamant3 modified the milestones: v0.10.0, v1.0.0 Nov 1, 2018
@Bradamant3
Copy link
Contributor

Milestone reverted; oneliner for 0.10 added (see PR #1023 )

@ncdc
Copy link
Contributor Author

ncdc commented Nov 27, 2018

xref #529

@ncdc ncdc modified the milestones: v1.0.0, v0.11.0 Nov 28, 2018
@skriss skriss modified the milestones: v0.11.0, v0.12.0 Feb 11, 2019
@skriss skriss modified the milestones: v0.12.0, v1.0.0 Apr 3, 2019
@skriss skriss modified the milestones: v1.0.0, v1.x May 20, 2019
@skriss skriss removed the Enhancement/User End-User Enhancement to Velero label Feb 19, 2020
@nrb nrb removed this from the v1.x milestone Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants