You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the old version and USE_CLAIM_NAME=true, my Snapshot names looked as expected. With the new version, Snapshot names are empty. I believe the k8s-snapshots version change is the only thing that changed in my cluster between the desired behavior and the buggy behavior.
If I have it right, the two changes merged between the old version and the new version are #51 --
which looks to be Google Cloud-only -- and #50. @wadahiro do you think this could be related to your boto3 changes?
The text was updated successfully, but these errors were encountered:
I've been running k8s-snapshots for a few months in a kops-managed Kubernetes cluster on AWS.
I pulled the latest k8s-snapshots Docker image. I believe I went from the 2018-02-09 image c5da4196dfa7 to the 2018-02-18 image d4c54dea2402 (current latest build).
With the old version and
USE_CLAIM_NAME=true
, my Snapshot names looked as expected. With the new version, Snapshot names are empty. I believe the k8s-snapshots version change is the only thing that changed in my cluster between the desired behavior and the buggy behavior.If I have it right, the two changes merged between the old version and the new version are #51 --
which looks to be Google Cloud-only -- and #50. @wadahiro do you think this could be related to your boto3 changes?
The text was updated successfully, but these errors were encountered: