英文:
volumesnapshotcontent created with old timestamp
问题
我有一个情景，其中volumesnapshotcontent的时间戳显示异常。
snapcontent-f5dae7f1-5fcc-4b10-a856-27462e8f248a false 1073741824 Retain vpc.block.csi.ibm.io stork-csi-snapshot-class-vpc.block.csi.ibm.io px-do-not-delete-cf058705-d4ea-4da8-b8e4-d8602a160acc-0e1b8534 kube-system 36d
这里的"Age"是36天。这是否有原因？
英文:
I have a scenario where volumesnapshotcontent is getting created with weird timestamp.
snapcontent-f5dae7f1-5fcc-4b10-a856-27462e8f248a false 1073741824 Retain vpc.block.csi.ibm.io stork-csi-snapshot-class-vpc.block.csi.ibm.io px-do-not-delete-cf058705-d4ea-4da8-b8e4-d8602a160acc-0e1b8534 kube-system 36d
Here Age is 36d. Is there a reason for this
答案1
得分: 0
一个VolumeSnapshotContent是从集群中由管理员提供的卷中创建的快照。它在集群中就像PersistentVolume一样是一个资源。与“VolumeSnapshotContent”资源关联的时间戳可能不总是反映系统准确创建的时间。当对象被修改或创建时，它不会自动更新。
当创建一个VolumeSnapshotContent时，GCP会根据快照内容生成的时间为资源分配一个时间戳。快照内容在将VolumeSnapshotContent注册到Kubernetes之前被提供。**因此，VSC可能会采用快照内容创建的时间戳。**随后，在“绑定”部分，最终用户创建他们的VolumeSnapshot。然后，管理员会继续进行数据快照，并最终注册一个VSC并将其绑定到最终用户的VolumeSnapshot。
确保您提供给Kubernetes集群或存储系统的配置是否正确。这可能会导致创建时间不正确。
要进一步进行故障排除，请提供更具体的详细信息，如Kubernetes版本、存储系统。
英文:
A VolumeSnapshotContent is a snapshot taken from a volume in the cluster that has been provisioned by an administrator. It is a resource in the cluster just like a PersistentVolume is a cluster resource. The timestamp associated with a ‘VolumeSnapshotContent’ resource might not always reflect the exact creation time by system. It does not update automatically when the object is modified or created.
When a VolumeSnapshotContent is created, GCP assigns a timestamp to the resource based on when snapshot content was generated. Snapshot content was provisioned before registering the VolumeSnapshotContent into kubernetes. So, VSC might take the timestamp of snapshot content creation. Later on, in the "binding" section, End-users creates their VolumeSnapshot. Then admin proceeds with snapshotting data, and eventually registers a VSC and binds it to the end-user's VolumeSnapshot.
Ensure the configuration within your kubernetes cluster or storage system you are providing is correct or not This might cause the incorrect timestamp in creation.
To troubleshoot further, please provide more specific details like the kubernetes version, storage system.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论