You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a) Use go run instead of scripts (downside: this does not clean up old resources)
b) Use the new k8s.io/code-generator/kube_codegen.sh
c) Wait until @cardil manages to migrate the scripts in K8s to full golang, then adapt to that solution
Todo
Agree on which way to go
Implement in pkg
Implement on all downstream repos
The text was updated successfully, but these errors were encountered:
From the discussion in kubernetes/kubernetes#122236 it is best to wait a bit until Kubernetes figures out the new way. Until then, knative/hack#357 will help to minimize the work needed for now.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
ReToCode
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Apr 15, 2024
Context
See https://cloud-native.slack.com/archives/C04LGHDR9K7/p1704710449414709 and #2904
Possible solutions
Based on #2904 (comment) and discussions.
a) Use
go run
instead of scripts (downside: this does not clean up old resources)b) Use the new
k8s.io/code-generator/kube_codegen.sh
c) Wait until @cardil manages to migrate the scripts in K8s to full golang, then adapt to that solution
Todo
pkg
The text was updated successfully, but these errors were encountered: