Before kubernetes 1.15 the answer is no. But there is a workaround of patching deployment spec with a dummy annotation:

    kubectl patch deployment web -p \
      &quot;{\&quot;spec\&quot;:{\&quot;template\&quot;:{\&quot;metadata\&quot;:{\&quot;annotations\&quot;:{\&quot;date\&quot;:\&quot;`date +&#39;%s&#39;`\&quot;}}}}}&quot;

As of kubernetes 1.15 you can use:

    kubectl rollout restart deployment your_deployment_name

&gt; [CLI Improvements][1]
&gt; 
&gt;  - Created a new `kubectl rollout restart` command that does a rolling restart of a deployment.
&gt;  - `kubectl rollout restart` now works for DaemonSets and StatefulSets


  [1]: https://kubernetes.io/docs/setup/release/#cli-improvements

If you use k9s, the restart command can be found if you select deployments, statefulsets or daemonsets:

[![screenshot of k9s][1]][1]


  [1]: https://i.stack.imgur.com/LSG1N.png

Let&#39;s say I go to compile some poorly-written C++ source code that invokes undefined behavior, and therefore (as they say) &quot;anything can happen&quot;.

From the perspective of what the C++ language specification deems acceptable in a &quot;conformant&quot; compiler, does &quot;anything&quot; in this scenario include the compiler crashing (or stealing my passwords, or otherwise misbehaving or erroring-out at compile-time), or is scope of the undefined-behavior limited specifically to what can happen when the resulting executable runs?

Is it legal for source code containing undefined behavior to crash the compiler?

I&#39;m playing with SwiftUI, trying to understand how `ObservableObject` works. I have an array of `Person` objects. When I add a new `Person` into the array, it is reloaded in my View, however if I change the value of an existing `Person`, it is not reloaded in the View. 

```SwiftUI
//  NamesClass.swift
import Foundation
import SwiftUI
import Combine

class Person: ObservableObject,Identifiable{
    var id: Int
    @Published var name: String
    
    init(id: Int, name: String){
        self.id = id
        self.name = name
    }
}

class People: ObservableObject{
    @Published var people: [Person]
    
    init(){
        self.people = [
            Person(id: 1, name:&quot;Javier&quot;),
            Person(id: 2, name:&quot;Juan&quot;),
            Person(id: 3, name:&quot;Pedro&quot;),
            Person(id: 4, name:&quot;Luis&quot;)]
    }
}
```

```SwiftUI
struct ContentView: View {
    @ObservedObject var mypeople: People
    
    var body: some View {
        VStack{
            ForEach(mypeople.people){ person in
                Text(&quot;\(person.name)&quot;)
            }
            Button(action: {
                self.mypeople.people[0].name=&quot;Jaime&quot;
                //self.mypeople.people.append(Person(id: 5, name: &quot;John&quot;))
            }) {
                Text(&quot;Add/Change name&quot;)
            }
        }
    }
}
```

If I uncomment the line to add a new `Person` (John), the name of Jaime is shown properly, however if I just change the name this is not shown in the View.

I&#39;m afraid I&#39;m doing something wrong or maybe I don&#39;t get how the `ObservedObjects` work with arrays.

Why is an ObservedObject array not updated in my SwiftUI application?

In kubernetes there is a rolling update (automatically without downtime) but there is not a rolling restart, at least i could not find. We have to change deployment yaml. Is there a way to make rolling &quot;restart&quot;, preferably without changing deployment yaml?

How to rolling restart pods without changing deployment yaml in kubernetes?

<p>In kubernetes there is a rolling update (automatically without downtime) but there is not a rolling restart, at least i could not find. We have to change deployment yaml. Is there a way to make rolling "restart", preferably without changing deployment yaml?</p>


I was playing around in minikube and installed the wrong version of istio.  I ran:

    kubectl apply -f install/kubernetes/istio-demo-auth.yaml

instead of:

    kubectl apply -f install/kubernetes/istio-demo.yaml

I figured I would just undo it and install the right one.

But I cannot seem to find an `unapply` command.

**How do I *undo* a &quot;kubectl apply&quot; command?**

What is the reverse of &quot;kubectl apply&quot;?

When I try to install a chart with helm:

    helm install stable/nginx-ingress --name my-nginx

I get the error: 

&gt; Error: unknown flag: --name

But I see the above command format in many documentations. 

Version: 

