Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,888
Community Members
 
Community Events
176
Community Groups

How can I Run more than one kubectl commands in a pipe atlassian/kubectl-run:3.2.0

I want to run multiple  commands line 

first is deleting an exicting pod then apply the new pod  x1and apply other pod.

Actually each time I excute apply cmd it brings me a new pod where I want it to replace the existing one.

2 answers

1 vote
Ben Atlassian Team Apr 25, 2022

G'day!

To run multiple commands within kubectl, you would specify this within your YML configuration using the following syntax inside the specification of the pods contents when listing commands to execute:

command: ["/bin/sh","-c"]
args: ["command one; command two && command three"]

I believe this StackOverflow discussion which I have found will also help to point you in the right direction:
https://stackoverflow.com/questions/33887194/how-to-set-multiple-commands-in-one-yaml-file-with-kubernetes

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)



 

Hi , 

When I push the image to the server it creates a new pod X-ID1 or I already have pod X-ID2 with diferent ID let's say.

So is there a way to prevent that to happen?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events