Description
Context
According to the docker hub page a known issue with the current Bamboo Docker container is that it does not have support for a reverse proxy setup. This is a little weird as we currently have a setup which includes:
- Jira Software
- Confluence
- Bitbucket
All of the above have support for reverse proxies but for some reason Bamboo doesn't.
User Story
As a DevOps engineer
I want to configure Bamboo Server on my infrastructure using a reverse proxy
So that Bamboo can be accessed securely and meet my organisations security standards
Acceptance Criteria
- Reverse Proxy settings can be passed as Variables for the Docker container
- ATL_PROXY_NAME (default: NONE)
- ATL_PROXY_PORT (default: NONE)
- ATL_TOMCAT_PORT (default: 8080)
- ATL_TOMCAT_SCHEME (default: http)
- ATL_TOMCAT_SECURE (default: false)
- ATL_TOMCAT_CONTEXTPATH (default: NONE)
- Additional Tomcat options are also supported
- ATL_TOMCAT_MGMT_PORT (default: 8005)
- ATL_TOMCAT_MAXTHREADS (default: 100)
- ATL_TOMCAT_MINSPARETHREADS (default: 10)
- ATL_TOMCAT_CONNECTIONTIMEOUT (default: 20000)
- ATL_TOMCAT_ENABLELOOKUPS (default: false)
- ATL_TOMCAT_PROTOCOL (default: HTTP/1.1)
- ATL_TOMCAT_ACCEPTCOUNT (default: 10)
- Bamboo Server can be accessed via Reverse Proxy
Attachments
Issue Links
- duplicates
-
BAM-20588 Add support for reverse proxy to atlassian/bamboo-server docker image
- Closed