nfs-subdir-external-provisioner icon indicating copy to clipboard operation
nfs-subdir-external-provisioner copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

question about tag of image k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner

Open hillbun opened this issue 3 years ago • 13 comments

I can just pull k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2

How to pull other version 4.0.17, 4.0.16, 4.0.15...?

hillbun avatar Aug 19 '22 05:08 hillbun

any advice?

hillbun avatar Aug 25 '22 09:08 hillbun

4.0.17 Releases

image:
  repository: k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner
  tag: v4.0.2
  pullPolicy: IfNotPresent
imagePullSecrets: []

tag version is v4.0.2

yokaimeow avatar Aug 26 '22 08:08 yokaimeow

tag version is always v4.0.2?

hillbun avatar Aug 27 '22 12:08 hillbun

Can anyone give advice about image tag rule?

hillbun avatar Aug 31 '22 02:08 hillbun

Versions 4.0.17, 4.0.16, 4.0.15.. are versions of the helm chart, appVersion is still 4.0.2. See https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/blob/master/charts/nfs-subdir-external-provisioner/Chart.yaml.

rmoreas avatar Aug 31 '22 08:08 rmoreas

do you mean this image of k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner version do not upgrade when new release https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/releases here?

hillbun avatar Aug 31 '22 09:08 hillbun

Yes,image version is still 4.0.2

yokaimeow avatar Sep 02 '22 16:09 yokaimeow

how to get new version then? if new feather released or bug fixed

hillbun avatar Sep 05 '22 03:09 hillbun

When there is a new version, the appVersion and image tag will be updated in the helm chart and the helm chart itself also get a version bump.

rmoreas avatar Sep 05 '22 07:09 rmoreas

this repo release version is nfs-subdir-external-provisioner-4.0.17, but image tag is still 4.0.2.

How to update image tag version.

hillbun avatar Sep 05 '22 08:09 hillbun

@hillbun : see comments https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/231#issuecomment-1232630549, https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/231#issuecomment-1235679775

rmoreas avatar Sep 05 '22 10:09 rmoreas

@rmoreas But I still do not understand how to upgrade image version to latest but not 4.0.2

please advice.

hillbun avatar Sep 07 '22 01:09 hillbun

@hillbun v4.0.2 is the latest version.

guilhermemalfatti avatar Sep 21 '22 13:09 guilhermemalfatti

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Dec 20 '22 14:12 k8s-triage-robot

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Jan 19 '23 15:01 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-triage-robot avatar Feb 18 '23 15:02 k8s-triage-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/test-infra repository.

k8s-ci-robot avatar Feb 18 '23 15:02 k8s-ci-robot