Closed Nayana-ibm closed 5 years ago
Could you please let us know on this
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
@fejta-bot Can someone confirm on the tag 1.2 for exechealthz? ( more details in description )
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/close
I could see the exechealthz image uploaded here and its for tag 1.2
I tried to build image from source as mentioned in Readme Using branch: cluster-autoscaler-0.5.1 make TAG=1.2 ARCH=s390x
However, the image created shows the tag as 3b70a71b-dirty and not as 1.2
gcr.io/google_containers/exechealthz-s390x 3b70a71b-dirty
Changes needed in makefile or any other build file?