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

Install Confluence on AWS via Kubernetes

Hi all!

 

I am trying to install Confluence using  this documentation on AWS. I managed to complete all of the steps, but when Kubernetes at the end tries to schedule a confluence pod to run on one of the nodes I get an error (via command kubectl describe nodes) like

0/2 nodes are available: 2 Insufficient cpu. preemption: 0/2 nodes are available: 2 No preemption victims found for incoming pod.

 

I tried googling and supposedly this means that the pods have no available CPU capacity, so I event tried propping up 4 nodes, but still the same error.

 

There are definitely available resources so I'm confused by the message.

2 answers

1 accepted

0 votes
Answer accepted

I finally managed to deploy this. For anyone stumbling over this I have a writeup on my wiki here https://dw.exitstatus0.com/doku.php?id=wiki:confluence_aws_deploy. Hope it helps someone else.

0 votes
Yevhen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 09, 2023 • edited

@AM perhaps your nodes do not have enough cpu or memory. You may want to override the default requests

Adding more nodes won't help if they are the same nodes with less than 2 vCPU available. You may need to use larger nodes or decrease cpu request.

Hi Yevhen, thank you!

I will try that, but IMHO this deployment should have been tested by Atlassian, since these are the default values.

Yevhen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 10, 2023

The deployments are continuously tested. The default values are close to prod values, and having 2 vCPU available isn't a huge resources request, imho.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events