&gt; version.BuildInfo{Version:&quot;v3.0.0-beta.3&quot;,
&gt; GitCommit:&quot;5cb923eecbe80d1ad76399aee234717c11931d9a&quot;,
&gt; GitTreeState:&quot;clean&quot;, GoVersion:&quot;go1.12.9&quot;}

Platform: Windows 10 64

What could be the reason?

Helm install unknown flag --name

I have been trying to install nginx ingress using helm version 3

    helm install my-ingress stable/nginx-ingress

But Helm doesn&#39;t seem to be able to find it&#39;s official `stable` repo. It gives the message: 

&gt; Error: failed to download &quot;stable/nginx-ingress&quot; (hint: running `helm
&gt; repo update` may help)


---

I tried `helm repo update`. But it doesn&#39;t help.

I tried listing the repos `helm repo list` but it is empty.


---


I tried to add the stable repo: 

    helm repo add stable https://github.com/helm/charts/tree/master/stable

But it fails with: 

&gt; Error: looks like &quot;https://github.com/helm/charts/tree/master/stable&quot;
&gt; is not a valid chart repository or cannot be reached: failed to fetch
&gt; https://github.com/helm/charts/tree/master/stable/index.yaml : 404 Not
&gt; Found

Helm V3 - Cannot find the official repo

I am building the Dockerfile for python script which will run in minikube windows 10 system below is my Dockerfile



Building the docker using the below command
```docker build -t python-helloworld . ```

and loading that in minikube docker demon
```docker save python-helloworld | (eval $(minikube docker-env) &amp;&amp; docker load)```

Docker File



```
FROM python:3.7-alpine
#add user group and ass user to that group
RUN addgroup -S appgroup &amp;&amp; adduser -S appuser -G appgroup

#creates work dir	
WORKDIR /app

#copy python script to the container folder app
COPY helloworld.py /app/helloworld.py

#user is appuser
USER appuser

ENTRYPOINT  [&quot;python&quot;, &quot;/app/helloworld.py&quot;]
```	


 pythoncronjob.yml file (cron job file)
 
```
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: python-helloworld
spec:
  schedule: &quot;*/1 * * * *&quot;
  jobTemplate:
    spec:
      backoffLimit: 5
      template:
        spec:
          containers:
          - name: python-helloworld
            image: python-helloworld
            imagePullPolicy: IfNotPresent
            command: [/app/helloworld.py]
          restartPolicy: OnFailure
```

Below is the command to run this Kubernetes job
```kubectl create -f pythoncronjob.yml```


But getting the below  error job is not running scuessfully but when u ran the Dockerfile alone its work fine 

standard_init_linux.go:211: exec user process caused &quot;exec format error&quot;

standard_init_linux.go:211: exec user process caused &quot;exec format error&quot;

While deploying mojaloop, Kubernetes responds with the following errors:  

&gt; Error: validation failed: [unable to recognize &quot;&quot;: no matches for kind
&gt; &quot;Deployment&quot; in version &quot;apps/v1beta2&quot;, unable to recognize &quot;&quot;: no
&gt; matches for kind &quot;Deployment&quot; in version &quot;extensions/v1beta1&quot;, unable
&gt; to recognize &quot;&quot;: no matches for kind &quot;StatefulSet&quot; in version
&gt; &quot;apps/v1beta2&quot;, unable to recognize &quot;&quot;: no matches for kind
&gt; &quot;StatefulSet&quot; in version &quot;apps/v1beta1&quot;]



My Kubernetes version is 1.16.  
How can I fix the problem with the API version?  
From investigating, I have found that Kubernetes doesn&#39;t support apps/v1beta2, apps/v1beta1.  
How can I make Kubernetes use a not deprecated version or some other supported version?  
 
I am new to Kubernetes and anyone who can support me I am happy 



Content Type	Original Author	Original Content on Stackoverflow
Question	muratcavus	View Question on Stackoverflow
Solution 1 - Kubernetes	stratovarius	View Answer on Stackoverflow
Solution 2 - Kubernetes	Brimstedt	View Answer on Stackoverflow

How to rolling restart pods without changing deployment yaml in kubernetes?

Kubernetes Problem Overview

Kubernetes Solutions

Solution 1 - Kubernetes

Solution 2 - Kubernetes

Why is an ObservedObject array not updated in my SwiftUI application?

Is it legal for source code containing undefined behavior to crash the compiler?

Attributions