-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Deprecate ancient errors/ package #10784
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
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
This was referenced Jun 19, 2024
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Nov 20, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 11, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 11, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 11, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 12, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 17, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 30, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
MaysaMacedo
pushed a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Dec 30, 2024
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
MaysaMacedo
pushed a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Jan 2, 2025
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
MaysaMacedo
pushed a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Jan 2, 2025
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
EmilienM
added a commit
to shiftstack/cluster-api-provider-openstack
that referenced
this issue
Jan 9, 2025
Context: kubernetes-sigs/cluster-api#10784 We'll maintain them here for the time being, until we have conditions replacing these errors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added (User Story)?
The /errors package has its origin in when capi providers were machineActuators that needed to vendor core capi to function.
There's no usage recommendations and value is questionable since we moved to CRDs and conditions for interoperability between core and providers.
I think we should deprecate it and if there's any use case relying on it we should support it via conditions
Detailed Description
The /errors package has its origin in when capi providers were machineActuators that needed to vendor core capi to function.
There's no usage recommendations and value is questionable since we moved to CRDs and conditions for interoperability between core and providers.
I think we should deprecate it and if there's any use case relying on it we should support it via conditions
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: