diff --git a/bitnami/aspnet-core/Chart.yaml b/bitnami/aspnet-core/Chart.yaml
index 768adfe489060b..f7658b4113412e 100644
--- a/bitnami/aspnet-core/Chart.yaml
+++ b/bitnami/aspnet-core/Chart.yaml
@@ -21,4 +21,4 @@ name: aspnet-core
 sources:
   - https://github.com/bitnami/bitnami-docker-aspnet-core
   - https://dotnet.microsoft.com/apps/aspnet
-version: 1.1.1
+version: 1.1.2
diff --git a/bitnami/aspnet-core/README.md b/bitnami/aspnet-core/README.md
index e21bf2f6cbe897..11b6dc23827ff8 100644
--- a/bitnami/aspnet-core/README.md
+++ b/bitnami/aspnet-core/README.md
@@ -217,24 +217,6 @@ It is strongly recommended to use immutable tags in a production environment. Th
 
 Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
 
-### Production configuration
-
-This chart includes a `values-production.yaml` file where you can find some parameters oriented to production configuration in comparison to the regular `values.yaml`. You can use this file instead of the default one.
-
-- Increase number of replicas to 3:
-
-```diff
-- replicaCount: 1
-+ replicaCount: 3
-```
-
-- Enable Pod Disruption Budget:
-
-```diff
-- pdb.enabled: false
-+ pdb.enabled: true
-```
-
 ### Deploying your custom ASP.NET Core application
 
 The ASP.NET Core chart allows you to deploy a custom application using one of the following methods:
