Marko Mudrinić

icon indicating a website link https://xmudrii.com icon indicating an email [email protected]

icon company @kubermatic icon location Belgrade, RS icon location Senior Software Engineer @kubermatic, @kubernetes Release Engineering Subproject Lead and SIG K8s Infra Tech Lead, CNCF Ambassador. Teaching Associate.

Results 897 comments of Marko Mudrinić

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

/remove-lifecycle stale

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

/remove-lifecycle stale

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

/remove-lifecycle stale

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

/remove-lifecycle stale

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

/remove-lifecycle stale

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

I didn't notice any issue with these annotations for the past couple of releases, I think we should be all good now. /close

Deprecate and turn down data studio GCP billing report

I'm +1 to turning this down ASAP, it's giving wrong results and we shouldn't use it.

Deprecate and turn down data studio GCP billing report

/remove-lifecycle stale

Deprecate and turn down data studio GCP billing report

/remove-lifecycle stale

Extend `apis.kcp.io/v1alpha2` with `APIBinding`

> While in general this looks good, the timing is questionable. Why don't we first get the API in place properly with the fields we want, and AFTER that do...