mdlint image is hosted in a VMware-owned registry

[sbueringer]

Hey folks,

just wanted to let you know that the mdlint image used (gcr.io/cluster-api-provider-vsphere/extra/mdlint:0.17.0) is hosted in a VMware-owned registry (/ GCP project). In CAPV we stopped using this image, so we won't maintain it anymore going forward.

We won't delete the image from the current registry, but we also cannot guarantee that it will exist forever there.

[k8s-triage-robot]

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

This bot triages un-triaged 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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:

• 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:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

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

/close not-planned

[k8s-ci-robot]

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

In response to this:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sbueringer]

Just fyi, we'll keep the image around best effort. But I assume after the migration to the community-owned registry we will eventually cleanup/delete the gcp project that contains this image

[sbueringer]

cc @lubronzhan @XudongLiuHarold

[XudongLiuHarold]

Hi @sbueringer , we plan to migrate to the community-owned registry soon 😄, but need to work on cherrying pick recent changes to each release branches first

[sbueringer]

I think this is a different topic. It's just about usage of the mdlint image. Except if you meant moving over the mdlint image 😃

[XudongLiuHarold]

I think this is a different topic. It's just about usage of the mdlint image. Except if you meant moving over the mdlint image 😃

Yeah, I mean we will migrate mdlint image to community-owned registry soon

[sbueringer]

Got it, sounds good!

[sbueringer]

Btw. If you need the corresponding Dockerfile. Looks like we deleted it after CAPV v1.4. Here seems to be the latest version: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/tree/release-1.4/hack/tools/mdlint

(this was way before the time I started contributing to CAPV)