diff --git a/bitnami/aspnet-core/values-production.yaml b/bitnami/aspnet-core/values-production.yaml
deleted file mode 100644
index 1f9110bb4d130f..00000000000000
--- a/bitnami/aspnet-core/values-production.yaml
+++ /dev/null
@@ -1,521 +0,0 @@
-## Global Docker image parameters
-## Please, note that this will override the image parameters, including dependencies, configured to use the global value
-## Current available global Docker image parameters: imageRegistry and imagePullSecrets
-##
-# global:
-#   imageRegistry: myRegistryName
-#   imagePullSecrets:
-#     - myRegistryKeySecretName
-
-## Force target Kubernetes version (using Helm capabilites if not set)
-##
-kubeVersion:
-
-## Bitnami ASP.NET Core image
-## ref: https://hub.docker.com/r/bitnami/aspnet-core/tags/
-##
-image:
-  registry: docker.io
-  repository: bitnami/aspnet-core
-  tag: 3.1.9-debian-10-r81
-  ## Specify a imagePullPolicy
-  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
-  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
-  ##
-  pullPolicy: IfNotPresent
-  ## Optionally specify an array of imagePullSecrets.
-  ## Secrets must be manually created in the namespace.
-  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
-  ##
-  # pullSecrets:
-  #   - myRegistryKeySecretName
-
-## String to partially override aspnet-core.fullname template (will maintain the release name)
-##
-# nameOverride:
-
-## String to fully override aspnet-core.fullname template
-##
-# fullnameOverride:
-
-## Kubernetes Cluster Domain
-##
-clusterDomain: cluster.local
-
-## Add labels to all the deployed resources
-##
-commonLabels: {}
-
-## Add annotations to all the deployed resources
-##
-commonAnnotations: {}
-
-## Enable to download/build ASP.NET Core app from external git repository.
-## Do not enable it if your docker image already includes your application
-##
-appFromExternalRepo:
-  enabled: true
-  clone:
-    ## Bitnami Git image version
-    ## ref: https://hub.docker.com/r/bitnami/git/tags/
-    ##
-    image:
-      registry: docker.io
-      repository: bitnami/git
-      tag: 2.30.0-debian-10-r11
-      ## Specify a imagePullPolicy
-      ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
-      ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
-      ##
-      pullPolicy: IfNotPresent
-      ## Optionally specify an array of imagePullSecrets.
-      ## Secrets must be manually created in the namespace.
-      ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
-      ##
-      # pullSecrets:
-      #   - myRegistryKeySecretName
-    ## Git repository to clone
-    ##
-    repository: https://github.com/dotnet/AspNetCore.Docs.git
-    ## Git revision to checkout
-    ##
-    revision: master
-  publish:
-    ## Bitnami .NET SDK image version
-    ## ref: https://hub.docker.com/r/bitnami/dotnet-sdk/tags/
-    ##
-    image:
-      registry: docker.io
-      repository: bitnami/dotnet-sdk
-      tag: 3.1.404-debian-10-r57
-      ## Specify a imagePullPolicy
-      ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
-      ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
-      ##
-      pullPolicy: IfNotPresent
-      ## Optionally specify an array of imagePullSecrets.
-      ## Secrets must be manually created in the namespace.
-      ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
-      ##
-      # pullSecrets:
-      #   - myRegistryKeySecretName
-    ## Sub folder under the Git repository containing the ASP.NET Core app
-    ##
-    subFolder: aspnetcore/fundamentals/servers/kestrel/samples/3.x/KestrelSample
-    ## Extra flags to be appended to "dotnet publish" command
-    ##
-    extraFlags: []
-  ## Command to start downloaded ASP.NET Core app
-  ##
-  startCommand: ["dotnet", "KestrelSample.dll"]
-
-## Enable mounting your ASP.NET Core app from an existing PVC
-## Do not enable it if your docker image already includes your application
-##
-appFromExistingPVC:
-  enabled: false
-  ## A existing Persistent Volume Claim containing your ASP.NET Core app
-  ## The value is evaluated as a template
-  ##
-  # existingClaim:
-
-## Command and args for running the container (set to default if not set). Use array form
-##
-command: []
-args: []
-
-## URLs to bind
-##
-bindURLs: http://+:8080
-
-## Additional environment variables to set
-## E.g:
-## extraEnvVars:
-##   - name: FOO
-##     value: BAR
-##
-extraEnvVars: []
-
-## ConfigMap with extra environment variables
-##
-# extraEnvVarsCM:
-
-## Secret with extra environment variables
-##
-# extraEnvVarsSecret:
-
-## Number of replicas to deploy.
-##
-replicaCount: 2
-
-## StrategyType, can be set to RollingUpdate or Recreate by default.
-##
-strategyType: RollingUpdate
-
-## Pod affinity preset
-## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
-## Allowed values: soft, hard
-##
-podAffinityPreset: ""
-
-## Pod anti-affinity preset
-## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
-## Allowed values: soft, hard
-##
-podAntiAffinityPreset: soft
-
-## Node affinity preset
-## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
-## Allowed values: soft, hard
-##
-nodeAffinityPreset:
-  ## Node affinity type
-  ## Allowed values: soft, hard
-  ##
-  type: ""
-  ## Node label key to match
-  ## E.g.
-  ## key: "kubernetes.io/e2e-az-name"
-  ##
-  key: ""
-  ## Node label values to match
-  ## E.g.
-  ## values:
-  ##   - e2e-az1
-  ##   - e2e-az2
-  ##
-  values: []
-
-## Affinity for pod assignment. Evaluated as a template.
-## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
-##
-affinity: {}
-
-## Node labels for pod assignment. Evaluated as a template.
-## ref: https://kubernetes.io/docs/user-guide/node-selection/
-##
-nodeSelector: {}
-
-## Tolerations for pod assignment. Evaluated as a template.
-## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
-##
-tolerations: []
-
-## Annotations for server pods.
-## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
-##
-podAnnotations: {}
-
-## ASP.NET Core pods' priority.
-## ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
-##
-# priorityClassName: ""
-
-## lifecycleHooks for the ASP.NET Core container to automate configuration before or after startup.
-##
-lifecycleHooks: {}
-
-## ASP.NET Core pods' Security Context.
-## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
-##
-podSecurityContext:
-  enabled: false
-  ## sysctl settings
-  ## Example:
-  ## sysctls:
-  ## - name: net.core.somaxconn
-  ##   value: "10000"
-  ##
-  sysctls: {}
-
-## ASP.NET Core containers' Security Context (only main container).
-## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
-##
-containerSecurityContext:
-  enabled: false
-  runAsUser: 0
-
-## Deployment Container Port
-##
-containerPort: 8080
-
-## ASP.NET Core containers' resource requests and limits.
-## ref: http://kubernetes.io/docs/user-guide/compute-resources/
-##
-resources:
-  # We usually recommend not to specify default resources and to leave this as a conscious
-  # choice for the user. This also increases chances charts run on environments with little
-  # resources, such as Minikube. If you do want to specify resources, uncomment the following
-  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-  limits: {}
-  #   cpu: 100m
-  #   memory: 128Mi
-  requests: {}
-  #   cpu: 100m
-  #   memory: 128Mi
-
-## ASP.NET Core pods' liveness and readiness probes. Evaluated as a template.
-## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
-##
-livenessProbe:
-  enabled: true
-  initialDelaySeconds: 10
-  timeoutSeconds: 1
-  periodSeconds: 20
-  failureThreshold: 6
-  successThreshold: 1
-readinessProbe:
-  enabled: true
-  initialDelaySeconds: 10
-  timeoutSeconds: 1
-  periodSeconds: 20
-  failureThreshold: 6
-  successThreshold: 1
-
-## Custom Liveness probes for ASP.NET Core pods
-##
-customLivenessProbe: {}
-
-## Custom Rediness probes ASP.NET Core pods
-##
-customReadinessProbe: {}
-
-## extraVolumes and extraVolumeMounts allows you to mount other volumes
-## Examples:
-## extraVolumeMounts:
-##   - name: extras
-##     mountPath: /usr/share/extras
-##     readOnly: true
-## extraVolumes:
-##   - name: extras
-##     emptyDir: {}
-##
-extraVolumeMounts: []
-extraVolumes: []
-
-## Add init containers to the ASP.NET Core pods.
-## Example:
-## initContainers:
-##   - name: your-image-name
-##     image: your-image
-##     imagePullPolicy: Always
-##     ports:
-##       - name: portname
-##         containerPort: 1234
-##
-initContainers: {}
-
-## Add sidecars to the ASP.NET Core pods.
-## Example:
-## sidecars:
-##   - name: your-image-name
-##     image: your-image
-##     imagePullPolicy: Always
-##     ports:
-##       - name: portname
-##         containerPort: 1234
-##
-sidecars: {}
-
-## Extra objects to deploy (value evaluated as a template)
-##
-extraDeploy: []
-
-## ASP.NET Core Pod Disruption Budget configuration
-## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
-##
-pdb:
-  create: true
-  ## Min number of pods that must still be available after the eviction
-  ##
-  minAvailable: 1
-  ## Max number of pods that can be unavailable after the eviction
-  ##
-  # maxUnavailable: 1
-
-## ASP.NET Core Autoscaling parameters.
-##
-autoscaling:
-  enabled: false
-  minReplicas: 1
-  maxReplicas: 11
-  # targetCPU: 50
-  # targetMemory: 50
-
-## ASP.NET Core Service parameters.
-##
-service:
-  ## Service type.
-  ##
-  type: ClusterIP
-  ## Service port.
-  ##
-  port: 80
-  ## Specify the nodePort value for the LoadBalancer and NodePort service types.
-  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
-  ##
-  # nodePort:
-  ## Service clusterIP.
-  ##
-  # clusterIP: None
-  ## Enable client source IP preservation
-  ## ref http://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
-  ##
-  externalTrafficPolicy: Cluster
-  ## Set the LoadBalancer service type to internal only.
-  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
-  ##
-  # loadBalancerIP:
-  ## Load Balancer sources.
-  ## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
-  ##
-  # loadBalancerSourceRanges:
-  # - 10.10.10.0/24
-  ## Provide any additional annotations which may be required. Evaluated as a template.
-  ##
-  annotations: {}
-
-## Configure the ingress resource that allows you to access to you ASP.NET Core app
-##
-ingress:
-  ## Set to true to enable ingress record generation
-  ##
-  enabled: false
-
-  ## Override API Version (automatically detected if not set)
-  ##
-  apiVersion:
-
-  ## Ingress Path type
-  ##
-  pathType: ImplementationSpecific
-
-  ## Ingress Path
-  ##
-  path: /
-
-  ## Set this to true in order to add the corresponding annotations for cert-manager
-  ##
-  certManager: false
-
-  ## When the ingress is enabled, a host pointing to this will be created
-  ##
-  hostname: aspnet-core.local
-
-  ## Ingress annotations done as key:value pairs
-  ## For a full list of possible ingress annotations, please see
-  ## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
-  ##
-  ## If certManager is set to true, annotation kubernetes.io/tls-acme: "true" will automatically be set
-  ##
-  annotations: {}
-
-  ## Enable TLS configuration for the hostname defined at ingress.hostname parameter
-  ## TLS certificates will be retrieved from a TLS secret with name: {{- printf "%s-tls" .Values.ingress.hostname }}
-  ## You can use the ingress.secrets parameter to create this TLS secret, relay on cert-manager to create it, or
-  ## let the chart create self-signed certificates for you
-  ##
-  tls: false
-
-  ## The list of additional hostnames to be covered with this ingress record.
-  ## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
-  ## extraHosts:
-  ## - name: aspnet-core.local
-  ##   path: /
-  ##
-
-  ## The tls configuration for additional hostnames to be covered with this ingress record.
-  ## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
-  ## extraTls:
-  ## - hosts:
-  ##     - aspnet-core.local
-  ##   secretName: aspnet-core.local-tls
-  ##
-
-  ## If you're providing your own certificates, please use this to add the certificates as secrets
-  ## key and certificate should start with -----BEGIN CERTIFICATE----- or -----BEGIN RSA PRIVATE KEY-----
-  ## name should line up with a secretName set further up
-  ##
-  ## If it is not set and you're using cert-manager, this is unneeded, as it will create the secret for you
-  ## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created
-  ## It is also possible to create and manage the certificates outside of this helm chart
-  ## Please see README.md for more information
-  ##
-  secrets: []
-  ## - name: aspnet-core.local-tls
-  ##   key:
-  ##   certificate:
-  ##
-
-healthIngress:
-  ## Set to true to enable heallth ingress record generation
-  ##
-  enabled: false
-
-  ## Set this to true in order to add the corresponding annotations for cert-manager
-  ##
-  certManager: false
-
-  ## When the heallth ingress is enabled, a host pointing to this will be created
-  ##
-  hostname: aspnet-core.local
-
-  ## Ingress annotations done as key:value pairs
-  ## For a full list of possible ingress annotations, please see
-  ## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
-  ##
-  ## If certManager is set to true, annotation kubernetes.io/tls-acme: "true" will automatically be set
-  ##
-  annotations: {}
-
-  ## Enable TLS configuration for the hostname defined at ingress.hostname parameter
-  ## TLS certificates will be retrieved from a TLS secret with name: {{- printf "%s-tls" .Values.ingress.hostname }}
-  ## You can use the ingress.secrets parameter to create this TLS secret, relay on cert-manager to create it, or
-  ## let the chart create self-signed certificates for you
-  ##
-  tls: false
-
-  ## The list of additional hostnames to be covered with this heallth ingress record.
-  ## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
-  ## extraHosts:
-  ## - name: aspnet-core.local
-  ##   path: /
-  ##
-
-  ## The tls configuration for additional hostnames to be covered with this heallth ingress record.
-  ## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
-  ## extraTls:
-  ## - hosts:
-  ##     - aspnet-core.local
-  ##   secretName: aspnet-core.local-tls
-  ##
-
-  ## If you're providing your own certificates, please use this to add the certificates as secrets
-  ## key and certificate should start with -----BEGIN CERTIFICATE----- or -----BEGIN RSA PRIVATE KEY-----
-  ## name should line up with a secretName set further up
-  ##
-  ## If it is not set and you're using cert-manager, this is unneeded, as it will create the secret for you
-  ## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created
-  ## It is also possible to create and manage the certificates outside of this helm chart
-  ## Please see README.md for more information
-  ##
-  secrets: []
-  ## - name: aspnet-core.local-tls
-  ##   key:
-  ##   certificate:
-  ##
-
-## K8s Service Account.
-## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
-##
-serviceAccount:
-  ## Specifies whether a ServiceAccount should be created.
-  ##
-  create: true
-  ## The name of the ServiceAccount to use.
-  ## If not set and create is true, a name is generated using the aspnet-core.fullname template
-  ##
-  # name:
-  ## Service Account annotations which may be required. Evaluated as a template.
-  ##
-  annotations: {}