Skip to content

Commit

Permalink
Merge pull request janus-idp#133 from janus-idp/renovate/backstage-1.x
Browse files Browse the repository at this point in the history
chore(deps): update helm release backstage to v1.4.0
  • Loading branch information
tumido committed Oct 24, 2023
2 parents c02e7a4 + 493dd6a commit ab8d72b
Show file tree
Hide file tree
Showing 4 changed files with 122 additions and 7 deletions.
6 changes: 3 additions & 3 deletions charts/backstage/Chart.lock
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ dependencies:
version: 2.13.3
- name: backstage
repository: https://backstage.github.io/charts
version: 1.3.0
digest: sha256:5313fd2b57ff358271413040450040556c448a19e869d259e3f1e75152432124
generated: "2023-10-24T11:31:31.545635545Z"
version: 1.4.0
digest: sha256:8bfa57e3af51e465cae1bc74eac45c1fafa5b3e52cf061cbdf4072fce3197387
generated: "2023-10-24T11:42:57.043238218Z"
4 changes: 2 additions & 2 deletions charts/backstage/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ dependencies:
version: "2.13.3"
- name: backstage
repository: https://backstage.github.io/charts
version: "1.3.0"
version: "1.4.0"
alias: upstream
home: https://janus-idp.io
icon: https://avatars.githubusercontent.com/u/117844786
Expand All @@ -41,4 +41,4 @@ sources:
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 2.6.3
version: 2.7.0
4 changes: 2 additions & 2 deletions charts/backstage/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
# Janus-IDP Backstage Helm Chart

[![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/janus-idp&style=flat-square)](https://artifacthub.io/packages/search?repo=janus-idp)
![Version: 2.6.3](https://img.shields.io/badge/Version-2.6.3-informational?style=flat-square)
![Version: 2.7.0](https://img.shields.io/badge/Version-2.7.0-informational?style=flat-square)
![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)

A Helm chart for deploying a Backstage application
Expand Down Expand Up @@ -121,7 +121,7 @@ Kubernetes: `>= 1.19.0-0`

| Repository | Name | Version |
|------------|------|---------|
| https://backstage.github.io/charts | upstream(backstage) | 1.3.0 |
| https://backstage.github.io/charts | upstream(backstage) | 1.4.0 |
| https://charts.bitnami.com/bitnami | common | 2.13.3 |

## Values
Expand Down
115 changes: 115 additions & 0 deletions charts/backstage/values.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -3992,6 +3992,121 @@
"title": "The count of deployment revisions",
"type": "integer"
},
"startupProbe": {
"description": "Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic.",
"properties": {
"exec": {
"description": "ExecAction describes a \"run in container\" action.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.",
"items": {
"type": "string"
},
"type": "array"
}
},
"type": "object"
},
"failureThreshold": {
"description": "Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.",
"type": "integer"
},
"httpGet": {
"description": "HTTPGetAction describes an action based on HTTP Get requests.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set \"Host\" in httpHeaders instead.",
"type": "string"
},
"httpHeaders": {
"description": "Custom headers to set in the request. HTTP allows repeated headers.",
"items": {
"description": "HTTPHeader describes a custom header to be used in HTTP probes",
"properties": {
"name": {
"description": "The header field name",
"type": "string"
},
"value": {
"description": "The header field value",
"type": "string"
}
},
"required": [
"name",
"value"
],
"type": "object"
},
"type": "array"
},
"path": {
"description": "Path to access on the HTTP server.",
"type": "string"
},
"port": {
"oneOf": [
{
"type": "string"
},
{
"type": "integer"
}
]
},
"scheme": {
"description": "Scheme to use for connecting to the host. Defaults to HTTP.",
"type": "string"
}
},
"required": [
"port"
],
"type": "object"
},
"initialDelaySeconds": {
"description": "Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"type": "integer"
},
"periodSeconds": {
"description": "How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.",
"type": "integer"
},
"successThreshold": {
"description": "Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1.",
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocketAction describes an action based on opening a socket",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
"type": "string"
},
"port": {
"oneOf": [
{
"type": "string"
},
{
"type": "integer"
}
]
}
},
"required": [
"port"
],
"type": "object"
},
"timeoutSeconds": {
"description": "Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"type": "integer"
}
},
"type": "object"
},
"tolerations": {
"default": [],
"description": "Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/",
Expand Down

0 comments on commit ab8d72b

Please sign in to comment.