--record has been deprecated, then what is the alternative

Arghya Roy

10 Jan 2024, 19:39 UTC

94.9K views1

When I am running the below command to record the change cause -

kubectl set image deployment.v1.apps/deploy1 nginx=nginx:1.16.0 --record

Then it records the change cause but shows that --record has been deprecated.

Flag --record has been deprecated, `--record` will be removed in the future
deployment.apps/deploy1 image updated

And when I run the command kubectl set image deployment.v1.apps/deploy1 nginx=nginx:1.16.0 without --record then it does not record the change cause.

So my question is if the --record has been deprecated and with be removed in the future then what is the easy alternative of that to record change? ( I mean to record the command using which I have done rollout ).

Thanks in advance.

kubectl

kubernetes

3,371 following

1 answer

Accepted answer · original discussion

Harsh Manvar

12 Jan 2024, 19:39 UTC

Permalink

Not sure if it's deprecated or will be fully.

You can use the annotate to manage the history same way.

Create the deployment

kubectl create deployment nginx --image=nginx:1.16.0 --replicas 1

check the history

kubectl rollout history deployment nginx

update the image on deployment

kubectl set image deployment nginx nginx=nginx:latest

Annotate the deployment now and create the history

kubectl annotate deployment nginx kubernetes.io/change-cause="version change to 1.16.0 to latest" --overwrite=true

Check the history

kubectl rollout history deployment nginx

1 question comment

Use comments to ask for clarification. Post a solution as an answer.

mckenzmPermalink

14 Jan 2024, 19:39 UTC

This sort of thing is why Kubernetes has a bad rap for stability. It is a cost of being bleeding edge during adoption.

Keep exploring this topic

Kubectl error: memcache.go:265] couldn’t get current server API group list: Get

Everything was running smoothly with my Kubernetes clusters until today: after performing an update on my Ubuntu system, I'm now unable to establish a connection from my working environment to the kubernetes clusters. When executing the command kubectl get pods , I'm encountering the following error message: E0805 09:59:45.750534 234576

Unable to connect to the server: getting credentials: exec: executable kubelogin not found

I created new config file for Kubernetes from Azure in Powershell by az aks get-credentials --resource-group --name . Got a message that Merged "cluster_name" as current context in C:\michu\.kube\config . I copied this file into default .kube\config location and now when I try to run any command e.g kubectl get pods

How do I install gke-gcloud-auth-plugin on a Mac M1 with zsh

I try to install gke-gcloud-auth-plugin on a Mac M1 with zsh, following the gcloud docs . The installation ran without issue and trying to re-run gcloud components install gke-gcloud-auth-plugin I get the All components are up to date. message. However, gke-gcloud-auth-plugin --version returns zsh: command not found: gke-gcloud-auth-plugi

Kubernetes: Pod IP address is out of range specified in --pod-network-cidr

After upgrading to v1.24.0 (after Dockershim removal), I had to install cri-dockerd , then I did the following: sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock --apiserver-advertise-address=192.168.0.196 I have chosen flannel as Network Plugin: kubectl apply -f https://raw.githubusercontent

--record has been deprecated, then what is the alternative

1 answer

1 question comment

Your perspective belongs here.

Good answers start here.