[{"_1":2,"_144":-5,"_145":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_138":139},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_55":56,"_57":-7,"_58":-7,"_59":-7,"_60":-7,"_61":-5,"_62":-5,"_63":11,"_64":11,"_48":65,"_128":17,"_96":97,"_129":95,"_130":47,"_31":32,"_131":11,"_132":17,"_133":134,"_135":-5,"_136":11,"_137":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},"content_type","unrecognized","creator",35095401,"digest","sha256:3157d658fb78c9297e36b52b024d8d09d06b5fe94882bf951580401f6078d748","full_size",916391,"id",1263815296,"images",[],"last_updated","2026-08-08T18:13:47.453059Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-09a85c38e48f9fcbe27ce86ee5cadea1c8160d5a470be7534f170591461e72aa.metadata","repository",19064315,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_66":67,"_78":79,"_82":83,"_84":85,"_86":11,"_39":87,"_88":89,"_90":91,"_46":95,"_96":97,"_98":99,"_100":81,"_101":102,"_103":104,"_105":106,"_107":-5,"_108":102,"_109":110,"_111":11,"_112":97,"_113":114,"_119":11,"_120":121,"_125":97,"_126":127},"categories",[68,72,75],{"_46":69,"_70":71},"Languages & frameworks","slug","languages-and-frameworks",{"_46":73,"_70":74},"Integration & delivery","integration-and-delivery",{"_46":76,"_70":77},"Web servers","web-servers","content_types",[80,81,28],"helm","image","date_registered","2023-01-24T10:50:10.08523Z","description","Bitnami Helm chart for Apache Tomcat","is_private","2026-09-20T14:39:07.434738Z","last_modified","2026-09-22T08:07:53.872288Z","media_types",[92,93,94,45],"application/vnd.cncf.helm.config.v1+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","tomcat","namespace","bitnamicharts","pull_count",924353,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Apache Tomcat\n\nApache Tomcat is an open-source web server designed to host and run Java-based web applications. It is a lightweight server with a good performance for applications running in production environments.\n\n[Overview of Apache Tomcat](http://tomcat.apache.org/)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/tomcat\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [Tomcat](https://github.com/bitnami/containers/tree/main/bitnami/tomcat) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\nTomcat implements several Java EE specifications including Java Servlet, JavaServer Pages, Java EL, and WebSocket, and provides a \"pure Java\" HTTP web server environment for Java code to run in.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n- PV provisioner support in the underlying infrastructure\n- ReadWriteMany volumes for deployment scaling\n\n## Installing the Chart\n\nFirst, log in to the OCI registry and create a secret with your registry credentials:\n\n```console\nhelm registry login REGISTRY_NAME\nkubectl create secret docker-registry SECRET_NAME -n NAMESPACE \\\n --docker-server REGISTRY_NAME \\\n --docker-username \"USER\" \\\n --docker-password \"TOKEN\"\n```\n\n> **Note** Replace the placeholders in these commands (`REGISTRY_NAME`, `SECRET_NAME`, `NAMESPACE`, `USER`, and `TOKEN`) with your actual values.\n\nThen install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/tomcat --set \"global.imagePullSecrets[0]=SECRET_NAME\" -n NAMESPACE\n```\n\n> **Note** Replace the placeholders in the `helm install` command (`REGISTRY_NAME`, `REPOSITORY_NAME`, `SECRET_NAME`, and `NAMESPACE`) with your actual values.\n\nThese commands deploy Tomcat on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Gateway API\n\nThis chart provides support for exposing Apache Tomcat using the [Gateway API](https://gateway-api.sigs.k8s.io/) and its `HTTPRoute` resource. If you have a Gateway controller installed on your cluster, such as APISIX, Contour, Envoy Gateway, NGINX Gateway Fabric or Kong Ingress Controller you can utilize the Gateway controller to serve your application. To enable Gateway API integration, set `httpRoute.enabled` to `true`.\nThe Gateway to be used can be customized by setting the `httpRoute.parentRefs` parameter. By default, it will reference a Gateway named `gateway` in the same namespace as the release.\n\nYou can specify the list of hostnames to be mapped to the deployment using the `httpRoute.hostnames` parameter. Additionally, you can customize the rules used to route the traffic to the service by modifying the `httpRoute.matches` and `httpRoute.filters` parameters or adding new rules using the `httpRoute.extraRules` parameter.\n\n### Ingress\n\nThis chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as NGINX Ingress Controller or Contour you can utilize the ingress controller to serve your application. To enable Ingress integration, set `ingress.enabled` to `true`.\n\nThe most common scenario is to have one host name mapped to the deployment. In this case, the `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host.\n\nHowever, it is also possible to have more than one host. To facilitate this, the `ingress.extraHosts` parameter (if available) can be set with the host names specified as an array. The `ingress.extraTLS` parameter (if available) can also be used to add the TLS configuration for extra hosts.\n\n> NOTE: For each host specified in the `ingress.extraHosts` parameter, it is necessary to set a name, path, and any annotations that the Ingress controller should know about. Not all annotations are supported by all Ingress controllers, but [this annotation reference document](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md) lists the annotations supported by many popular Ingress controllers.\n\nAdding the TLS parameter (where available) will cause the chart to generate HTTPS URLs, and the application will be available on port 443. The actual TLS secrets do not have to be generated by this chart. However, if TLS is enabled, the Ingress record will not work until the TLS secret exists.\n\n[Learn more about Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### Update credentials\n\nBitnami charts configure credentials at first boot. Any further change in the secrets or credentials require manual intervention. Follow these instructions:\n\n- Update the user password following [the upstream documentation](https://tomcat.apache.org/)\n- Update the password secret with the new values (replace the SECRET_NAME, USER and PASSWORD placeholders)\n\n```shell\nkubectl create secret generic SECRET_NAME --from-literal=tomcat-username=USER --from-literal=tomcat-password=PASSWORD --dry-run -o yaml | kubectl apply -f -\n```\n\n### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to `true`. This will deploy a sidecar container with [jmx_exporter](https://github.com/prometheus/jmx_exporter) in all pods. It will have the necessary annotations to be automatically scraped by Prometheus.\n\n#### Prometheus requirements\n\nIt is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the [Bitnami Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/prometheus) or the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) to easily have a working Prometheus in your cluster.\n\n#### Integration with Prometheus Operator\n\nThe chart can deploy `PodMonitor` objects for integration with Prometheus Operator installations. To do so, set the value `metrics.podMonitor.enabled=true`. Ensure that the Prometheus Operator `CustomResourceDefinitions` are installed in the cluster or it will fail with the following error:\n\n```text\nno matches for kind \"PodMonitor\" in version \"monitoring.coreos.com/v1\"\n```\n\nInstall the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) for having the necessary CRDs and the Prometheus Operator.\n\n### [Rolling vs Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Use a different Tomcat version\n\nTo modify the application version used in this chart, specify a different version of the image using the `image.tag` parameter and/or a different repository using the `image.repository` parameter.\n\n### Add extra environment variables\n\nTo add extra environment variables (useful for advanced operations like custom init scripts), use the `extraEnvVars` property.\n\n```yaml\nextraEnvVars:\n - name: LOG_LEVEL\n value: DEBUG\n```\n\nAlternatively, define a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values.\n\n### Use Sidecars and Init Containers\n\nIf additional containers are needed in the same pod (such as additional metrics or logging exporters), they can be defined using the `sidecars` config parameter.\n\n```yaml\nsidecars:\n- name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nIf these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter (where available), as shown in the example below:\n\n```yaml\nservice:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\n\n> NOTE: This Helm chart already includes sidecar containers for the Prometheus exporters (where applicable). These can be activated by adding the `--enable-metrics=true` parameter at deployment time. The `sidecars` parameter should therefore only be used for any extra sidecar containers.\n\nIf additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter. Here is an example:\n\n```yaml\ninitContainers:\n - name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nLearn more about [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/) and [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).\n\n### Set Pod affinity\n\nThis chart allows you to set custom Pod affinity using the `affinity` parameter. Find more information about Pod's affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Persistence\n\nThe [Bitnami Tomcat](https://github.com/bitnami/containers/tree/main/bitnami/tomcat) image stores the Tomcat data and configurations at the `/bitnami/tomcat` path of the container.\n\nPersistent Volume Claims (PVCs) are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.\n\nSee the [Parameters](#parameters) section to configure the PVC or to disable persistence.\n\n### Adjust permissions of persistent volume mountpoint\n\nAs the image run as non-root by default, it is necessary to adjust the ownership of the persistent volume so that the container can write data into it.\n\nBy default, the chart is configured to use Kubernetes Security Context to automatically change the ownership of the volume. However, this feature does not work in all Kubernetes distributions.\nAs an alternative, this chart supports using an init container to change the ownership of the volume before mounting it in the final destination.\n\nYou can enable this init container by setting `volumePermissions.enabled` to `true`.\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `disabled` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------- | -------------------------------------------------------------------------------------------- | --------------- |\n| `kubeVersion` | Force target Kubernetes version (using Helm capabilities if not set) | `\"\"` |\n| `nameOverride` | String to partially override common.names.fullname template (will maintain the release name) | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname template | `\"\"` |\n| `commonLabels` | Add labels to all the deployed resources | `{}` |\n| `commonAnnotations` | Add annotations to all the deployed resources | `{}` |\n| `clusterDomain` | Kubernetes Cluster Domain | `cluster.local` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n| `usePasswordFiles` | Mount credentials as files instead of using environment variables | `true` |\n\n### Tomcat parameters\n\n| Name | Description | Value |\n| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------ |\n| `image.registry` | Tomcat image registry | `REGISTRY_NAME` |\n| `image.repository` | Tomcat image repository | `REPOSITORY_NAME/tomcat` |\n| `image.digest` | Tomcat image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | Tomcat image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `image.debug` | Specify if debug logs should be enabled | `false` |\n| `automountServiceAccountToken` | Mount Service Account token in pod | `false` |\n| `hostAliases` | Deployment pod host aliases | `[]` |\n| `tomcatUsername` | Tomcat admin user | `user` |\n| `tomcatPassword` | Tomcat admin password | `\"\"` |\n| `existingSecret` | Use existing secret for credentials details (`tomcatUsername` and `tomcatPassword` will be ignored and picked up from this secret) | `\"\"` |\n| `secretKeys.adminUsernameKey` | Name of key in existing secret to use instead of default `tomcat-username` key to provide Tomcat admin username (overrides `tomcatUsername`). Only used when `existingSecret` is set | `\"\"` |\n| `secretKeys.adminPasswordKey` | Name of key in existing secret to use instead of default `tomcat-password` key to provide Tomcat admin password (overrides `tomcatPassword`). Only used when `existingSecret` is set | `\"\"` |\n| `tomcatInstallDefaultWebapps` | Install default webapps | `false` |\n| `tomcatAllowRemoteManagement` | Enable remote access to management interface | `false` |\n| `catalinaOpts` | Java runtime option used by tomcat JVM | `\"\"` |\n| `command` | Override default container command (useful when using custom images) | `[]` |\n| `args` | Override default container args (useful when using custom images) | `[]` |\n| `extraEnvVars` | Extra environment variables to be set on Tomcat container | `[]` |\n| `extraEnvVarsCM` | Name of existing ConfigMap containing extra environment variables | `\"\"` \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-tomcat-index.html_","has_starred","hub_user","immutable_tags_settings",{"_115":11,"_116":117},"enabled","rules",[118],".*","is_automated","permissions",{"_122":17,"_123":11,"_124":11},"read","write","admin","user","storage_size",71233913,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":140,"_31":32,"_142":-7,"_143":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":141,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/tomcat:sha256-09a85c38e48f9fcbe27ce86ee5cadea1c8160d5a470be7534f170591461e72aa.metadata