ramsey,
@ramsey@phpc.social avatar

Why isn’t --record=true the default behavior when applying changes to a deployment?

alessandrolai,
@alessandrolai@phpc.social avatar

@ramsey what command are talking about? I do not use kubectl so much since Helm took over in my projects, but I don't remember that option though

ramsey,
@ramsey@phpc.social avatar

@alessandrolai Like when creating a deployment. It tells it to record the command used to create the deployment. If you don’t use it, then it doesn’t record the command, so if you update your deployment and don’t tell it to record, then when you look at your history, you see each revision, but not the command that made the revision.

alessandrolai,
@alessandrolai@phpc.social avatar

@ramsey I always only did kubectl apply for changes, never delved deeper so I didn't know this option! I switched to Helm that handles revisions automatically for rollbacks too...

I was searching around to understand it and I stumbled on this, it seems they're deprecating it: https://stackoverflow.com/questions/73814500/record-has-been-deprecated-then-what-is-the-alternative

  • All
  • Subscribed
  • Moderated
  • Favorites
  • Kubernetes
  • DreamBathrooms
  • InstantRegret
  • ethstaker
  • magazineikmin
  • GTA5RPClips
  • rosin
  • modclub
  • Youngstown
  • ngwrru68w68
  • slotface
  • osvaldo12
  • kavyap
  • mdbf
  • thenastyranch
  • JUstTest
  • everett
  • cubers
  • cisconetworking
  • normalnudes
  • Durango
  • anitta
  • khanakhh
  • tacticalgear
  • tester
  • provamag3
  • megavids
  • Leos
  • lostlight
  • All magazines