1

I am trying to update a custom resource:

kubectl edit ticketservice r134-4979a2f6-f46d-405d-97bc-ab1ba -n 2b9aea53dbfc47a

apiVersion: ticketservice.ias.alpha.com/v1alpha1
kind: TicketService
metadata:
  annotations:
    foo: bar
    baz: bux
    .. etc ..
  creationTimestamp: "2022-05-04T20:08:06Z" <--- here
  finalizers:
  - ticket-generator/simulator-finalizer
  generation: 3
  labels:
    label1: value1
    .. etc ..
  name: r134-4979a2f6-f46d-405d-97bc-ab1baf97543d

No matter what I do on the edit, the creationTimestamp just comes back at the same time. I can't edit it, can't remove the line either - it just comes back.

I thought maybe the finalizer line was involved, but I was able to delete it, but still no dice editing the creationTimestamp

I think there must be another resource that locks this value; any idea what the reason is, and if there's another check going on on submission, then how would I trace that?

Oliver Williams
  • 5,966
  • 7
  • 36
  • 78

1 Answers1

2

creationtimestamp can only be set by Kubernetes as it turns out. From a trusted source but sadly don't have the specific k8s docs ref.

Oliver Williams
  • 5,966
  • 7
  • 36
  • 78