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.

Sign up for GitHub

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

Jump to bottom

Spike: Investigate valid changes to existing fields (should result in more checks to be written) #669

Closed
Tracked by #657
everettraven opened this issue Feb 27, 2024 · 1 comment
Closed
Tracked by #657

Spike: Investigate valid changes to existing fields (should result in more checks to be written) #669

everettraven opened this issue Feb 27, 2024 · 1 comment
Assignees
@rashmigottipati
Labels
epic/crd-upgrade-safety Marks an issue as part of the CRD Upgrade Safety epic

Comments

@everettraven
Copy link
Contributor

everettraven commented Feb 27, 2024 •
edited
Loading

In order to build on top of #666 we need to identify what changes to existing fields are valid changes and are suitable for static validation. The result of this spike should be a set of issues identifying which additional checks should be added on top of the implementation in #666
@everettraven everettraven mentioned this issue Feb 27, 2024
Open
26 tasks
@everettraven everettraven added the epic/crd-upgrade-safety Marks an issue as part of the CRD Upgrade Safety epic label Mar 13, 2024
@everettraven
Copy link
Contributor Author

This has been done and resulted in the creation of issues #713, #714, #715, #716

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rashmigottipati rashmigottipati

Labels
epic/crd-upgrade-safety Marks an issue as part of the CRD Upgrade Safety epic
Projects
OLM V1
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rashmigottipati @everettraven