Skip to content

Commit

Permalink
Fix KubeExec args in cassandra blueprint (#1277)
Browse files Browse the repository at this point in the history
In the cassandra-blueprint for `KubeExec` function
in 2 phases we were using `containers` arguments which
is not supported by the function.
This has been working I think, because the container
defaults to the main container in the pod.
The is the reason instead of correct the typo
am removing it so that the behaviour, how it has
been runnig till now would not be changed.

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
  • Loading branch information
viveksinghggits and mergify[bot] committed Mar 10, 2022
1 parent 4ea5ff8 commit 56c153e
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions examples/stable/cassandra/cassandra-blueprint.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,6 @@ actions:
args:
namespace: "{{ .StatefulSet.Namespace }}"
pod: "{{ index .StatefulSet.Pods 0}}"
containers: "cassandra"
command:
- bash
- -o
Expand Down Expand Up @@ -120,7 +119,6 @@ actions:
args:
namespace: "{{ .StatefulSet.Namespace }}"
pod: "{{ index .StatefulSet.Pods 0 }}"
containers: "cassandra"
command:
- bash
- -o
Expand Down

0 comments on commit 56c153e

Please sign in to comment.