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,464,962
Community Members
 
Community Events
176
Community Groups

Do we have helm charts for bitbucket?

Do we have helm charts for bitbucket?

2 answers

1 accepted

0 votes
Answer accepted
Daniel Eads Atlassian Team Mar 24, 2020

Hi there,

For some explanation to other readers, helm charts are descriptors for deploying containers into kubernetes. You could think of them like a template for deploying applications in kubernetes (which is a popular orchestration platform for containers). To people who haven't worked with containers before, this would be a similar concept to a VM image in a virtualization environment.

The quick answer is that Atlassian does not currently provide helm charts for any product. I am aware of third-party helm charts for Jira and Confluence: https://github.com/stevehipwell/helm-charts

Atlassian does however provide docker images for Bitbucket, which would be useful in creating your own helm chart:
https://hub.docker.com/r/atlassian/bitbucket-server/

If you do create your own helm chart and make it available in a public repo, post it here! I'm quite sure others in the Community would be glad to have one available and help contribute to it.

Cheers,
Daniel

Hello Daniel, 

Thanks for response. I was off for sometime, so my reply took time. We have helm chart for 5.X version. But when I try to upgrade it to 6.X we are facing issue. Do you know what is the differance between 5.x vs 6.x?

Daniel Eads Atlassian Team Apr 14, 2020

This page explains in easy-to-digest detail all the significant changes between versions:

Bitbucket upgrade matrix 

On the jump from 5.x to 6.x, there weren't major breaking platform changes - more details about the upgrade are in the Bitbucket Server 6.0 release notes. I wouldn't expect that upgrade to completely break a system, although I imagine it's possible changes to the underlying elasticsearch service might not translate correctly to a helm chart.

Given some details about the issue you have, I might be able to provide some guidance. It sounds like you've either built your own helm chart or acquired one from an unknown third party though, so I do need to call out that I won't be super helpful in regards to the helm chart itself without seeing both copies.

Sure Daniel, let me know what you need for this. :)

Daniel Eads Atlassian Team Apr 16, 2020

Would you be able to provide this information?:

  1. What issue do you face when trying to upgrade?
  2. Can you provide the helm chart you are using for 5.X?
  3. Are you trying to use the same helm chart when trying to upgrade to 6.X?

Thanks!

1.  Pods are not coming up. End up in error. Says readiness probe error. 

2. It's in private repo, so need to find a way.

3. Yes. 

 

Br,

Krishna

Daniel Eads Atlassian Team Apr 27, 2020

Thanks for the extra info Krishna! The readiness probe will fail if Bitbucket hasn't been able to start for some reason, but we'll need to dig into the application logs to figure out why. I'd like to try launching both Bitbucket 5.x and 6.x on my infrastructure with your helm chart. I understand the helm chart is in a private repo, but if you could copy and paste it to something like Bitbucket Cloud snippets, pastebin, or a gist, that would allow me to work on the chart and see if I can determine what's up. Of course, strip out any potentially private info in the chart if there are things in the chart that aren't stored as variables/secrets. Thanks!

Hello Daniel,

We were using AWS efs in Bitbucket architecture. After suggestion from documentation, I moved AWS EFS to normal NFS. Now readiness probe is green, but getting new errors. 

2020-06-11 05:04:24,857 WARN  [spring-startup]  o.s.w.c.s.XmlWebApplicationContext Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'homeLayout' defined in class path resource [critical-context.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.stash.internal.HomeLayout]: Constructor threw exception; nested exception is java.lang.IllegalStateException: Could not create /var/atlassian/application-data/bitbucket/shared/config/upgrades

 

 

 

2020-06-11 05:04:24,872 ERROR [spring-startup]  c.a.j.s.w.s.JohnsonDispatcherServlet SpringMVC dispatcher [springMvc] could not be started

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'homeLayout' defined in class path resource [critical-context.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.stash.internal.HomeLayout]: Constructor threw exception; nested exception is java.lang.IllegalStateException: Could not create /var/atlassian/application-data/bitbucket/shared/config/upgrades

at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:304)

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)

at javax.servlet.GenericServlet.init(GenericServlet.java:158)

at java.lang.Thread.run(Thread.java:748)

... 18 frames trimmed

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.stash.internal.HomeLayout]: Constructor threw exception; nested exception is java.lang.IllegalStateException: Could not create /var/atlassian/application-data/bitbucket/shared/config/upgrades

at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:184)

... 5 common frames omitted

Caused by: java.lang.IllegalStateException: Could not create /var/atlassian/application-data/bitbucket/shared/config/upgrades

at com.atlassian.bitbucket.util.MoreFiles.mkdir(MoreFiles.java:271)

at com.atlassian.bitbucket.util.MoreFiles.mkdir(MoreFiles.java:294)

at com.atlassian.stash.internal.home.DefaultHomeSubdirectoryResolver.create(DefaultHomeSubdirectoryResolver.java:28)

at com.atlassian.stash.internal.HomeLayout.<init>(HomeLayout.java:129)

at com.atlassian.stash.internal.HomeLayout.<init>(HomeLayout.java:98)

at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:172)

... 5 common frames omitted

Caused by: java.nio.file.AccessDeniedException: /var/atlassian/application-data/bitbucket/shared/config/upgrades

at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)

at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)

at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)

at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)

at java.nio.file.Files.createDirectory(Files.java:674)

at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)

at java.nio.file.Files.createDirectories(Files.java:767)

at com.atlassian.bitbucket.util.MoreFiles.mkdir(MoreFiles.java:262)

... 10 common frames omitted

 

 

2020-06-12 09:10:23,846 WARN  [http-nio-7990-exec-10]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [authenticationAttributeFilter]; no Spring WebApplicationContext is available

2020-06-12 09:10:23,846 WARN  [http-nio-7990-exec-10]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [rateLimitFilter]; no Spring WebApplicationContext is available

2020-06-12 09:10:23,846 WARN  [http-nio-7990-exec-10]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [standardResponseHeadersFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,845 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [hazelcastFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,846 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [requestAttributeFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,846 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [entityMovedFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,846 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [pluginProvidedAuthenticationFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,846 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [trustedApplicationsAuthenticationFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,846 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [goGetFilter]; no Spring WebApplicationContext is available

2020-06-12 09:11:23,846 WARN  [http-nio-7990-exec-1]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [springSecurityFilterChain]; no Spring WebApplicationContext is available

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events