Open aojea opened 3 months ago
This issue is currently awaiting triage.
If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/assign @justinsb
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
This is referenced in the following manifest
https://github.com/kubernetes/cloud-provider-gcp/blob/1de847756d12ddb6fbc920277f3e836fd5617443/deploy/packages/default/manifest.yaml#L46
used by the jobs
https://github.com/kubernetes/cloud-provider-gcp/blob/1de847756d12ddb6fbc920277f3e836fd5617443/e2e/scenarios/kops-simple#L184
some users take those images for testing , but they should be using the staging images https://github.com/kubernetes/cloud-provider-gcp/issues/289#issuecomment-1537442581 or the released ones https://github.com/kubernetes/cloud-provider-gcp/issues/289#issuecomment-1889176432