search

kubernetes / cloud-provider-gcp

cloud-provider-gcp contains several projects used to run Kubernetes in Google Cloud
Apache License 2.0
121 stars 209 forks source link

Add periodic job with Cilium #496

Closed aojea closed 8 months ago

aojea commented 1 year ago

GKE has different networking options, one of them is DPv2, that is Cilium with some nice sugar on top.

Since cloud-provider-gcp has multiple network controllers, it will be nice to have a periodic job to track the status of both integration. The periodic should not run very often , every 24 h I think that is reasonable.

We can not add it as a presubmit because tracking different HEAD of different projects is a source of problems

justinsb commented 1 year ago

Agree that we probably don't want a presubmit for every scenario! But re "We can not add it as a presubmit because tracking different HEAD of different projects is a source of problems", we do have a technique where we test with head of cilium with last-known-good of cloud-provider-gcp, whenever that passes we update the last-known-good of cilium. And then we test head of cloud-provider-gcp with last-known-good of cilium, and whenever that passes we update last-known-good of cloud-provider-gcp. It's used in kOps with kube and I think a few other places, we write marker files to GCS for last-known-good.

aojea commented 1 year ago

ok, I didn't know you were so ahead of my thinking 😄

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 8 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 8 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/cloud-provider-gcp/issues/496#issuecomment-1901032850): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.