kubernetes/kubernetes

last applied annotations are not getting updated

jainpratik163 opened this issue · 5 comments

jainpratik163 commented

What happened?

i was trying to update configmap and after editing successfully configmap annotation didn't update with the last values. still, it holds 1st-time data only.
basically, I am trying to write one code to capture if someone changes anything in CM and we can identify it.

and also in some configmap I am not able to find last-applied annotation.

What did you expect to happen?

annotation should update

How can we reproduce it (as minimally and precisely as possible)?

create cm with below
apiVersion: v1 kind: ConfigMap metadata: name: game-config-env-file data: allowed: '"true"' enemies: aliens lives: "31"

and now edit this cm game-config-env-file and let say change any values last-applied annotation is not getting chnaged

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# Client Version: v1.28.8-eks-ae9a62a
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.8-eks-adc7111

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

k8s-ci-robot commented

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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.

k8s-ci-robot commented

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

neolit123 commented

try opening a thread at the support channels like discuss.k8s.io first.
https://git.k8s.io/kubernetes/SUPPORT.md

/kind support
/close

k8s-ci-robot commented

@neolit123: Closing this issue.

In response to this:

try opening a thread at the support channels like discuss.k8s.io first.
https://git.k8s.io/kubernetes/SUPPORT.md

/kind support
/close

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.