选择指南版本

Kubernetes extension

Quarkus offers the ability to automatically generate Kubernetes resources based on sane defaults and user-supplied configuration using dekorate. It currently supports generating resources for vanilla Kubernetes, OpenShift and Knative. Furthermore, Quarkus can deploy the application to a target Kubernetes cluster by applying the generated manifests to the target cluster’s API Server. Finally, when either one of container image extensions is present (see the container image guide for more details), Quarkus has the ability to create a container image and push it to a registry before deploying the application to the target platform.

先决条件

完成这个指南，你需要:

大概15分钟
编辑器
JDK 17+ installed with JAVA_HOME configured appropriately
Apache Maven 3.9.9
如果你愿意的话，还可以选择使用Quarkus CLI
Access to a Kubernetes cluster (Minikube is a viable option)

Kubernetes

Let’s create a new project that contains both the Kubernetes and Jib extensions:

CLI

quarkus create app org.acme:kubernetes-quickstart \
    --extension='rest,kubernetes,jib'
cd kubernetes-quickstart

创建Grade项目，请添加 --gradle 或者 --gradle-kotlin-dsl 参数。

For more information about how to install and use the Quarkus CLI, see the Quarkus CLI guide.

Maven

mvn io.quarkus.platform:quarkus-maven-plugin:3.16.3:create \
    -DprojectGroupId=org.acme \
    -DprojectArtifactId=kubernetes-quickstart \
    -Dextensions='rest,kubernetes,jib'
cd kubernetes-quickstart

创建Grade项目，请添加 -DbuildTool=gradle 或者 -DbuildTool=gradle-kotlin-dsl 参数。

For Windows users:

If using cmd, (don’t use backward slash \ and put everything on the same line)
If using Powershell, wrap -D parameters in double quotes e.g. "-DprojectArtifactId=kubernetes-quickstart"

This added the following dependencies to the build file:

pom.xml

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-rest</artifactId>
</dependency>
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-kubernetes</artifactId>
</dependency>
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-container-image-jib</artifactId>
</dependency>

build.gradle

implementation("io.quarkus:quarkus-rest")
implementation("io.quarkus:quarkus-kubernetes")
implementation("io.quarkus:quarkus-container-image-jib")

By adding these dependencies, we enable the generation of Kubernetes manifests each time we perform a build while also enabling the build of a container image using Jib. For example, following the execution of:

CLI

quarkus build

Maven

./mvnw install

Gradle

./gradlew build

you will notice amongst the other files that are created, two files named kubernetes.json and kubernetes.yml in the target/kubernetes/ directory.

If you look at either file you will see that it contains both a Kubernetes Deployment and a Service.

The full source of the kubernetes.json file looks something like this:

{
  {
    "apiVersion" : "apps/v1",
    "kind" : "Deployment",
    "metadata" : {
      "annotations": {
       "app.quarkus.io/vcs-uri" : "<some url>",
       "app.quarkus.io/commit-id" : "<some git SHA>",
      },
      "labels" : {
        "app.kubernetes.io/name" : "test-quarkus-app",
        "app.kubernetes.io/version" : "1.0.0-SNAPSHOT",
      },
      "name" : "test-quarkus-app"
    },
    "spec" : {
      "replicas" : 1,
      "selector" : {
        "matchLabels" : {
          "app.kubernetes.io/name" : "test-quarkus-app",
          "app.kubernetes.io/version" : "1.0.0-SNAPSHOT",
        }
      },
      "template" : {
        "metadata" : {
          "labels" : {
            "app.kubernetes.io/name" : "test-quarkus-app",
            "app.kubernetes.io/version" : "1.0.0-SNAPSHOT"
          }
        },
        "spec" : {
          "containers" : [ {
            "env" : [ {
              "name" : "KUBERNETES_NAMESPACE",
              "valueFrom" : {
                "fieldRef" : {
                  "fieldPath" : "metadata.namespace"
                }
              }
            } ],
            "image" : "yourDockerUsername/test-quarkus-app:1.0.0-SNAPSHOT",
            "imagePullPolicy" : "Always",
            "name" : "test-quarkus-app"
          } ]
        }
      }
    }
  },
  {
  "apiVersion" : "v1",
  "kind" : "Service",
    "metadata" : {
      "annotations": {
       "app.quarkus.io/vcs-uri" : "<some url>",
       "app.quarkus.io/commit-id" : "<some git SHA>",
      },
      "labels" : {
        "app.kubernetes.io/name" : "test-quarkus-app",
        "app.kubernetes.io/version" : "1.0.0-SNAPSHOT",
      },
      "name" : "test-quarkus-app"
    },
  "spec" : {
    "ports" : [ {
      "name" : "http",
      "port" : 8080,
      "targetPort" : 8080
    } ],
    "selector" : {
      "app.kubernetes.io/name" : "test-quarkus-app",
      "app.kubernetes.io/version" : "1.0.0-SNAPSHOT"
    },
    "type" : "ClusterIP"
  }
 }
}

The generated manifest can be applied to the cluster from the project root using kubectl:

kubectl apply -f target/kubernetes/kubernetes.json

An important thing to note about the Deployment (or StatefulSet) is that is uses yourDockerUsername/test-quarkus-app:1.0.0-SNAPSHOT as the container image of the Pod. The name of the image is controlled by the Jib extension and can be customized using the usual application.properties.

For example with a configuration like:

quarkus.container-image.group=quarkus #optional, default to the system username
quarkus.container-image.name=demo-app #optional, defaults to the application name
quarkus.container-image.tag=1.0       #optional, defaults to the application version

The image that will be used in the generated manifests will be quarkus/demo-app:1.0

Generating idempotent resources

When generating the Kubernetes manifests, Quarkus automatically adds some labels and annotations to give extra information about the generation date or versions. For example:

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    app.quarkus.io/commit-id: 0f8b87788bc446a9347a7961bea8a60889fe1494
    app.quarkus.io/build-timestamp: 2023-02-10 - 13:07:51 +0000
  labels:
    app.kubernetes.io/managed-by: quarkus
    app.kubernetes.io/version: 0.0.1-SNAPSHOT
    app.kubernetes.io/name: example
  name: example
spec:
  ...

The app.quarkus.io/commit-id, app.quarkus.io/build-timestamp labels and the app.kubernetes.io/version annotation might change every time we re-build the Kubernetes manifests which can be problematic when we want to deploy these resources using a Git-Ops tool (because these tools will detect differences and hence will perform a re-deployment).

To make the generated resources Git-Ops friendly and only produce idempotent resources (resources that won’t change every time we build the sources), we need to add the following property:

quarkus.kubernetes.idempotent=true

Moreover, by default the directory where the generated resources are created is target/kubernetes, to change it, we need to use:

quarkus.kubernetes.output-directory=target/kubernetes-with-idempotent

Note that the property quarkus.kubernetes.output-directory is relative to the current project location.

Changing the generated deployment resource

Besides generating a Deployment resource, you can also choose to generate either a StatefulSet, or a Job, or a CronJob resource instead via application.properties:

quarkus.kubernetes.deployment-kind=StatefulSet

Generating Job resources

If you want to generate a Job resource, you need to add the following property to the application.properties:

quarkus.kubernetes.deployment-kind=Job

If you are using the Picocli extension, by default a Job resource will be generated.

You can provide the arguments that will be used by the Kubernetes Job via the property quarkus.kubernetes.arguments. For example, by adding the property quarkus.kubernetes.arguments=A,B.

Finally, the Kubernetes job will be launched every time it is installed in Kubernetes. You can know more about how to run Kubernetes jobs in this link.

You can configure the rest of the Kubernetes Job configuration using the properties under quarkus.kubernetes.job.xxx (see link).

Generating CronJob resources

If you want to generate a CronJob resource, you need to add the following property via the application.properties:

quarkus.kubernetes.deployment-kind=CronJob
# Cron expression to run the job every hour
quarkus.kubernetes.cron-job.schedule=0 * * * *

CronJob resources require the Cron expression to specify when to launch the job via the property quarkus.kubernetes.cron-job.schedule. If not provide, the build will fail.

You can configure the rest of the Kubernetes CronJob configuration using the properties under quarkus.kubernetes.cron-job.xxx (see link).

Namespace

By default, Quarkus omits the namespace in the generated manifests, rather than enforce the default namespace. That means that you can apply the manifest to your chosen namespace when using kubectl, which in the example below is test:

kubectl apply -f target/kubernetes/kubernetes.json -n=test

To specify the namespace in your manifest customize with the following property in your application.properties:

quarkus.kubernetes.namespace=mynamespace

Defining a Docker registry

The Docker registry can be specified with the following property:

quarkus.container-image.registry=my.docker-registry.net

By adding this property along with the rest of the container image properties of the previous section, the generated manifests will use the image my.docker-registry.net/quarkus/demo-app:1.0. The image is not the only thing that can be customized in the generated manifests, as will become evident in the following sections.

Automatic generation of pull secrets

When docker registries are used, users often provide credentials, so that an image is built and pushed to the specified registry during the build.

quarkus.container-image.username=myusername
quarkus.container-image.password=mypassword

Kubernetes will also need these credentials when it comes to pull the image from the registry. This is where image pull secrets are used. An image pull secret is a special kind of secret that contains the required credentials. Quarkus can automatically generate and configure when:

quarkus.kubernetes.generate-image-pull-secret=true

More specifically a `Secret`like the one bellow is genrated:

apiVersion: v1
kind: Secret
metadata:
  name: test-quarkus-app-pull-secret
data:
  ".dockerconfigjson": ewogCSJhdXRocyI6IHsKCQkibXkucmVnaXN0eS5vcmciOiB7CiAJCQkiYXV0aCI6ImJYbDFjMlZ5Ym1GdFpUcHRlWEJoYzNOM2IzSmsiCgkJfQoJfQp9
type: kubernetes.io/dockerconfigjson

And also test-quarkus-app-pull-secret is added to the imagePullSecrets list.

Labels and Annotations

Labels

The generated manifests use the Kubernetes recommended labels. These labels can be customized using quarkus.kubernetes.name, quarkus.kubernetes.version and quarkus.kubernetes.part-of. For example by adding the following configuration to your application.properties:

quarkus.kubernetes.part-of=todo-app
quarkus.kubernetes.name=todo-rest
quarkus.kubernetes.version=1.0-rc.1

As is described in detail in the OpenShift section, customizing OpenShift (or Knative) properties is done in the same way, but replacing kubernetes with openshift (or knative). The previous example for OpenShift would look like this:

quarkus.openshift.part-of=todo-app
quarkus.openshift.name=todo-rest
quarkus.openshift.version=1.0-rc.1

The labels in generated resources will look like:

  "labels" : {
    "app.kubernetes.io/part-of" : "todo-app",
    "app.kubernetes.io/name" : "todo-rest",
    "app.kubernetes.io/version" : "1.0-rc.1"
  }

You can also remove the app.kubernetes.io/version label by applying the following configuration:

quarkus.kubernetes.add-version-to-label-selectors=false

Custom Labels

To add additional custom labels, for example foo=bar just apply the following configuration:

quarkus.kubernetes.labels.foo=bar

When using the quarkus-container-image-jib extension to build a container image, then any label added via the aforementioned property will also be added to the generated container image.

Annotations

Out of the box, the generated resources will be annotated with version control related information that can be used either by tooling, or by the user for troubleshooting purposes.

  "annotations": {
    "app.quarkus.io/vcs-uri" : "<some url>",
    "app.quarkus.io/commit-id" : "<some git SHA>",
   }

Custom Annotations

Custom annotations can be added in a way similar to labels.For example to add the annotation foo=bar and app.quarkus/id=42 just apply the following configuration:

quarkus.kubernetes.annotations.foo=bar
quarkus.kubernetes.annotations."app.quarkus/id"=42

Environment variables

Kubernetes provides multiple ways of defining environment variables:

key/value pairs
import all values from a Secret or ConfigMap
interpolate a single value identified by a given field in a Secret or ConfigMap
interpolate a value from a field within the same resource

Environment variables from key/value pairs

To add a key/value pair as an environment variable in the generated resources:

quarkus.kubernetes.env.vars.my-env-var=foobar

The command above will add MY_ENV_VAR=foobar as an environment variable. Please note that the key my-env-var will be converted to uppercase and dashes will be replaced by underscores resulting in MY_ENV_VAR.

Environment variables from Secret

To add all key/value pairs of Secret as environment variables just apply the following configuration, separating each Secret to be used as source by a comma (,):

quarkus.kubernetes.env.secrets=my-secret,my-other-secret

which would generate the following in the container definition:

envFrom:
  - secretRef:
      name: my-secret
      optional: false
  - secretRef:
      name: my-other-secret
      optional: false

The following extracts a value identified by the keyName field from the my-secret Secret into a foo environment variable:

quarkus.kubernetes.env.mapping.foo.from-secret=my-secret
quarkus.kubernetes.env.mapping.foo.with-key=keyName

This would generate the following in the env section of your container:

- env:
  - name: FOO
    valueFrom:
      secretKeyRef:
        key: keyName
        name: my-secret
        optional: false

It is also possible to add a prefix when you are generating env from Secret, the following configuration creates environment variable from Secret with key foo adding a prefix BAR:

quarkus.kubernetes.env.secrets=foo
quarkus.kubernetes.env.using-prefix."BAR".for-secret=foo

This would generate the following in the env section of your container:

- env:
    envFrom:
    - secretRef:
        name: foo
      prefix: BAR

Environment variables from ConfigMap

To add all key/value pairs from ConfigMap as environment variables just apply the following configuration, separating each ConfigMap to be used as source by a comma (,):

quarkus.kubernetes.env.configmaps=my-config-map,another-config-map

which would generate the following in the container definition:

envFrom:
  - configMapRef:
      name: my-config-map
      optional: false
  - configMapRef:
      name: another-config-map
      optional: false

The following extracts a value identified by the keyName field from the my-config-map ConfigMap into a foo environment variable:

quarkus.kubernetes.env.mapping.foo.from-configmap=my-configmap
quarkus.kubernetes.env.mapping.foo.with-key=keyName

This would generate the following in the env section of your container:

- env:
  - name: FOO
    valueFrom:
      configMapKeyRef:
        key: keyName
        name: my-configmap
        optional: false

It is also possible to add a prefix when you are generating env from ConfigMap, the following configuration creates environment variable from ConfigMap with key foo adding a prefix BAR:

quarkus.kubernetes.env.configmaps=foo
quarkus.kubernetes.prefixes."BAR".for-configmap=foo

This would generate the following in the env section of your container:

- env:
    envFrom:
    - configMapRef:
        name: foo
      prefix: BAR

Environment variables from fields

It’s also possible to use the value from another field to add a new environment variable by specifying the path of the field to be used as a source, as follows:

quarkus.kubernetes.env.fields.foo=metadata.name

As is described in detail in the OpenShift section, customizing OpenShift properties is done in the same way, but replacing kubernetes with openshift. The previous example for OpenShift would look like this:

quarkus.openshift.env.fields.foo=metadata.name

Validation

A conflict between two definitions, e.g. mistakenly assigning both a value and specifying that a variable is derived from a field, will result in an error being thrown at build time so that you get the opportunity to fix the issue before you deploy your application to your cluster where it might be more difficult to diagnose the source of the issue.

Similarly, two redundant definitions, e.g. defining an injection from the same secret twice, will not cause an issue but will indeed report a warning to let you know that you might not have intended to duplicate that definition.

Backwards compatibility

Previous versions of the Kubernetes extension supported a different syntax to add environment variables. The older syntax is still supported but is deprecated, and it’s advised that you migrate to the new syntax.

Table 1. Old vs. new syntax
	Old	New
Plain variable	`quarkus.kubernetes.env-vars.my-env-var.value=foobar`	`quarkus.kubernetes.env.vars.my-env-var=foobar`
From field	`quarkus.kubernetes.env-vars.my-env-var.field=foobar`	`quarkus.kubernetes.env.fields.my-env-var=foobar`
All from `ConfigMap`	`quarkus.kubernetes.env-vars.xxx.configmap=foobar`	`quarkus.kubernetes.env.configmaps=foobar`
All from `Secret`	`quarkus.kubernetes.env-vars.xxx.secret=foobar`	`quarkus.kubernetes.env.secrets=foobar`
From one `Secret` field	`quarkus.kubernetes.env-vars.foo.secret=foobar`	`quarkus.kubernetes.env.mapping.foo.from-secret=foobar`
	`quarkus.kubernetes.env-vars.foo.value=field`	`quarkus.kubernetes.env.mapping.foo.with-key=field`
From one `ConfigMap` field	`quarkus.kubernetes.env-vars.foo.configmap=foobar`	`quarkus.kubernetes.env.mapping.foo.from-configmap=foobar`
	`quarkus.kubernetes.env-vars.foo.value=field`	`quarkus.kubernetes.env.mapping.foo.with-key=field`

If you redefine the same variable using the new syntax while keeping the old syntax, ONLY the new version will be kept and a warning will be issued to alert you of the problem.For example, if you define both quarkus.kubernetes.env-vars.my-env-var.value=foobar and quarkus.kubernetes.env.vars.my-env-var=newValue, the extension will only generate an environment variable MY_ENV_VAR=newValue and issue a warning.

Mounting volumes

The Kubernetes extension allows the user to configure both volumes and mounts for the application. Any volume can be mounted with a simple configuration:

quarkus.kubernetes.mounts.my-volume.path=/where/to/mount

This will add a mount to the pod for volume my-volume to path /where/to/mount. The volumes themselves can be configured as shown in the sections below.

Secret volumes

quarkus.kubernetes.secret-volumes.my-volume.secret-name=my-secret

ConfigMap volumes

quarkus.kubernetes.config-map-volumes.my-volume.config-map-name=my-config-map

Passing application configuration

Quarkus supports passing configuration from external locations (via SmallRye Config). This usually requires setting an additional environment variable or system property. When you need to use a secret or a config map for the purpose of application configuration, you need to:

define a volume
mount the volume
create an environment variable for SMALLRYE_CONFIG_LOCATIONS

To simplify things, quarkus provides single step alternative:

quarkus.kubernetes.app-secret=<name of the secret containing the configuration>

quarkus.kubernetes.app-config-map=<name of the config map containing the configuration>

When these properties are used, the generated manifests will contain everything required. The application config volumes will be created using path: /mnt/app-secret and /mnt/app-config-map for secrets and configmaps respectively.

Note: Users may use both properties at the same time.

Changing the number of replicas

To change the number of replicas from 1 to 3:

quarkus.kubernetes.replicas=3

Add readiness and liveness probes

By default, the Kubernetes resources do not contain readiness and liveness probes in the generated Deployment. Adding them however is just a matter of adding the SmallRye Health extension like so:

pom.xml

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-smallrye-health</artifactId>
</dependency>

build.gradle

implementation("io.quarkus:quarkus-smallrye-health")

The values of the generated probes will be determined by the configured health properties: quarkus.smallrye-health.root-path, quarkus.smallrye-health.liveness-path and quarkus.smallrye-health.readiness-path. More information about the health extension can be found in the relevant guide.

Customizing the readiness probe

To set the initial delay of the probe to 20 seconds and the period to 45:

quarkus.kubernetes.readiness-probe.initial-delay=20s
quarkus.kubernetes.readiness-probe.period=45s

Add hostAliases

To add entries to a Pod’s /etc/hosts file (more information can be found in Kubernetes documentation), just apply the following configuration:

quarkus.kubernetes.hostaliases."10.0.0.0".hostnames=foo.com,bar.org

This would generate the following hostAliases section in the deployment definition:

kind: Deployment
spec:
  template:
    spec:
      hostAliases:
      - hostnames:
        - foo.com
        - bar.org
        ip: 10.0.0.0

Container Resources Management

CPU & Memory limits and requests can be applied to a Container (more info in Kubernetes documentation) using the following configuration:

quarkus.kubernetes.resources.requests.memory=64Mi
quarkus.kubernetes.resources.requests.cpu=250m
quarkus.kubernetes.resources.limits.memory=512Mi
quarkus.kubernetes.resources.limits.cpu=1000m

This would generate the following entry in the container section:

containers:
  - resources:
    limits:
      cpu: 1000m
      memory: 512Mi
    requests:
      cpu: 250m
      memory: 64Mi

Exposing your application in Kubernetes

Kubernetes exposes applications using Ingress resources. To generate the Ingress resource, just apply the following configuration:

quarkus.kubernetes.ingress.expose=true

This would generate the following Ingress resource:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    app.quarkus.io/commit-id: a58d2211c86f07a47d4b073ea9ce000d2c6828d5
    app.quarkus.io/build-timestamp: 2022-06-29 - 13:22:41 +0000
  labels:
    app.kubernetes.io/name: kubernetes-with-ingress
    app.kubernetes.io/version: 0.1-SNAPSHOT
  name: kubernetes-with-ingress
spec:
  rules:
    - http:
        paths:
          - backend:
              service:
                name: kubernetes-with-ingress
                port:
                  name: http
            path: /
            pathType: Prefix

After deploying these resources to Kubernetes, the Ingress resource will allow unsecured connections to reach out your application.

Adding Ingress rules

To customize the default host and path properties of the generated Ingress resources, you need to apply the following configuration:

quarkus.kubernetes.ingress.expose=true
# To change the Ingress host. By default, it's empty.
quarkus.kubernetes.ingress.host=prod.svc.url
# To change the Ingress path of the generated Ingress rule. By default, it's "/".
quarkus.kubernetes.ports.http.path=/prod

This would generate the following Ingress resource:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  labels:
    app.kubernetes.io/name: kubernetes-with-ingress
    app.kubernetes.io/version: 0.1-SNAPSHOT
  name: kubernetes-with-ingress
spec:
  rules:
    - host: prod.svc.url
      http:
        paths:
          - backend:
              service:
                name: kubernetes-with-ingress
                port:
                  name: http
            path: /prod
            pathType: Prefix

Additionally, you can also add new Ingress rules by adding the following configuration:

# Example to add a new rule
quarkus.kubernetes.ingress.rules.1.host=dev.svc.url
quarkus.kubernetes.ingress.rules.1.path=/dev
quarkus.kubernetes.ingress.rules.1.path-type=ImplementationSpecific
# by default, path type is Prefix

# Example to add a new rule that use another service binding
quarkus.kubernetes.ingress.rules.2.host=alt.svc.url
quarkus.kubernetes.ingress.rules.2.path=/ea
quarkus.kubernetes.ingress.rules.2.service-name=updated-service
quarkus.kubernetes.ingress.rules.2.service-port-name=tcpurl

This would generate the following Ingress resource:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  labels:
    app.kubernetes.io/name: kubernetes-with-ingress
    app.kubernetes.io/version: 0.1-SNAPSHOT
  name: kubernetes-with-ingress
spec:
  rules:
    - host: prod.svc.url
      http:
        paths:
          - backend:
              service:
                name: kubernetes-with-ingress
                port:
                  name: http
            path: /prod
            pathType: Prefix
    - host: dev.svc.url
      http:
        paths:
          - backend:
              service:
                name: kubernetes-with-ingress
                port:
                  name: http
            path: /dev
            pathType: ImplementationSpecific
    - host: alt.svc.url
      http:
        paths:
          - backend:
              service:
                name: updated-service
                port:
                  name: tcpurl
            path: /ea
            pathType: Prefix

Securing the Ingress resource

To secure the incoming connections, Kubernetes allows enabling TLS within the Ingress resource by specifying a Secret that contains a TLS private key and certificate. You can generate a secured Ingress resource by simply adding the "tls.secret-name" properties:

quarkus.kubernetes.ingress.expose=true
## Ingress TLS configuration:
quarkus.kubernetes.ingress.tls.my-secret.enabled=true

This configuration will generate the following secured Ingress resource:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  ...
  name: kubernetes-with-secure-ingress
spec:
  rules:
    ...
  tls:
    - secretName: my-secret

Now, Kubernetes will validate all the incoming connections using SSL with the certificates provided within the secret with name "my-secret".

More information about how to create the secret in here.

Using the Kubernetes client

Applications that are deployed to Kubernetes and need to access the API server will usually make use of the kubernetes-client extension:

pom.xml

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-kubernetes-client</artifactId>
</dependency>

build.gradle

implementation("io.quarkus:quarkus-kubernetes-client")

To access the API server from within a Kubernetes cluster, some RBAC related resources are required (e.g. a ServiceAccount, a RoleBinding). To ease the usage of the kubernetes-client extension, the kubernetes extension is going to generate a RoleBinding resource that binds a cluster role named "view" to the application ServiceAccount resource. It’s important to note that the cluster role "view" won’t be generated automatically, so it’s expected that you have this cluster role with name "view" already installed in your cluster.

On the other hand, you can fully customize the roles, subjects and role bindings to generate using the properties under quarkus.kubernetes.rbac.role-bindings, and if present, the kubernetes-client extension will use it and hence won’t generate any RoleBinding resource.

You can disable the RBAC resources generation using the property quarkus.kubernetes-client.generate-rbac=false.

Generating RBAC resources

In some scenarios, it’s necessary to generate additional RBAC resources that are used by Kubernetes to grant or limit access to other resources. For example, in our use case, we are building a Kubernetes operator that needs to read the list of the installed deployments. To do this, we would need to assign a service account to our operator and link this service account with a role that grants access to the Deployment resources. Let’s see how to do this using the quarkus.kubernetes.rbac properties:

# Generate the Role resource with name "my-role" (1)
quarkus.kubernetes.rbac.roles.my-role.policy-rules.0.api-groups=extensions,apps
quarkus.kubernetes.rbac.roles.my-role.policy-rules.0.resources=deployments
quarkus.kubernetes.rbac.roles.my-role.policy-rules.0.verbs=list

1	In this example, the role "my-role" will be generated with a policy rule to get the list of deployments.

By default, if one role is configured, a RoleBinding resource will be generated as well to link this role with the ServiceAccount resource.

Moreover, you can have more control over the RBAC resources to be generated:

# Generate Role resource with name "my-role" (1)
quarkus.kubernetes.rbac.roles.my-role.policy-rules.0.api-groups=extensions,apps
quarkus.kubernetes.rbac.roles.my-role.policy-rules.0.resources=deployments
quarkus.kubernetes.rbac.roles.my-role.policy-rules.0.verbs=get,watch,list

# Generate ServiceAccount resource with name "my-service-account" in namespace "my_namespace" (2)
quarkus.kubernetes.rbac.service-accounts.my-service-account.namespace=my_namespace

# Bind Role "my-role" with ServiceAccount "my-service-account" (3)
quarkus.kubernetes.rbac.role-bindings.my-role-binding.subjects.my-service-account.kind=ServiceAccount
quarkus.kubernetes.rbac.role-bindings.my-role-binding.subjects.my-service-account.namespace=my_namespace
quarkus.kubernetes.rbac.role-bindings.my-role-binding.role-name=my-role

1	In this example, the role "my-role" will be generated with the specified policy rules.
2	Also, the service account "my-service-account" will be generated.
3	And we can configure the generated RoleBinding resource by selecting the role to be used and the subject.

Finally, we can also generate the cluster wide role resource of "ClusterRole" kind and a "ClusterRoleBinding" resource as follows:

# Generate ClusterRole resource with name "my-cluster-role" (1)
quarkus.kubernetes.rbac.cluster-roles.my-cluster-role.policy-rules.0.api-groups=extensions,apps
quarkus.kubernetes.rbac.cluster-roles.my-cluster-role.policy-rules.0.resources=deployments
quarkus.kubernetes.rbac.cluster-roles.my-cluster-role.policy-rules.0.verbs=get,watch,list

# Bind the ClusterRole "my-cluster-role" with the application service account
quarkus.kubernetes.rbac.cluster-role-bindings.my-cluster-role-binding.subjects.manager.kind=Group
quarkus.kubernetes.rbac.cluster-role-bindings.my-cluster-role-binding.subjects.manager.api-group=rbac.authorization.k8s.io
quarkus.kubernetes.rbac.cluster-role-bindings.my-cluster-role-binding.role-name=my-cluster-role (2)

1	In this example, the cluster role "my-cluster-role" will be generated with the specified policy rules.
2	The name of the ClusterRole resource to use. Role resources are namespace-based and hence not allowed in ClusterRoleBinding resources.

Deploying to local Kubernetes

When deploying to local Kubernetes environments, users often perform minor changes to their manifests that simplify the development process. The most common changes are:

Setting imagePullPolicy to IfNotPresent
Using NodePort as Service type

Quarkus provides extensions that among others set these options by default. Such extensions are:

quarkus-minikube
quarkus-kind

If the list of extensions does not match the tool you are using (e.g. Docker Desktop, microk8s etc) then it is suggested to use the quarkus-minikube extension. as its defaults should be reasonable for most environments.

Deploying to Minikube

Minikube is quite popular when a Kubernetes cluster is needed for development purposes. To make the deployment to Minikube experience as frictionless as possible, Quarkus provides the quarkus-minikube extension. This extension can be added to a project like so:

pom.xml

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-minikube</artifactId>
</dependency>

build.gradle

implementation("io.quarkus:quarkus-minikube")

The purpose of this extension is to generate Kubernetes manifests (minikube.yaml and minikube.json) that are tailored to Minikube. This extension assumes a couple of things:

Users won’t be using an image registry and will instead make their container image accessible to the Kubernetes cluster by building it directly into Minikube’s Docker daemon. To use Minikube’s Docker daemon you must first execute:
```
eval $(minikube -p minikube docker-env)
```
Applications deployed to Kubernetes won’t be accessed via a Kubernetes Ingress, but rather as a NodePort Service. The advantage of doing this is that the URL of an application can be retrieved trivially by executing:
```
minikube service list
```

To control the nodePort that is used in this case, users can set quarkus.kubernetes.node-port. Note however that this configuration is entirely optional because Quarkus will automatically use a proper (and non-changing) value if none is set.

It is highly discouraged to use the manifests generated by the Minikube extension when deploying to production as these manifests are intended for development purposes only. When deploying to production, consider using the vanilla Kubernetes manifests (or the OpenShift ones when targeting OpenShift).

If the assumptions the Minikube extension makes don’t fit your workflow, nothing prevents you from using the regular Kubernetes extension to generate Kubernetes manifests and apply those to your Minikube cluster.

Deploying to Kind

Kind is another popular tool used as a Kubernetes cluster for development purposes. To make the deployment to Kind experience as frictionless as possible, Quarkus provides the quarkus-kind extension. This extension can be added to a project like so:

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-kind</artifactId>
</dependency>

The purpose of this extension is to generate Kubernetes manifests (kind.yaml and kind.json) that are tailored to Kind and also to automate the process of loading images to the cluster when performing container image builds. The tailor made manifests will be pretty similar (they share the same rules) with Minikube (see above).

Tuning the generated resources using application.properties

The Kubernetes extension allows tuning the generated manifest, using the application.properties file. Here are some examples:

Configuration options

The table below describe all the available configuration options.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	类型	默认
`quarkus.kubernetes.part-of` The name of the group this component belongs too Environment variable: `QUARKUS_KUBERNETES_PART_OF` Show more	string
`quarkus.kubernetes.name` The name of the application. This value will be used for naming Kubernetes resources like: - Deployment - Service and so on … Environment variable: `QUARKUS_KUBERNETES_NAME` Show more	string
`quarkus.kubernetes.version` The version of the application. Environment variable: `QUARKUS_KUBERNETES_VERSION` Show more	string
`quarkus.kubernetes.deployment-kind` The kind of the deployment resource to use. Supported values are 'StatefulSet', 'Job', 'CronJob' and 'Deployment' defaulting to the latter. Environment variable: `QUARKUS_KUBERNETES_DEPLOYMENT_KIND` Show more	`deployment`, `deployment-config`, `stateful-set`, `job`, `cron-job`, `knative-service`
`quarkus.kubernetes.namespace` The namespace the generated resources should belong to. If not value is set, then the 'namespace' field will not be added to the 'metadata' section of the generated manifests. This in turn means that when the manifests are applied to a cluster, the namespace will be resolved from the current Kubernetes context (see https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#context for more details). Environment variable: `QUARKUS_KUBERNETES_NAMESPACE` Show more	string
`quarkus.kubernetes.labels."label-name"` Custom labels to add to all resources Environment variable: `QUARKUS_KUBERNETES_LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.annotations."annotation-name"` Custom annotations to add to all resources Environment variable: `QUARKUS_KUBERNETES_ANNOTATIONS__ANNOTATION_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.add-build-timestamp` Whether to add the build timestamp to the Kubernetes annotations This is a very useful way to have manifests of successive builds of the same application differ - thus ensuring that Kubernetes will apply the updated resources Environment variable: `QUARKUS_KUBERNETES_ADD_BUILD_TIMESTAMP` Show more	boolean	`true`
`quarkus.kubernetes.working-dir` Working directory Environment variable: `QUARKUS_KUBERNETES_WORKING_DIR` Show more	string
`quarkus.kubernetes.command` The commands Environment variable: `QUARKUS_KUBERNETES_COMMAND` Show more	list of string
`quarkus.kubernetes.arguments` The arguments Environment variable: `QUARKUS_KUBERNETES_ARGUMENTS` Show more	list of string
`quarkus.kubernetes.service-account` The service account Environment variable: `QUARKUS_KUBERNETES_SERVICE_ACCOUNT` Show more	string
`quarkus.kubernetes.ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_KUBERNETES_PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.kubernetes.ports."ports".host-port` The host port. Environment variable: `QUARKUS_KUBERNETES_PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.kubernetes.ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_KUBERNETES_PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.kubernetes.ports."ports".protocol` The protocol. Environment variable: `QUARKUS_KUBERNETES_PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.kubernetes.ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_KUBERNETES_PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.kubernetes.ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_KUBERNETES_PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.kubernetes.replicas` The number of desired pods Environment variable: `QUARKUS_KUBERNETES_REPLICAS` Show more	int	`1`
`quarkus.kubernetes.strategy` Specifies the deployment strategy. Environment variable: `QUARKUS_KUBERNETES_STRATEGY` Show more	`none`, `recreate`, `rolling-update`	`none`
`quarkus.kubernetes.rolling-update.max-unavailable` Specifies the maximum number of Pods that can be unavailable during the update process. Environment variable: `QUARKUS_KUBERNETES_ROLLING_UPDATE_MAX_UNAVAILABLE` Show more	string	`25%`
`quarkus.kubernetes.rolling-update.max-surge` Specifies the maximum number of Pods that can be created over the desired number of Pods. Environment variable: `QUARKUS_KUBERNETES_ROLLING_UPDATE_MAX_SURGE` Show more	string	`25%`
`quarkus.kubernetes.service-type` The type of service that will be generated for the application Environment variable: `QUARKUS_KUBERNETES_SERVICE_TYPE` Show more	`cluster-ip`, `node-port`, `load-balancer`, `external-name`	`cluster-ip`
`quarkus.kubernetes.node-port` The nodePort to set when serviceType is set to node-port. Environment variable: `QUARKUS_KUBERNETES_NODE_PORT` Show more	int
`quarkus.kubernetes.image-pull-policy` Image pull policy Environment variable: `QUARKUS_KUBERNETES_IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.kubernetes.image-pull-secrets` The image pull secret Environment variable: `QUARKUS_KUBERNETES_IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.kubernetes.generate-image-pull-secret` Enable generation of image pull secret, when the container image username and password are provided. Environment variable: `QUARKUS_KUBERNETES_GENERATE_IMAGE_PULL_SECRET` Show more	boolean	`false`
`quarkus.kubernetes.liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.startup-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.startup-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.startup-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.startup-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.startup-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.startup-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.startup-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.startup-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.startup-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.startup-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.startup-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.startup-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.startup-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_STARTUP_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.prometheus.annotations` When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary. Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_ANNOTATIONS` Show more	boolean	`true`
`quarkus.kubernetes.prometheus.generate-service-monitor` When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary. Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_GENERATE_SERVICE_MONITOR` Show more	boolean	`true`
`quarkus.kubernetes.prometheus.prefix` Define the annotation prefix used for scrape values, this value will be used as the base for other annotation name defaults. Altering the base for generated annotations can make it easier to define re-labeling rules and avoid unexpected knock-on effects. The default value is `prometheus.io` See Prometheus example: https://github.com/prometheus/prometheus/blob/main/documentation/examples/prometheus-kubernetes.yml Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_PREFIX` Show more	string	`prometheus.io`
`quarkus.kubernetes.prometheus.scrape` Define the annotation used to indicate services that should be scraped. By default, `/scrape` will be appended to the defined prefix. Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_SCRAPE` Show more	string
`quarkus.kubernetes.prometheus.path` Define the annotation used to indicate the path to scrape. By default, `/path` will be appended to the defined prefix. Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_PATH` Show more	string
`quarkus.kubernetes.prometheus.port` Define the annotation used to indicate the port to scrape. By default, `/port` will be appended to the defined prefix. Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_PORT` Show more	string
`quarkus.kubernetes.prometheus.scheme` Define the annotation used to indicate the scheme to use for scraping By default, `/scheme` will be appended to the defined prefix. Environment variable: `QUARKUS_KUBERNETES_PROMETHEUS_SCHEME` Show more	string
`quarkus.kubernetes.mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_KUBERNETES_MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.kubernetes.mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_KUBERNETES_MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.kubernetes.mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_KUBERNETES_MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.kubernetes.mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_KUBERNETES_MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.kubernetes.secret-volumes."secret-volumes".secret-name` The name of the secret to mount. Environment variable: `QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__SECRET_NAME` Show more	string	required
`quarkus.kubernetes.secret-volumes."secret-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.kubernetes.secret-volumes."secret-volumes".items."items".path` The path where the file will be mounted. Environment variable: `QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__PATH` Show more	string	required
`quarkus.kubernetes.secret-volumes."secret-volumes".items."items".mode` It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used. Environment variable: `QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__MODE` Show more	int	`-1`
`quarkus.kubernetes.secret-volumes."secret-volumes".optional` Optional Environment variable: `QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.kubernetes.config-map-volumes."config-map-volumes".config-map-name` The name of the ConfigMap to mount. Environment variable: `QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__CONFIG_MAP_NAME` Show more	string	required
`quarkus.kubernetes.config-map-volumes."config-map-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.kubernetes.config-map-volumes."config-map-volumes".items."items".path` The path where the file will be mounted. Environment variable: `QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__PATH` Show more	string	required
`quarkus.kubernetes.config-map-volumes."config-map-volumes".items."items".mode` It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used. Environment variable: `QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__MODE` Show more	int	`-1`
`quarkus.kubernetes.config-map-volumes."config-map-volumes".optional` Optional Environment variable: `QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.kubernetes.empty-dir-volumes` EmptyDir volumes Environment variable: `QUARKUS_KUBERNETES_EMPTY_DIR_VOLUMES` Show more	list of string
`quarkus.kubernetes.git-repo-volumes."git-repo-volumes".repository` Git repository URL. Environment variable: `QUARKUS_KUBERNETES_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REPOSITORY` Show more	string	required
`quarkus.kubernetes.git-repo-volumes."git-repo-volumes".directory` The directory of the repository to mount. Environment variable: `QUARKUS_KUBERNETES_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__DIRECTORY` Show more	string
`quarkus.kubernetes.git-repo-volumes."git-repo-volumes".revision` The commit hash to use. Environment variable: `QUARKUS_KUBERNETES_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REVISION` Show more	string
`quarkus.kubernetes.pvc-volumes."pvc-volumes".claim-name` The name of the claim to mount. Environment variable: `QUARKUS_KUBERNETES_PVC_VOLUMES__PVC_VOLUMES__CLAIM_NAME` Show more	string	required
`quarkus.kubernetes.pvc-volumes."pvc-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_KUBERNETES_PVC_VOLUMES__PVC_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.kubernetes.pvc-volumes."pvc-volumes".optional` Optional Environment variable: `QUARKUS_KUBERNETES_PVC_VOLUMES__PVC_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".volume-id` The name of the disk to mount. Environment variable: `QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__VOLUME_ID` Show more	string	required
`quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".partition` The partition. Environment variable: `QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__PARTITION` Show more	int
`quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".fs-type` Filesystem type. Environment variable: `QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__FS_TYPE` Show more	string	`ext4`
`quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.kubernetes.azure-file-volumes."azure-file-volumes".share-name` The share name. Environment variable: `QUARKUS_KUBERNETES_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SHARE_NAME` Show more	string	required
`quarkus.kubernetes.azure-file-volumes."azure-file-volumes".secret-name` The secret name. Environment variable: `QUARKUS_KUBERNETES_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SECRET_NAME` Show more	string	required
`quarkus.kubernetes.azure-file-volumes."azure-file-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_KUBERNETES_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".disk-name` The name of the disk to mount. Environment variable: `QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_NAME` Show more	string	required
`quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".disk-uri` The URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed Environment variable: `QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_URI` Show more	string	required
`quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".kind` Kind of disk. Environment variable: `QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__KIND` Show more	`managed`, `shared`	`managed`
`quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".caching-mode` Disk caching mode. Environment variable: `QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__CACHING_MODE` Show more	`read-write`, `read-only`, `none`	`read-write`
`quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".fs-type` File system type. Environment variable: `QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__FS_TYPE` Show more	string	`ext4`
`quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.kubernetes.init-containers."init-containers".image` The container image. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE` Show more	string
`quarkus.kubernetes.init-containers."init-containers".working-dir` Working directory. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__WORKING_DIR` Show more	string
`quarkus.kubernetes.init-containers."init-containers".command` The commands Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__COMMAND` Show more	list of string
`quarkus.kubernetes.init-containers."init-containers".arguments` The arguments Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ARGUMENTS` Show more	list of string
`quarkus.kubernetes.init-containers."init-containers".service-account` The service account. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__SERVICE_ACCOUNT` Show more	string
`quarkus.kubernetes.init-containers."init-containers".host` The host under which the application is going to be exposed. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__HOST` Show more	string
`quarkus.kubernetes.init-containers."init-containers".ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.kubernetes.init-containers."init-containers".ports."ports".host-port` The host port. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.kubernetes.init-containers."init-containers".ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.kubernetes.init-containers."init-containers".ports."ports".protocol` The protocol. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.kubernetes.init-containers."init-containers".ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.kubernetes.init-containers."init-containers".ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.kubernetes.init-containers."init-containers".image-pull-policy` Image pull policy. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.kubernetes.init-containers."init-containers".image-pull-secrets` The image pull secret Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.init-containers."init-containers".liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.init-containers."init-containers".readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.init-containers."init-containers".mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.kubernetes.init-containers."init-containers".mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.kubernetes.init-containers."init-containers".mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.kubernetes.init-containers."init-containers".mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.kubernetes.init-containers."init-containers".resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_CPU` Show more	string
`quarkus.kubernetes.init-containers."init-containers".resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.kubernetes.init-containers."init-containers".resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.kubernetes.init-containers."init-containers".resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.kubernetes.init-containers."init-containers".env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_SECRETS` Show more	list of string
`quarkus.kubernetes.init-containers."init-containers".env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_CONFIGMAPS` Show more	list of string
`quarkus.kubernetes.init-containers."init-containers".env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.init-containers."init-containers".env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.kubernetes.init-containers."init-containers".env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.kubernetes.init-containers."init-containers".env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.kubernetes.init-containers."init-containers".env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.kubernetes.init-containers."init-containers".env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.kubernetes.init-containers."init-containers".env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.kubernetes.sidecars."sidecars".image` The container image. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__IMAGE` Show more	string
`quarkus.kubernetes.sidecars."sidecars".working-dir` Working directory. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__WORKING_DIR` Show more	string
`quarkus.kubernetes.sidecars."sidecars".command` The commands Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__COMMAND` Show more	list of string
`quarkus.kubernetes.sidecars."sidecars".arguments` The arguments Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ARGUMENTS` Show more	list of string
`quarkus.kubernetes.sidecars."sidecars".service-account` The service account. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__SERVICE_ACCOUNT` Show more	string
`quarkus.kubernetes.sidecars."sidecars".host` The host under which the application is going to be exposed. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__HOST` Show more	string
`quarkus.kubernetes.sidecars."sidecars".ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.kubernetes.sidecars."sidecars".ports."ports".host-port` The host port. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.kubernetes.sidecars."sidecars".ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.kubernetes.sidecars."sidecars".ports."ports".protocol` The protocol. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.kubernetes.sidecars."sidecars".ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.kubernetes.sidecars."sidecars".ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.kubernetes.sidecars."sidecars".image-pull-policy` Image pull policy. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.kubernetes.sidecars."sidecars".image-pull-secrets` The image pull secret Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.sidecars."sidecars".liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.kubernetes.sidecars."sidecars".readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.kubernetes.sidecars."sidecars".mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.kubernetes.sidecars."sidecars".mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.kubernetes.sidecars."sidecars".mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.kubernetes.sidecars."sidecars".mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.kubernetes.sidecars."sidecars".resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_LIMITS_CPU` Show more	string
`quarkus.kubernetes.sidecars."sidecars".resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.kubernetes.sidecars."sidecars".resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.kubernetes.sidecars."sidecars".resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.kubernetes.sidecars."sidecars".env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_SECRETS` Show more	list of string
`quarkus.kubernetes.sidecars."sidecars".env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_CONFIGMAPS` Show more	list of string
`quarkus.kubernetes.sidecars."sidecars".env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.sidecars."sidecars".env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.kubernetes.sidecars."sidecars".env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.kubernetes.sidecars."sidecars".env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.kubernetes.sidecars."sidecars".env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.kubernetes.sidecars."sidecars".env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.kubernetes.sidecars."sidecars".env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.kubernetes.deployment-target` The target deployment platform. Defaults to kubernetes. Can be kubernetes, openshift, knative, minikube etc., or any combination of the above as comma separated list. Environment variable: `QUARKUS_KUBERNETES_DEPLOYMENT_TARGET` Show more	list of string
`quarkus.kubernetes.hostaliases."host-aliases".ip` The ip address Environment variable: `QUARKUS_KUBERNETES_HOSTALIASES__HOST_ALIASES__IP` Show more	string
`quarkus.kubernetes.hostaliases."host-aliases".hostnames` The hostnames to resolve to the ip Environment variable: `QUARKUS_KUBERNETES_HOSTALIASES__HOST_ALIASES__HOSTNAMES` Show more	list of string
`quarkus.kubernetes.resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_KUBERNETES_RESOURCES_LIMITS_CPU` Show more	string
`quarkus.kubernetes.resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_KUBERNETES_RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.kubernetes.resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_KUBERNETES_RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.kubernetes.resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_KUBERNETES_RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.kubernetes.rbac.roles."roles".name` The name of the role. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__NAME` Show more	string
`quarkus.kubernetes.rbac.roles."roles".namespace` The namespace of the role. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__NAMESPACE` Show more	string
`quarkus.kubernetes.rbac.roles."roles".labels."label-name"` Labels to add into the Role resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".api-groups` API groups of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS` Show more	list of string
`quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".non-resource-urls` Non resource URLs of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS` Show more	list of string
`quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".resource-names` Resource names of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES` Show more	list of string
`quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".resources` Resources of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCES` Show more	list of string
`quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".verbs` Verbs of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__VERBS` Show more	list of string
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".name` The name of the cluster role. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__NAME` Show more	string
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".labels."label-name"` Labels to add into the ClusterRole resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".api-groups` API groups of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS` Show more	list of string
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".non-resource-urls` Non resource URLs of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS` Show more	list of string
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resource-names` Resource names of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES` Show more	list of string
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resources` Resources of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCES` Show more	list of string
`quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".verbs` Verbs of the policy rule. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__VERBS` Show more	list of string
`quarkus.kubernetes.rbac.service-accounts."service-accounts".name` The name of the service account. Environment variable: `QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAME` Show more	string
`quarkus.kubernetes.rbac.service-accounts."service-accounts".namespace` The namespace of the service account. Environment variable: `QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAMESPACE` Show more	string
`quarkus.kubernetes.rbac.service-accounts."service-accounts".labels."label-name"` Labels of the service account. Environment variable: `QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.rbac.service-accounts."service-accounts".use-as-default` If true, this service account will be used in the generated Deployment resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__USE_AS_DEFAULT` Show more	boolean
`quarkus.kubernetes.rbac.role-bindings."role-bindings".name` Name of the RoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__NAME` Show more	string
`quarkus.kubernetes.rbac.role-bindings."role-bindings".labels."label-name"` Labels to add into the RoleBinding resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.rbac.role-bindings."role-bindings".role-name` The name of the Role resource to use by the RoleRef element in the generated Role Binding resource. By default, it’s "view" role name. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__ROLE_NAME` Show more	string
`quarkus.kubernetes.rbac.role-bindings."role-bindings".cluster-wide` If the Role sets in the `role-name` property is cluster wide or not. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__CLUSTER_WIDE` Show more	boolean
`quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".name` The "name" resource to use by the Subject element in the generated Role Binding resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME` Show more	string
`quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".kind` The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND` Show more	string	`ServiceAccount`
`quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".api-group` The "apiGroup" resource that matches with the "kind" property. By default, it’s empty. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP` Show more	string
`quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".namespace` The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources. Environment variable: `QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE` Show more	string
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".name` Name of the ClusterRoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__NAME` Show more	string
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".labels."label-name"` Labels to add into the RoleBinding resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".role-name` The name of the ClusterRole resource to use by the RoleRef element in the generated ClusterRoleBinding resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__ROLE_NAME` Show more	string	required
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".name` The "name" resource to use by the Subject element in the generated Role Binding resource. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME` Show more	string
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".kind` The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND` Show more	string	`ServiceAccount`
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".api-group` The "apiGroup" resource that matches with the "kind" property. By default, it’s empty. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP` Show more	string
`quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".namespace` The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources. Environment variable: `QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE` Show more	string
`quarkus.kubernetes.ingress.expose` If true, the service will be exposed Environment variable: `QUARKUS_KUBERNETES_INGRESS_EXPOSE` Show more	boolean	`false`
`quarkus.kubernetes.ingress.host` The host under which the application is going to be exposed Environment variable: `QUARKUS_KUBERNETES_INGRESS_HOST` Show more	string
`quarkus.kubernetes.ingress.target-port` The default target named port. If not provided, it will be deducted from the Service resource ports. Options are: "http" and "https". Environment variable: `QUARKUS_KUBERNETES_INGRESS_TARGET_PORT` Show more	string	`http`
`quarkus.kubernetes.ingress.ingress-class-name` The class of the Ingress. If the ingressClassName is omitted, a default Ingress class is used. Environment variable: `QUARKUS_KUBERNETES_INGRESS_INGRESS_CLASS_NAME` Show more	string
`quarkus.kubernetes.ingress.annotations."annotation-name"` Custom annotations to add to exposition (route or ingress) resources Environment variable: `QUARKUS_KUBERNETES_INGRESS_ANNOTATIONS__ANNOTATION_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.ingress.tls."tls".enabled` If true, it will use the TLS configuration in the generated Ingress resource. Environment variable: `QUARKUS_KUBERNETES_INGRESS_TLS__TLS__ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.ingress.tls."tls".hosts` The list of hosts to be included in the TLS certificate. By default, it will use the application host. Environment variable: `QUARKUS_KUBERNETES_INGRESS_TLS__TLS__HOSTS` Show more	list of string
`quarkus.kubernetes.ingress.rules."rules".host` The host under which the rule is going to be used. Environment variable: `QUARKUS_KUBERNETES_INGRESS_RULES__RULES__HOST` Show more	string	required
`quarkus.kubernetes.ingress.rules."rules".path` The path under which the rule is going to be used. Default is "/". Environment variable: `QUARKUS_KUBERNETES_INGRESS_RULES__RULES__PATH` Show more	string	`/`
`quarkus.kubernetes.ingress.rules."rules".path-type` The path type strategy to use by the Ingress rule. Default is "Prefix". Environment variable: `QUARKUS_KUBERNETES_INGRESS_RULES__RULES__PATH_TYPE` Show more	string	`Prefix`
`quarkus.kubernetes.ingress.rules."rules".service-name` The service name to be used by this Ingress rule. Default is the generated service name of the application. Environment variable: `QUARKUS_KUBERNETES_INGRESS_RULES__RULES__SERVICE_NAME` Show more	string
`quarkus.kubernetes.ingress.rules."rules".service-port-name` The service port name to be used by this Ingress rule. Default is the port name of the generated service of the application. Environment variable: `QUARKUS_KUBERNETES_INGRESS_RULES__RULES__SERVICE_PORT_NAME` Show more	string
`quarkus.kubernetes.ingress.rules."rules".service-port-number` The service port number to be used by this Ingress rule. This is only used when the servicePortName is not set. Environment variable: `QUARKUS_KUBERNETES_INGRESS_RULES__RULES__SERVICE_PORT_NUMBER` Show more	int
`quarkus.kubernetes.job.parallelism` Specifies the maximum desired number of pods the job should run at any given time. Environment variable: `QUARKUS_KUBERNETES_JOB_PARALLELISM` Show more	int
`quarkus.kubernetes.job.completions` Specifies the desired number of successfully finished pods the job should be run with. Environment variable: `QUARKUS_KUBERNETES_JOB_COMPLETIONS` Show more	int
`quarkus.kubernetes.job.completion-mode` CompletionMode specifies how Pod completions are tracked. Environment variable: `QUARKUS_KUBERNETES_JOB_COMPLETION_MODE` Show more	`non-indexed`, `indexed`	`non-indexed`
`quarkus.kubernetes.job.backoff-limit` Specifies the number of retries before marking this job failed. Environment variable: `QUARKUS_KUBERNETES_JOB_BACKOFF_LIMIT` Show more	int
`quarkus.kubernetes.job.active-deadline-seconds` Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. Environment variable: `QUARKUS_KUBERNETES_JOB_ACTIVE_DEADLINE_SECONDS` Show more	long
`quarkus.kubernetes.job.ttl-seconds-after-finished` Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. Environment variable: `QUARKUS_KUBERNETES_JOB_TTL_SECONDS_AFTER_FINISHED` Show more	int
`quarkus.kubernetes.job.suspend` Suspend specifies whether the Job controller should create Pods or not. Environment variable: `QUARKUS_KUBERNETES_JOB_SUSPEND` Show more	boolean	`false`
`quarkus.kubernetes.job.restart-policy` Restart policy when the job container fails. Environment variable: `QUARKUS_KUBERNETES_JOB_RESTART_POLICY` Show more	`on-failure`, `never`	`on-failure`
`quarkus.kubernetes.cron-job.schedule` The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_SCHEDULE` Show more	string
`quarkus.kubernetes.cron-job.concurrency-policy` ConcurrencyPolicy describes how the job will be handled. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_CONCURRENCY_POLICY` Show more	`allow`, `forbid`, `replace`	`allow`
`quarkus.kubernetes.cron-job.starting-deadline-seconds` Deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_STARTING_DEADLINE_SECONDS` Show more	long
`quarkus.kubernetes.cron-job.failed-jobs-history-limit` The number of failed finished jobs to retain. The default value is 1. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_FAILED_JOBS_HISTORY_LIMIT` Show more	int
`quarkus.kubernetes.cron-job.successful-jobs-history-limit` The number of successful finished jobs to retain. The default value is 3. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_SUCCESSFUL_JOBS_HISTORY_LIMIT` Show more	int
`quarkus.kubernetes.cron-job.parallelism` Specifies the maximum desired number of pods the job should run at any given time. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_PARALLELISM` Show more	int
`quarkus.kubernetes.cron-job.completions` Specifies the desired number of successfully finished pods the job should be run with. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_COMPLETIONS` Show more	int
`quarkus.kubernetes.cron-job.completion-mode` CompletionMode specifies how Pod completions are tracked. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_COMPLETION_MODE` Show more	`non-indexed`, `indexed`	`non-indexed`
`quarkus.kubernetes.cron-job.backoff-limit` Specifies the number of retries before marking this job failed. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_BACKOFF_LIMIT` Show more	int
`quarkus.kubernetes.cron-job.active-deadline-seconds` Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_ACTIVE_DEADLINE_SECONDS` Show more	long
`quarkus.kubernetes.cron-job.ttl-seconds-after-finished` Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_TTL_SECONDS_AFTER_FINISHED` Show more	int
`quarkus.kubernetes.cron-job.suspend` Suspend specifies whether the Job controller should create Pods or not. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_SUSPEND` Show more	boolean	`false`
`quarkus.kubernetes.cron-job.restart-policy` Restart policy when the job container fails. Environment variable: `QUARKUS_KUBERNETES_CRON_JOB_RESTART_POLICY` Show more	`on-failure`, `never`	`on-failure`
`quarkus.kubernetes.add-version-to-label-selectors` If true, the 'app.kubernetes.io/version' label will be part of the selectors of Service and Deployment Environment variable: `QUARKUS_KUBERNETES_ADD_VERSION_TO_LABEL_SELECTORS` Show more	boolean	`true`
`quarkus.kubernetes.add-name-to-label-selectors` If true, the 'app.kubernetes.io/name' label will be part of the selectors of Service and Deployment Environment variable: `QUARKUS_KUBERNETES_ADD_NAME_TO_LABEL_SELECTORS` Show more	boolean	`true`
`quarkus.kubernetes.deploy` If set to true, Quarkus will attempt to deploy the application to the target Kubernetes cluster Environment variable: `QUARKUS_KUBERNETES_DEPLOY` Show more	boolean	`false`
`quarkus.kubernetes.deploy-strategy` If deploy is enabled, it will follow this strategy to update the resources to the target Kubernetes cluster. Environment variable: `QUARKUS_KUBERNETES_DEPLOY_STRATEGY` Show more	`create-or-update`, `create`, `replace`, `server-side-apply`	`create-or-update`
`quarkus.kubernetes.app-secret` If set, the secret will mounted to the application container and its contents will be used for application configuration. Environment variable: `QUARKUS_KUBERNETES_APP_SECRET` Show more	string
`quarkus.kubernetes.app-config-map` If set, the config map will be mounted to the application container and its contents will be used for application configuration. Environment variable: `QUARKUS_KUBERNETES_APP_CONFIG_MAP` Show more	string
`quarkus.kubernetes.security-context.se-linux-options.level` The SELinux level label that applies to the container. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_LEVEL` Show more	string
`quarkus.kubernetes.security-context.se-linux-options.role` The SELinux role label that applies to the container. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_ROLE` Show more	string
`quarkus.kubernetes.security-context.se-linux-options.type` The SELinux type label that applies to the container. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_TYPE` Show more	string
`quarkus.kubernetes.security-context.se-linux-options.user` The SELinux user label that applies to the container. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_USER` Show more	string
`quarkus.kubernetes.security-context.windows-options.gmsa-credential-spec-name` The name of the GMSA credential spec to use. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC_NAME` Show more	string
`quarkus.kubernetes.security-context.windows-options.gmsa-credential-spec` GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC` Show more	string
`quarkus.kubernetes.security-context.windows-options.run-as-user-name` The UserName in Windows to run the entrypoint of the container process. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_RUN_AS_USER_NAME` Show more	string
`quarkus.kubernetes.security-context.windows-options.host-process` HostProcess determines if a container should be run as a 'Host Process' container. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_HOST_PROCESS` Show more	boolean
`quarkus.kubernetes.security-context.run-as-user` The UID to run the entrypoint of the container process. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_RUN_AS_USER` Show more	long
`quarkus.kubernetes.security-context.run-as-group` The GID to run the entrypoint of the container process. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_RUN_AS_GROUP` Show more	long
`quarkus.kubernetes.security-context.run-as-non-root` Indicates that the container must run as a non-root user. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_RUN_AS_NON_ROOT` Show more	boolean
`quarkus.kubernetes.security-context.supplemental-groups` A list of groups applied to the first process run in each container, in addition to the container’s primary GID. If unspecified, no groups will be added to any container. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_SUPPLEMENTAL_GROUPS` Show more	list of long
`quarkus.kubernetes.security-context.fs-group` A special supplemental group that applies to all containers in a pod. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_FS_GROUP` Show more	long
`quarkus.kubernetes.security-context.sysctls."sysctl-name"` Sysctls hold a list of namespaced sysctls used for the pod. Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_SYSCTLS__SYSCTL_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.security-context.fs-group-change-policy` It holds policies that will be used for applying fsGroup to a volume when volume is mounted. Values: OnRootMismatch, Always Environment variable: `QUARKUS_KUBERNETES_SECURITY_CONTEXT_FS_GROUP_CHANGE_POLICY` Show more	`on-root-mismatch`It indicates that volume’s ownership and permissions will be changed only when permission and ownership of root directory does not match with expected permissions on the volume., `always`It indicates that volume’s ownership and permissions should always be changed whenever volume is mounted inside a Pod. This the default behavior.
`quarkus.kubernetes.container-name` If set, it will change the name of the container according to the configuration Environment variable: `QUARKUS_KUBERNETES_CONTAINER_NAME` Show more	string
`quarkus.kubernetes.remote-debug.enabled` If true, the debug mode in pods will be enabled. Environment variable: `QUARKUS_KUBERNETES_REMOTE_DEBUG_ENABLED` Show more	boolean	`false`
`quarkus.kubernetes.remote-debug.transport` The transport to use. Environment variable: `QUARKUS_KUBERNETES_REMOTE_DEBUG_TRANSPORT` Show more	string	`dt_socket`
`quarkus.kubernetes.remote-debug.suspend` If enabled, it means the JVM will wait for the debugger to attach before executing the main class. If false, the JVM will immediately execute the main class, while listening for the debugger connection. Environment variable: `QUARKUS_KUBERNETES_REMOTE_DEBUG_SUSPEND` Show more	string	`n`
`quarkus.kubernetes.remote-debug.address-port` It specifies the address at which the debug socket will listen. Environment variable: `QUARKUS_KUBERNETES_REMOTE_DEBUG_ADDRESS_PORT` Show more	int	`5005`
`quarkus.kubernetes.init-tasks."init-tasks".enabled` If true, the init task will be generated. Otherwise, the init task resource generation will be skipped. Environment variable: `QUARKUS_KUBERNETES_INIT_TASKS__INIT_TASKS__ENABLED` Show more	boolean	`true`
`quarkus.kubernetes.init-tasks."init-tasks".wait-for-container.image` The init task image to use by the init-container. Environment variable: `QUARKUS_KUBERNETES_INIT_TASKS__INIT_TASKS__WAIT_FOR_CONTAINER_IMAGE` Show more	string	`groundnuty/k8s-wait-for:no-root-v1.7`
`quarkus.kubernetes.init-task-defaults.enabled` If true, the init task will be generated. Otherwise, the init task resource generation will be skipped. Environment variable: `QUARKUS_KUBERNETES_INIT_TASK_DEFAULTS_ENABLED` Show more	boolean	`true`
`quarkus.kubernetes.init-task-defaults.wait-for-container.image` The init task image to use by the init-container. Environment variable: `QUARKUS_KUBERNETES_INIT_TASK_DEFAULTS_WAIT_FOR_CONTAINER_IMAGE` Show more	string	`groundnuty/k8s-wait-for:no-root-v1.7`
`quarkus.kubernetes.idempotent` Switch used to control whether non-idempotent fields are included in generated kubernetes resources to improve git-ops compatibility Environment variable: `QUARKUS_KUBERNETES_IDEMPOTENT` Show more	boolean	`false`
`quarkus.kubernetes.vcs-uri.enabled` Whether the vcs-uri annotation should be added to the generated configuration. Environment variable: `QUARKUS_KUBERNETES_VCS_URI_ENABLED` Show more	boolean	`true`
`quarkus.kubernetes.vcs-uri.override` Optional override of the vcs-uri annotation. Environment variable: `QUARKUS_KUBERNETES_VCS_URI_OVERRIDE` Show more	string
`quarkus.kubernetes.output-directory` Optionally set directory generated kubernetes resources will be written to. Default is `target/kubernetes`. Environment variable: `QUARKUS_KUBERNETES_OUTPUT_DIRECTORY` Show more	string
`quarkus.kubernetes.env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_KUBERNETES_ENV_SECRETS` Show more	list of string
`quarkus.kubernetes.env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_KUBERNETES_ENV_CONFIGMAPS` Show more	list of string
`quarkus.kubernetes.env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_KUBERNETES_ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.kubernetes.env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_KUBERNETES_ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.kubernetes.env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_KUBERNETES_ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.kubernetes.env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_KUBERNETES_ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.kubernetes.env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_KUBERNETES_ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.kubernetes.env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KUBERNETES_ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.kubernetes.env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KUBERNETES_ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string

Configuration property

类型

默认

quarkus.kubernetes.part-of

The name of the group this component belongs too

Environment variable: QUARKUS_KUBERNETES_PART_OF

string

quarkus.kubernetes.name

The name of the application. This value will be used for naming Kubernetes resources like: - Deployment - Service and so on …

Environment variable: QUARKUS_KUBERNETES_NAME

string

quarkus.kubernetes.version

The version of the application.

Environment variable: QUARKUS_KUBERNETES_VERSION

string

quarkus.kubernetes.deployment-kind

The kind of the deployment resource to use. Supported values are 'StatefulSet', 'Job', 'CronJob' and 'Deployment' defaulting to the latter.

Environment variable: QUARKUS_KUBERNETES_DEPLOYMENT_KIND

deployment, deployment-config, stateful-set, job, cron-job, knative-service

quarkus.kubernetes.namespace

The namespace the generated resources should belong to. If not value is set, then the 'namespace' field will not be added to the 'metadata' section of the generated manifests. This in turn means that when the manifests are applied to a cluster, the namespace will be resolved from the current Kubernetes context (see https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#context for more details).

Environment variable: QUARKUS_KUBERNETES_NAMESPACE

string

quarkus.kubernetes.labels."label-name"

Custom labels to add to all resources

Environment variable: QUARKUS_KUBERNETES_LABELS__LABEL_NAME_

Map<String,String>

quarkus.kubernetes.annotations."annotation-name"

Custom annotations to add to all resources

Environment variable: QUARKUS_KUBERNETES_ANNOTATIONS__ANNOTATION_NAME_

Map<String,String>

quarkus.kubernetes.add-build-timestamp

Whether to add the build timestamp to the Kubernetes annotations This is a very useful way to have manifests of successive builds of the same application differ - thus ensuring that Kubernetes will apply the updated resources

Environment variable: QUARKUS_KUBERNETES_ADD_BUILD_TIMESTAMP

boolean

true

quarkus.kubernetes.working-dir

Working directory

Environment variable: QUARKUS_KUBERNETES_WORKING_DIR

string

quarkus.kubernetes.command

The commands

Environment variable: QUARKUS_KUBERNETES_COMMAND

list of string

quarkus.kubernetes.arguments

The arguments

Environment variable: QUARKUS_KUBERNETES_ARGUMENTS

list of string

quarkus.kubernetes.service-account

The service account

Environment variable: QUARKUS_KUBERNETES_SERVICE_ACCOUNT

string

quarkus.kubernetes.ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_KUBERNETES_PORTS__PORTS__CONTAINER_PORT

int

quarkus.kubernetes.ports."ports".host-port

The host port.

Environment variable: QUARKUS_KUBERNETES_PORTS__PORTS__HOST_PORT

int

quarkus.kubernetes.ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_KUBERNETES_PORTS__PORTS__PATH

string

/

quarkus.kubernetes.ports."ports".protocol

The protocol.

Environment variable: QUARKUS_KUBERNETES_PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.kubernetes.ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_KUBERNETES_PORTS__PORTS__NODE_PORT

int

quarkus.kubernetes.ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_KUBERNETES_PORTS__PORTS__TLS

boolean

false

quarkus.kubernetes.replicas

The number of desired pods

Environment variable: QUARKUS_KUBERNETES_REPLICAS

int

1

quarkus.kubernetes.strategy

Specifies the deployment strategy.

Environment variable: QUARKUS_KUBERNETES_STRATEGY

none, recreate, rolling-update

none

quarkus.kubernetes.rolling-update.max-unavailable

Specifies the maximum number of Pods that can be unavailable during the update process.

Environment variable: QUARKUS_KUBERNETES_ROLLING_UPDATE_MAX_UNAVAILABLE

string

25%

quarkus.kubernetes.rolling-update.max-surge

Specifies the maximum number of Pods that can be created over the desired number of Pods.

Environment variable: QUARKUS_KUBERNETES_ROLLING_UPDATE_MAX_SURGE

string

25%

quarkus.kubernetes.service-type

The type of service that will be generated for the application

Environment variable: QUARKUS_KUBERNETES_SERVICE_TYPE

cluster-ip, node-port, load-balancer, external-name

cluster-ip

quarkus.kubernetes.node-port

The nodePort to set when serviceType is set to node-port.

Environment variable: QUARKUS_KUBERNETES_NODE_PORT

int

quarkus.kubernetes.image-pull-policy

Image pull policy

Environment variable: QUARKUS_KUBERNETES_IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.kubernetes.image-pull-secrets

The image pull secret

Environment variable: QUARKUS_KUBERNETES_IMAGE_PULL_SECRETS

list of string

quarkus.kubernetes.generate-image-pull-secret

Enable generation of image pull secret, when the container image username and password are provided.

Environment variable: QUARKUS_KUBERNETES_GENERATE_IMAGE_PULL_SECRET

boolean

false

quarkus.kubernetes.liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.liveness-probe.http-action-path

The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_EXEC_ACTION

string

quarkus.kubernetes.liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_GRPC_ACTION

string

quarkus.kubernetes.liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.readiness-probe.http-action-path

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_EXEC_ACTION

string

quarkus.kubernetes.readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_GRPC_ACTION

string

quarkus.kubernetes.readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.startup-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.startup-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.startup-probe.http-action-path

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.startup-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.startup-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_EXEC_ACTION

string

quarkus.kubernetes.startup-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.startup-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_GRPC_ACTION

string

quarkus.kubernetes.startup-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.startup-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.startup-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.startup-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.startup-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.startup-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_STARTUP_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.prometheus.annotations

When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary.

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_ANNOTATIONS

boolean

true

quarkus.kubernetes.prometheus.generate-service-monitor

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_GENERATE_SERVICE_MONITOR

boolean

true

quarkus.kubernetes.prometheus.prefix

Define the annotation prefix used for scrape values, this value will be used as the base for other annotation name defaults. Altering the base for generated annotations can make it easier to define re-labeling rules and avoid unexpected knock-on effects. The default value is prometheus.io See Prometheus example: https://github.com/prometheus/prometheus/blob/main/documentation/examples/prometheus-kubernetes.yml

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_PREFIX

string

prometheus.io

quarkus.kubernetes.prometheus.scrape

Define the annotation used to indicate services that should be scraped. By default, /scrape will be appended to the defined prefix.

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_SCRAPE

string

quarkus.kubernetes.prometheus.path

Define the annotation used to indicate the path to scrape. By default, /path will be appended to the defined prefix.

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_PATH

string

quarkus.kubernetes.prometheus.port

Define the annotation used to indicate the port to scrape. By default, /port will be appended to the defined prefix.

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_PORT

string

quarkus.kubernetes.prometheus.scheme

Define the annotation used to indicate the scheme to use for scraping By default, /scheme will be appended to the defined prefix.

Environment variable: QUARKUS_KUBERNETES_PROMETHEUS_SCHEME

string

quarkus.kubernetes.mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_KUBERNETES_MOUNTS__MOUNTS__NAME

string

quarkus.kubernetes.mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_KUBERNETES_MOUNTS__MOUNTS__PATH

string

quarkus.kubernetes.mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_KUBERNETES_MOUNTS__MOUNTS__SUB_PATH

string

quarkus.kubernetes.mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_KUBERNETES_MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.kubernetes.secret-volumes."secret-volumes".secret-name

The name of the secret to mount.

Environment variable: QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__SECRET_NAME

string

required

quarkus.kubernetes.secret-volumes."secret-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__DEFAULT_MODE

string

0600

quarkus.kubernetes.secret-volumes."secret-volumes".items."items".path

The path where the file will be mounted.

Environment variable: QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__PATH

string

required

quarkus.kubernetes.secret-volumes."secret-volumes".items."items".mode

It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used.

Environment variable: QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__MODE

int

-1

quarkus.kubernetes.secret-volumes."secret-volumes".optional

Optional

Environment variable: QUARKUS_KUBERNETES_SECRET_VOLUMES__SECRET_VOLUMES__OPTIONAL

boolean

false

quarkus.kubernetes.config-map-volumes."config-map-volumes".config-map-name

The name of the ConfigMap to mount.

Environment variable: QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__CONFIG_MAP_NAME

string

required

quarkus.kubernetes.config-map-volumes."config-map-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__DEFAULT_MODE

string

0600

quarkus.kubernetes.config-map-volumes."config-map-volumes".items."items".path

The path where the file will be mounted.

Environment variable: QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__PATH

string

required

quarkus.kubernetes.config-map-volumes."config-map-volumes".items."items".mode

It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used.

Environment variable: QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__MODE

int

-1

quarkus.kubernetes.config-map-volumes."config-map-volumes".optional

Optional

Environment variable: QUARKUS_KUBERNETES_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__OPTIONAL

boolean

false

quarkus.kubernetes.empty-dir-volumes

EmptyDir volumes

Environment variable: QUARKUS_KUBERNETES_EMPTY_DIR_VOLUMES

list of string

quarkus.kubernetes.git-repo-volumes."git-repo-volumes".repository

Git repository URL.

Environment variable: QUARKUS_KUBERNETES_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REPOSITORY

string

required

quarkus.kubernetes.git-repo-volumes."git-repo-volumes".directory

The directory of the repository to mount.

Environment variable: QUARKUS_KUBERNETES_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__DIRECTORY

string

quarkus.kubernetes.git-repo-volumes."git-repo-volumes".revision

The commit hash to use.

Environment variable: QUARKUS_KUBERNETES_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REVISION

string

quarkus.kubernetes.pvc-volumes."pvc-volumes".claim-name

The name of the claim to mount.

Environment variable: QUARKUS_KUBERNETES_PVC_VOLUMES__PVC_VOLUMES__CLAIM_NAME

string

required

quarkus.kubernetes.pvc-volumes."pvc-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_KUBERNETES_PVC_VOLUMES__PVC_VOLUMES__DEFAULT_MODE

string

0600

quarkus.kubernetes.pvc-volumes."pvc-volumes".optional

Optional

Environment variable: QUARKUS_KUBERNETES_PVC_VOLUMES__PVC_VOLUMES__OPTIONAL

boolean

false

quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".volume-id

The name of the disk to mount.

Environment variable: QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__VOLUME_ID

string

required

quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".partition

The partition.

Environment variable: QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__PARTITION

int

quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".fs-type

Filesystem type.

Environment variable: QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__FS_TYPE

string

ext4

quarkus.kubernetes.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_KUBERNETES_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__READ_ONLY

boolean

false

quarkus.kubernetes.azure-file-volumes."azure-file-volumes".share-name

The share name.

Environment variable: QUARKUS_KUBERNETES_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SHARE_NAME

string

required

quarkus.kubernetes.azure-file-volumes."azure-file-volumes".secret-name

The secret name.

Environment variable: QUARKUS_KUBERNETES_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SECRET_NAME

string

required

quarkus.kubernetes.azure-file-volumes."azure-file-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_KUBERNETES_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__READ_ONLY

boolean

false

quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".disk-name

The name of the disk to mount.

Environment variable: QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_NAME

string

required

quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".disk-uri

The URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed

Environment variable: QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_URI

string

required

quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".kind

Kind of disk.

Environment variable: QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__KIND

managed, shared

managed

quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".caching-mode

Disk caching mode.

Environment variable: QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__CACHING_MODE

read-write, read-only, none

read-write

quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".fs-type

File system type.

Environment variable: QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__FS_TYPE

string

ext4

quarkus.kubernetes.azure-disk-volumes."azure-disk-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_KUBERNETES_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__READ_ONLY

boolean

false

quarkus.kubernetes.init-containers."init-containers".image

The container image.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE

string

quarkus.kubernetes.init-containers."init-containers".working-dir

Working directory.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__WORKING_DIR

string

quarkus.kubernetes.init-containers."init-containers".command

The commands

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__COMMAND

list of string

quarkus.kubernetes.init-containers."init-containers".arguments

The arguments

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ARGUMENTS

list of string

quarkus.kubernetes.init-containers."init-containers".service-account

The service account.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__SERVICE_ACCOUNT

string

quarkus.kubernetes.init-containers."init-containers".host

The host under which the application is going to be exposed.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__HOST

string

quarkus.kubernetes.init-containers."init-containers".ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__CONTAINER_PORT

int

quarkus.kubernetes.init-containers."init-containers".ports."ports".host-port

The host port.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__HOST_PORT

int

quarkus.kubernetes.init-containers."init-containers".ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PATH

string

/

quarkus.kubernetes.init-containers."init-containers".ports."ports".protocol

The protocol.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.kubernetes.init-containers."init-containers".ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__NODE_PORT

int

quarkus.kubernetes.init-containers."init-containers".ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__TLS

boolean

false

quarkus.kubernetes.init-containers."init-containers".image-pull-policy

Image pull policy.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.kubernetes.init-containers."init-containers".image-pull-secrets

The image pull secret

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_SECRETS

list of string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-path

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_EXEC_ACTION

string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION

string

quarkus.kubernetes.init-containers."init-containers".liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.init-containers."init-containers".liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.init-containers."init-containers".liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.init-containers."init-containers".liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.init-containers."init-containers".liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.init-containers."init-containers".liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-path

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.init-containers."init-containers".readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.init-containers."init-containers".readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_EXEC_ACTION

string

quarkus.kubernetes.init-containers."init-containers".readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.init-containers."init-containers".readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION

string

quarkus.kubernetes.init-containers."init-containers".readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.init-containers."init-containers".readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.init-containers."init-containers".readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.init-containers."init-containers".readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.init-containers."init-containers".readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.init-containers."init-containers".readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.init-containers."init-containers".mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__NAME

string

quarkus.kubernetes.init-containers."init-containers".mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__PATH

string

quarkus.kubernetes.init-containers."init-containers".mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__SUB_PATH

string

quarkus.kubernetes.init-containers."init-containers".mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.kubernetes.init-containers."init-containers".resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_CPU

string

quarkus.kubernetes.init-containers."init-containers".resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_MEMORY

string

quarkus.kubernetes.init-containers."init-containers".resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_CPU

string

quarkus.kubernetes.init-containers."init-containers".resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_MEMORY

string

quarkus.kubernetes.init-containers."init-containers".env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_SECRETS

list of string

quarkus.kubernetes.init-containers."init-containers".env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_CONFIGMAPS

list of string

quarkus.kubernetes.init-containers."init-containers".env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.kubernetes.init-containers."init-containers".env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.kubernetes.init-containers."init-containers".env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.kubernetes.init-containers."init-containers".env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.kubernetes.init-containers."init-containers".env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.kubernetes.init-containers."init-containers".env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.kubernetes.init-containers."init-containers".env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KUBERNETES_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.kubernetes.sidecars."sidecars".image

The container image.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__IMAGE

string

quarkus.kubernetes.sidecars."sidecars".working-dir

Working directory.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__WORKING_DIR

string

quarkus.kubernetes.sidecars."sidecars".command

The commands

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__COMMAND

list of string

quarkus.kubernetes.sidecars."sidecars".arguments

The arguments

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ARGUMENTS

list of string

quarkus.kubernetes.sidecars."sidecars".service-account

The service account.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__SERVICE_ACCOUNT

string

quarkus.kubernetes.sidecars."sidecars".host

The host under which the application is going to be exposed.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__HOST

string

quarkus.kubernetes.sidecars."sidecars".ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__CONTAINER_PORT

int

quarkus.kubernetes.sidecars."sidecars".ports."ports".host-port

The host port.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__HOST_PORT

int

quarkus.kubernetes.sidecars."sidecars".ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__PATH

string

/

quarkus.kubernetes.sidecars."sidecars".ports."ports".protocol

The protocol.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.kubernetes.sidecars."sidecars".ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__NODE_PORT

int

quarkus.kubernetes.sidecars."sidecars".ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__PORTS__PORTS__TLS

boolean

false

quarkus.kubernetes.sidecars."sidecars".image-pull-policy

Image pull policy.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.kubernetes.sidecars."sidecars".image-pull-secrets

The image pull secret

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__IMAGE_PULL_SECRETS

list of string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-path

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_EXEC_ACTION

string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION

string

quarkus.kubernetes.sidecars."sidecars".liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.sidecars."sidecars".liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.sidecars."sidecars".liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.sidecars."sidecars".liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.sidecars."sidecars".liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.sidecars."sidecars".liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-path

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.kubernetes.sidecars."sidecars".readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.kubernetes.sidecars."sidecars".readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_EXEC_ACTION

string

quarkus.kubernetes.sidecars."sidecars".readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.kubernetes.sidecars."sidecars".readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION

string

quarkus.kubernetes.sidecars."sidecars".readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.kubernetes.sidecars."sidecars".readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.kubernetes.sidecars."sidecars".readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_PERIOD

Duration

10S

quarkus.kubernetes.sidecars."sidecars".readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.kubernetes.sidecars."sidecars".readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.kubernetes.sidecars."sidecars".readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.kubernetes.sidecars."sidecars".mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__NAME

string

quarkus.kubernetes.sidecars."sidecars".mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__PATH

string

quarkus.kubernetes.sidecars."sidecars".mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__SUB_PATH

string

quarkus.kubernetes.sidecars."sidecars".mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.kubernetes.sidecars."sidecars".resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_LIMITS_CPU

string

quarkus.kubernetes.sidecars."sidecars".resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_LIMITS_MEMORY

string

quarkus.kubernetes.sidecars."sidecars".resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_REQUESTS_CPU

string

quarkus.kubernetes.sidecars."sidecars".resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__RESOURCES_REQUESTS_MEMORY

string

quarkus.kubernetes.sidecars."sidecars".env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_SECRETS

list of string

quarkus.kubernetes.sidecars."sidecars".env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_CONFIGMAPS

list of string

quarkus.kubernetes.sidecars."sidecars".env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.kubernetes.sidecars."sidecars".env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.kubernetes.sidecars."sidecars".env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.kubernetes.sidecars."sidecars".env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.kubernetes.sidecars."sidecars".env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.kubernetes.sidecars."sidecars".env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.kubernetes.sidecars."sidecars".env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KUBERNETES_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.kubernetes.deployment-target

The target deployment platform. Defaults to kubernetes. Can be kubernetes, openshift, knative, minikube etc., or any combination of the above as comma separated list.

Environment variable: QUARKUS_KUBERNETES_DEPLOYMENT_TARGET

list of string

quarkus.kubernetes.hostaliases."host-aliases".ip

The ip address

Environment variable: QUARKUS_KUBERNETES_HOSTALIASES__HOST_ALIASES__IP

string

quarkus.kubernetes.hostaliases."host-aliases".hostnames

The hostnames to resolve to the ip

Environment variable: QUARKUS_KUBERNETES_HOSTALIASES__HOST_ALIASES__HOSTNAMES

list of string

quarkus.kubernetes.resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_KUBERNETES_RESOURCES_LIMITS_CPU

string

quarkus.kubernetes.resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_KUBERNETES_RESOURCES_LIMITS_MEMORY

string

quarkus.kubernetes.resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_KUBERNETES_RESOURCES_REQUESTS_CPU

string

quarkus.kubernetes.resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_KUBERNETES_RESOURCES_REQUESTS_MEMORY

string

quarkus.kubernetes.rbac.roles."roles".name

The name of the role.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__NAME

string

quarkus.kubernetes.rbac.roles."roles".namespace

The namespace of the role.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__NAMESPACE

string

quarkus.kubernetes.rbac.roles."roles".labels."label-name"

Labels to add into the Role resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__LABELS__LABEL_NAME_

Map<String,String>

quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".api-groups

API groups of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS

list of string

quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".non-resource-urls

Non resource URLs of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS

list of string

quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".resource-names

Resource names of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES

list of string

quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".resources

Resources of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCES

list of string

quarkus.kubernetes.rbac.roles."roles".policy-rules."policy-rules".verbs

Verbs of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__VERBS

list of string

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".name

The name of the cluster role.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__NAME

string

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".labels."label-name"

Labels to add into the ClusterRole resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__LABELS__LABEL_NAME_

Map<String,String>

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".api-groups

API groups of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS

list of string

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".non-resource-urls

Non resource URLs of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS

list of string

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resource-names

Resource names of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES

list of string

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resources

Resources of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCES

list of string

quarkus.kubernetes.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".verbs

Verbs of the policy rule.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__VERBS

list of string

quarkus.kubernetes.rbac.service-accounts."service-accounts".name

The name of the service account.

Environment variable: QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAME

string

quarkus.kubernetes.rbac.service-accounts."service-accounts".namespace

The namespace of the service account.

Environment variable: QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAMESPACE

string

quarkus.kubernetes.rbac.service-accounts."service-accounts".labels."label-name"

Labels of the service account.

Environment variable: QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.kubernetes.rbac.service-accounts."service-accounts".use-as-default

If true, this service account will be used in the generated Deployment resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__USE_AS_DEFAULT

boolean

quarkus.kubernetes.rbac.role-bindings."role-bindings".name

Name of the RoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__NAME

string

quarkus.kubernetes.rbac.role-bindings."role-bindings".labels."label-name"

Labels to add into the RoleBinding resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.kubernetes.rbac.role-bindings."role-bindings".role-name

The name of the Role resource to use by the RoleRef element in the generated Role Binding resource. By default, it’s "view" role name.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__ROLE_NAME

string

quarkus.kubernetes.rbac.role-bindings."role-bindings".cluster-wide

If the Role sets in the role-name property is cluster wide or not.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__CLUSTER_WIDE

boolean

quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".name

The "name" resource to use by the Subject element in the generated Role Binding resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME

string

quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".kind

The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND

string

ServiceAccount

quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".api-group

The "apiGroup" resource that matches with the "kind" property. By default, it’s empty.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP

string

quarkus.kubernetes.rbac.role-bindings."role-bindings".subjects."subjects".namespace

The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources.

Environment variable: QUARKUS_KUBERNETES_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE

string

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".name

Name of the ClusterRoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__NAME

string

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".labels."label-name"

Labels to add into the RoleBinding resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".role-name

The name of the ClusterRole resource to use by the RoleRef element in the generated ClusterRoleBinding resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__ROLE_NAME

string

required

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".name

The "name" resource to use by the Subject element in the generated Role Binding resource.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME

string

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".kind

The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND

string

ServiceAccount

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".api-group

The "apiGroup" resource that matches with the "kind" property. By default, it’s empty.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP

string

quarkus.kubernetes.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".namespace

The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources.

Environment variable: QUARKUS_KUBERNETES_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE

string

quarkus.kubernetes.ingress.expose

If true, the service will be exposed

Environment variable: QUARKUS_KUBERNETES_INGRESS_EXPOSE

boolean

false

quarkus.kubernetes.ingress.host

The host under which the application is going to be exposed

Environment variable: QUARKUS_KUBERNETES_INGRESS_HOST

string

quarkus.kubernetes.ingress.target-port

The default target named port. If not provided, it will be deducted from the Service resource ports. Options are: "http" and "https".

Environment variable: QUARKUS_KUBERNETES_INGRESS_TARGET_PORT

string

http

quarkus.kubernetes.ingress.ingress-class-name

The class of the Ingress. If the ingressClassName is omitted, a default Ingress class is used.

Environment variable: QUARKUS_KUBERNETES_INGRESS_INGRESS_CLASS_NAME

string

quarkus.kubernetes.ingress.annotations."annotation-name"

Custom annotations to add to exposition (route or ingress) resources

Environment variable: QUARKUS_KUBERNETES_INGRESS_ANNOTATIONS__ANNOTATION_NAME_

Map<String,String>

quarkus.kubernetes.ingress.tls."tls".enabled

If true, it will use the TLS configuration in the generated Ingress resource.

Environment variable: QUARKUS_KUBERNETES_INGRESS_TLS__TLS__ENABLED

boolean

false

quarkus.kubernetes.ingress.tls."tls".hosts

The list of hosts to be included in the TLS certificate. By default, it will use the application host.

Environment variable: QUARKUS_KUBERNETES_INGRESS_TLS__TLS__HOSTS

list of string

quarkus.kubernetes.ingress.rules."rules".host

The host under which the rule is going to be used.

Environment variable: QUARKUS_KUBERNETES_INGRESS_RULES__RULES__HOST

string

required

quarkus.kubernetes.ingress.rules."rules".path

The path under which the rule is going to be used. Default is "/".

Environment variable: QUARKUS_KUBERNETES_INGRESS_RULES__RULES__PATH

string

/

quarkus.kubernetes.ingress.rules."rules".path-type

The path type strategy to use by the Ingress rule. Default is "Prefix".

Environment variable: QUARKUS_KUBERNETES_INGRESS_RULES__RULES__PATH_TYPE

string

Prefix

quarkus.kubernetes.ingress.rules."rules".service-name

The service name to be used by this Ingress rule. Default is the generated service name of the application.

Environment variable: QUARKUS_KUBERNETES_INGRESS_RULES__RULES__SERVICE_NAME

string

quarkus.kubernetes.ingress.rules."rules".service-port-name

The service port name to be used by this Ingress rule. Default is the port name of the generated service of the application.

Environment variable: QUARKUS_KUBERNETES_INGRESS_RULES__RULES__SERVICE_PORT_NAME

string

quarkus.kubernetes.ingress.rules."rules".service-port-number

The service port number to be used by this Ingress rule. This is only used when the servicePortName is not set.

Environment variable: QUARKUS_KUBERNETES_INGRESS_RULES__RULES__SERVICE_PORT_NUMBER

int

quarkus.kubernetes.job.parallelism

Specifies the maximum desired number of pods the job should run at any given time.

Environment variable: QUARKUS_KUBERNETES_JOB_PARALLELISM

int

quarkus.kubernetes.job.completions

Specifies the desired number of successfully finished pods the job should be run with.

Environment variable: QUARKUS_KUBERNETES_JOB_COMPLETIONS

int

quarkus.kubernetes.job.completion-mode

CompletionMode specifies how Pod completions are tracked.

Environment variable: QUARKUS_KUBERNETES_JOB_COMPLETION_MODE

non-indexed, indexed

non-indexed

quarkus.kubernetes.job.backoff-limit

Specifies the number of retries before marking this job failed.

Environment variable: QUARKUS_KUBERNETES_JOB_BACKOFF_LIMIT

int

quarkus.kubernetes.job.active-deadline-seconds

Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer.

Environment variable: QUARKUS_KUBERNETES_JOB_ACTIVE_DEADLINE_SECONDS

long

quarkus.kubernetes.job.ttl-seconds-after-finished

Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted.

Environment variable: QUARKUS_KUBERNETES_JOB_TTL_SECONDS_AFTER_FINISHED

int

quarkus.kubernetes.job.suspend

Suspend specifies whether the Job controller should create Pods or not.

Environment variable: QUARKUS_KUBERNETES_JOB_SUSPEND

boolean

false

quarkus.kubernetes.job.restart-policy

Restart policy when the job container fails.

Environment variable: QUARKUS_KUBERNETES_JOB_RESTART_POLICY

on-failure, never

on-failure

quarkus.kubernetes.cron-job.schedule

The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_SCHEDULE

string

quarkus.kubernetes.cron-job.concurrency-policy

ConcurrencyPolicy describes how the job will be handled.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_CONCURRENCY_POLICY

allow, forbid, replace

allow

quarkus.kubernetes.cron-job.starting-deadline-seconds

Deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_STARTING_DEADLINE_SECONDS

long

quarkus.kubernetes.cron-job.failed-jobs-history-limit

The number of failed finished jobs to retain. The default value is 1.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_FAILED_JOBS_HISTORY_LIMIT

int

quarkus.kubernetes.cron-job.successful-jobs-history-limit

The number of successful finished jobs to retain. The default value is 3.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_SUCCESSFUL_JOBS_HISTORY_LIMIT

int

quarkus.kubernetes.cron-job.parallelism

Specifies the maximum desired number of pods the job should run at any given time.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_PARALLELISM

int

quarkus.kubernetes.cron-job.completions

Specifies the desired number of successfully finished pods the job should be run with.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_COMPLETIONS

int

quarkus.kubernetes.cron-job.completion-mode

CompletionMode specifies how Pod completions are tracked.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_COMPLETION_MODE

non-indexed, indexed

non-indexed

quarkus.kubernetes.cron-job.backoff-limit

Specifies the number of retries before marking this job failed.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_BACKOFF_LIMIT

int

quarkus.kubernetes.cron-job.active-deadline-seconds

Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_ACTIVE_DEADLINE_SECONDS

long

quarkus.kubernetes.cron-job.ttl-seconds-after-finished

Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_TTL_SECONDS_AFTER_FINISHED

int

quarkus.kubernetes.cron-job.suspend

Suspend specifies whether the Job controller should create Pods or not.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_SUSPEND

boolean

false

quarkus.kubernetes.cron-job.restart-policy

Restart policy when the job container fails.

Environment variable: QUARKUS_KUBERNETES_CRON_JOB_RESTART_POLICY

on-failure, never

on-failure

quarkus.kubernetes.add-version-to-label-selectors

If true, the 'app.kubernetes.io/version' label will be part of the selectors of Service and Deployment

Environment variable: QUARKUS_KUBERNETES_ADD_VERSION_TO_LABEL_SELECTORS

boolean

true

quarkus.kubernetes.add-name-to-label-selectors

If true, the 'app.kubernetes.io/name' label will be part of the selectors of Service and Deployment

Environment variable: QUARKUS_KUBERNETES_ADD_NAME_TO_LABEL_SELECTORS

boolean

true

quarkus.kubernetes.deploy

If set to true, Quarkus will attempt to deploy the application to the target Kubernetes cluster

Environment variable: QUARKUS_KUBERNETES_DEPLOY

boolean

false

quarkus.kubernetes.deploy-strategy

If deploy is enabled, it will follow this strategy to update the resources to the target Kubernetes cluster.

Environment variable: QUARKUS_KUBERNETES_DEPLOY_STRATEGY

create-or-update, create, replace, server-side-apply

create-or-update

quarkus.kubernetes.app-secret

If set, the secret will mounted to the application container and its contents will be used for application configuration.

Environment variable: QUARKUS_KUBERNETES_APP_SECRET

string

quarkus.kubernetes.app-config-map

If set, the config map will be mounted to the application container and its contents will be used for application configuration.

Environment variable: QUARKUS_KUBERNETES_APP_CONFIG_MAP

string

quarkus.kubernetes.security-context.se-linux-options.level

The SELinux level label that applies to the container.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_LEVEL

string

quarkus.kubernetes.security-context.se-linux-options.role

The SELinux role label that applies to the container.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_ROLE

string

quarkus.kubernetes.security-context.se-linux-options.type

The SELinux type label that applies to the container.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_TYPE

string

quarkus.kubernetes.security-context.se-linux-options.user

The SELinux user label that applies to the container.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_SE_LINUX_OPTIONS_USER

string

quarkus.kubernetes.security-context.windows-options.gmsa-credential-spec-name

The name of the GMSA credential spec to use.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC_NAME

string

quarkus.kubernetes.security-context.windows-options.gmsa-credential-spec

GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC

string

quarkus.kubernetes.security-context.windows-options.run-as-user-name

The UserName in Windows to run the entrypoint of the container process.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_RUN_AS_USER_NAME

string

quarkus.kubernetes.security-context.windows-options.host-process

HostProcess determines if a container should be run as a 'Host Process' container.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_WINDOWS_OPTIONS_HOST_PROCESS

boolean

quarkus.kubernetes.security-context.run-as-user

The UID to run the entrypoint of the container process.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_RUN_AS_USER

long

quarkus.kubernetes.security-context.run-as-group

The GID to run the entrypoint of the container process.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_RUN_AS_GROUP

long

quarkus.kubernetes.security-context.run-as-non-root

Indicates that the container must run as a non-root user.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_RUN_AS_NON_ROOT

boolean

quarkus.kubernetes.security-context.supplemental-groups

A list of groups applied to the first process run in each container, in addition to the container’s primary GID. If unspecified, no groups will be added to any container.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_SUPPLEMENTAL_GROUPS

list of long

quarkus.kubernetes.security-context.fs-group

A special supplemental group that applies to all containers in a pod.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_FS_GROUP

long

quarkus.kubernetes.security-context.sysctls."sysctl-name"

Sysctls hold a list of namespaced sysctls used for the pod.

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_SYSCTLS__SYSCTL_NAME_

Map<String,String>

quarkus.kubernetes.security-context.fs-group-change-policy

It holds policies that will be used for applying fsGroup to a volume when volume is mounted. Values: OnRootMismatch, Always

Environment variable: QUARKUS_KUBERNETES_SECURITY_CONTEXT_FS_GROUP_CHANGE_POLICY

on-root-mismatchIt indicates that volume’s ownership and permissions will be changed only when permission and ownership of root directory does not match with expected permissions on the volume., alwaysIt indicates that volume’s ownership and permissions should always be changed whenever volume is mounted inside a Pod. This the default behavior.

quarkus.kubernetes.container-name

If set, it will change the name of the container according to the configuration

Environment variable: QUARKUS_KUBERNETES_CONTAINER_NAME

string

quarkus.kubernetes.remote-debug.enabled

If true, the debug mode in pods will be enabled.

Environment variable: QUARKUS_KUBERNETES_REMOTE_DEBUG_ENABLED

boolean

false

quarkus.kubernetes.remote-debug.transport

The transport to use.

Environment variable: QUARKUS_KUBERNETES_REMOTE_DEBUG_TRANSPORT

string

dt_socket

quarkus.kubernetes.remote-debug.suspend

If enabled, it means the JVM will wait for the debugger to attach before executing the main class. If false, the JVM will immediately execute the main class, while listening for the debugger connection.

Environment variable: QUARKUS_KUBERNETES_REMOTE_DEBUG_SUSPEND

string

n

quarkus.kubernetes.remote-debug.address-port

It specifies the address at which the debug socket will listen.

Environment variable: QUARKUS_KUBERNETES_REMOTE_DEBUG_ADDRESS_PORT

int

5005

quarkus.kubernetes.init-tasks."init-tasks".enabled

If true, the init task will be generated. Otherwise, the init task resource generation will be skipped.

Environment variable: QUARKUS_KUBERNETES_INIT_TASKS__INIT_TASKS__ENABLED

boolean

true

quarkus.kubernetes.init-tasks."init-tasks".wait-for-container.image

The init task image to use by the init-container.

Environment variable: QUARKUS_KUBERNETES_INIT_TASKS__INIT_TASKS__WAIT_FOR_CONTAINER_IMAGE

string

groundnuty/k8s-wait-for:no-root-v1.7

quarkus.kubernetes.init-task-defaults.enabled

If true, the init task will be generated. Otherwise, the init task resource generation will be skipped.

Environment variable: QUARKUS_KUBERNETES_INIT_TASK_DEFAULTS_ENABLED

boolean

true

quarkus.kubernetes.init-task-defaults.wait-for-container.image

The init task image to use by the init-container.

Environment variable: QUARKUS_KUBERNETES_INIT_TASK_DEFAULTS_WAIT_FOR_CONTAINER_IMAGE

string

groundnuty/k8s-wait-for:no-root-v1.7

quarkus.kubernetes.idempotent

Switch used to control whether non-idempotent fields are included in generated kubernetes resources to improve git-ops compatibility

Environment variable: QUARKUS_KUBERNETES_IDEMPOTENT

boolean

false

quarkus.kubernetes.vcs-uri.enabled

Whether the vcs-uri annotation should be added to the generated configuration.

Environment variable: QUARKUS_KUBERNETES_VCS_URI_ENABLED

boolean

true

quarkus.kubernetes.vcs-uri.override

Optional override of the vcs-uri annotation.

Environment variable: QUARKUS_KUBERNETES_VCS_URI_OVERRIDE

string

quarkus.kubernetes.output-directory

Optionally set directory generated kubernetes resources will be written to. Default is target/kubernetes.

Environment variable: QUARKUS_KUBERNETES_OUTPUT_DIRECTORY

string

quarkus.kubernetes.env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_KUBERNETES_ENV_SECRETS

list of string

quarkus.kubernetes.env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_KUBERNETES_ENV_CONFIGMAPS

list of string

quarkus.kubernetes.env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_KUBERNETES_ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.kubernetes.env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_KUBERNETES_ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.kubernetes.env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_KUBERNETES_ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.kubernetes.env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_KUBERNETES_ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.kubernetes.env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_KUBERNETES_ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.kubernetes.env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KUBERNETES_ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.kubernetes.env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KUBERNETES_ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

Properties that use non-standard types, can be referenced by expanding the property. For example to define a kubernetes-readiness-probe which is of type Probe:

quarkus.kubernetes.readiness-probe.initial-delay=20s
quarkus.kubernetes.readiness-probe.period=45s

In this example initial-delay and period are fields of the type Probe. Below you will find tables describing all available types.

Client Connection Configuration

You may need to configure the connection to your Kubernetes cluster. By default, it automatically uses the active context used by kubectl.

For instance, if your cluster API endpoint uses a self-signed SSL Certificate you need to explicitly configure the client to trust it. You can achieve this by defining the following property:

quarkus.kubernetes-client.trust-certs=true

The full list of the Kubernetes client configuration properties is provided below.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	类型	默认
`quarkus.kubernetes-client.trust-certs` Whether the client should trust a self-signed certificate if so presented by the API server Environment variable: `QUARKUS_KUBERNETES_CLIENT_TRUST_CERTS` Show more	boolean
`quarkus.kubernetes-client.api-server-url` URL of the Kubernetes API server Environment variable: `QUARKUS_KUBERNETES_CLIENT_API_SERVER_URL` Show more	string
`quarkus.kubernetes-client.namespace` Default namespace to use Environment variable: `QUARKUS_KUBERNETES_CLIENT_NAMESPACE` Show more	string
`quarkus.kubernetes-client.ca-cert-file` CA certificate file Environment variable: `QUARKUS_KUBERNETES_CLIENT_CA_CERT_FILE` Show more	string
`quarkus.kubernetes-client.ca-cert-data` CA certificate data Environment variable: `QUARKUS_KUBERNETES_CLIENT_CA_CERT_DATA` Show more	string
`quarkus.kubernetes-client.client-cert-file` Client certificate file Environment variable: `QUARKUS_KUBERNETES_CLIENT_CLIENT_CERT_FILE` Show more	string
`quarkus.kubernetes-client.client-cert-data` Client certificate data Environment variable: `QUARKUS_KUBERNETES_CLIENT_CLIENT_CERT_DATA` Show more	string
`quarkus.kubernetes-client.client-key-file` Client key file Environment variable: `QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_FILE` Show more	string
`quarkus.kubernetes-client.client-key-data` Client key data Environment variable: `QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_DATA` Show more	string
`quarkus.kubernetes-client.client-key-algo` Client key algorithm Environment variable: `QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_ALGO` Show more	string
`quarkus.kubernetes-client.client-key-passphrase` Client key passphrase Environment variable: `QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_PASSPHRASE` Show more	string
`quarkus.kubernetes-client.username` Kubernetes auth username Environment variable: `QUARKUS_KUBERNETES_CLIENT_USERNAME` Show more	string
`quarkus.kubernetes-client.password` Kubernetes auth password Environment variable: `QUARKUS_KUBERNETES_CLIENT_PASSWORD` Show more	string
`quarkus.kubernetes-client.token` Kubernetes oauth token Environment variable: `QUARKUS_KUBERNETES_CLIENT_TOKEN` Show more	string
`quarkus.kubernetes-client.watch-reconnect-interval` Watch reconnect interval Environment variable: `QUARKUS_KUBERNETES_CLIENT_WATCH_RECONNECT_INTERVAL` Show more	Duration
`quarkus.kubernetes-client.watch-reconnect-limit` Maximum reconnect attempts in case of watch failure By default there is no limit to the number of reconnect attempts Environment variable: `QUARKUS_KUBERNETES_CLIENT_WATCH_RECONNECT_LIMIT` Show more	int
`quarkus.kubernetes-client.connection-timeout` Maximum amount of time to wait for a connection with the API server to be established Environment variable: `QUARKUS_KUBERNETES_CLIENT_CONNECTION_TIMEOUT` Show more	Duration
`quarkus.kubernetes-client.request-timeout` Maximum amount of time to wait for a request to the API server to be completed Environment variable: `QUARKUS_KUBERNETES_CLIENT_REQUEST_TIMEOUT` Show more	Duration
`quarkus.kubernetes-client.request-retry-backoff-limit` Maximum number of retry attempts for API requests that fail with an HTTP code of >= 500 Environment variable: `QUARKUS_KUBERNETES_CLIENT_REQUEST_RETRY_BACKOFF_LIMIT` Show more	int
`quarkus.kubernetes-client.request-retry-backoff-interval` Time interval between retry attempts for API requests that fail with an HTTP code of >= 500 Environment variable: `QUARKUS_KUBERNETES_CLIENT_REQUEST_RETRY_BACKOFF_INTERVAL` Show more	Duration
`quarkus.kubernetes-client.http-proxy` HTTP proxy used to access the Kubernetes API server Environment variable: `QUARKUS_KUBERNETES_CLIENT_HTTP_PROXY` Show more	string
`quarkus.kubernetes-client.https-proxy` HTTPS proxy used to access the Kubernetes API server Environment variable: `QUARKUS_KUBERNETES_CLIENT_HTTPS_PROXY` Show more	string
`quarkus.kubernetes-client.proxy-username` Proxy username Environment variable: `QUARKUS_KUBERNETES_CLIENT_PROXY_USERNAME` Show more	string
`quarkus.kubernetes-client.proxy-password` Proxy password Environment variable: `QUARKUS_KUBERNETES_CLIENT_PROXY_PASSWORD` Show more	string
`quarkus.kubernetes-client.no-proxy` IP addresses or hosts to exclude from proxying Environment variable: `QUARKUS_KUBERNETES_CLIENT_NO_PROXY` Show more	list of string
`quarkus.kubernetes-client.generate-rbac` Enable the generation of the RBAC manifests. If enabled and no other role binding are provided using the properties `quarkus.kubernetes.rbac.`, it will generate a default role binding using the role "view" and the application service account. Environment variable: `QUARKUS_KUBERNETES_CLIENT_GENERATE_RBAC` Show more	boolean	`true`
Dev Services	类型	默认
`quarkus.kubernetes-client.devservices.enabled` If Dev Services for Kubernetes should be used. (default to true) If this is true and kubernetes client is not configured then a kubernetes cluster will be started and will be used. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_ENABLED` Show more	boolean	`true`
`quarkus.kubernetes-client.devservices.api-version` The kubernetes api server version to use. If not set, Dev Services for Kubernetes will use the latest supported version of the given flavor. see https://github.com/dajudge/kindcontainer/blob/master/k8s-versions.json Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_API_VERSION` Show more	string
`quarkus.kubernetes-client.devservices.flavor` The flavor to use (kind, k3s or api-only). Default to api-only. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_FLAVOR` Show more	`kind`kind (needs priviledge docker), `k3s`k3s (needs priviledge docker), `api-only`api only	`api-only`api only
`quarkus.kubernetes-client.devservices.override-kubeconfig` By default, if a kubeconfig is found, Dev Services for Kubernetes will not start. Set this to true to override the kubeconfig config. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_OVERRIDE_KUBECONFIG` Show more	boolean	`false`
`quarkus.kubernetes-client.devservices.shared` Indicates if the Kubernetes cluster managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kubernetes starts a new container. The discovery uses the `quarkus-dev-service-kubernetes` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_SHARED` Show more	boolean	`true`
`quarkus.kubernetes-client.devservices.service-name` The value of the `quarkus-dev-service-kubernetes` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Kubernetes looks for a container with the `quarkus-dev-service-kubernetes` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-kubernetes` label set to the specified value. This property is used when you need multiple shared Kubernetes clusters. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_SERVICE_NAME` Show more	string	`kubernetes`
`quarkus.kubernetes-client.devservices.container-env."environment-variable-name"` Environment variables that are passed to the container. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_CONTAINER_ENV__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>

Configuration property

类型

默认

quarkus.kubernetes-client.trust-certs

Whether the client should trust a self-signed certificate if so presented by the API server

Environment variable: QUARKUS_KUBERNETES_CLIENT_TRUST_CERTS

boolean

quarkus.kubernetes-client.api-server-url

URL of the Kubernetes API server

Environment variable: QUARKUS_KUBERNETES_CLIENT_API_SERVER_URL

string

quarkus.kubernetes-client.namespace

Default namespace to use

Environment variable: QUARKUS_KUBERNETES_CLIENT_NAMESPACE

string

quarkus.kubernetes-client.ca-cert-file

CA certificate file

Environment variable: QUARKUS_KUBERNETES_CLIENT_CA_CERT_FILE

string

quarkus.kubernetes-client.ca-cert-data

CA certificate data

Environment variable: QUARKUS_KUBERNETES_CLIENT_CA_CERT_DATA

string

quarkus.kubernetes-client.client-cert-file

Client certificate file

Environment variable: QUARKUS_KUBERNETES_CLIENT_CLIENT_CERT_FILE

string

quarkus.kubernetes-client.client-cert-data

Client certificate data

Environment variable: QUARKUS_KUBERNETES_CLIENT_CLIENT_CERT_DATA

string

quarkus.kubernetes-client.client-key-file

Client key file

Environment variable: QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_FILE

string

quarkus.kubernetes-client.client-key-data

Client key data

Environment variable: QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_DATA

string

quarkus.kubernetes-client.client-key-algo

Client key algorithm

Environment variable: QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_ALGO

string

quarkus.kubernetes-client.client-key-passphrase

Client key passphrase

Environment variable: QUARKUS_KUBERNETES_CLIENT_CLIENT_KEY_PASSPHRASE

string

quarkus.kubernetes-client.username

Kubernetes auth username

Environment variable: QUARKUS_KUBERNETES_CLIENT_USERNAME

string

quarkus.kubernetes-client.password

Kubernetes auth password

Environment variable: QUARKUS_KUBERNETES_CLIENT_PASSWORD

string

quarkus.kubernetes-client.token

Kubernetes oauth token

Environment variable: QUARKUS_KUBERNETES_CLIENT_TOKEN

string

quarkus.kubernetes-client.watch-reconnect-interval

Watch reconnect interval

Environment variable: QUARKUS_KUBERNETES_CLIENT_WATCH_RECONNECT_INTERVAL

Duration

quarkus.kubernetes-client.watch-reconnect-limit

Maximum reconnect attempts in case of watch failure By default there is no limit to the number of reconnect attempts

Environment variable: QUARKUS_KUBERNETES_CLIENT_WATCH_RECONNECT_LIMIT

int

quarkus.kubernetes-client.connection-timeout

Maximum amount of time to wait for a connection with the API server to be established

Environment variable: QUARKUS_KUBERNETES_CLIENT_CONNECTION_TIMEOUT

Duration

quarkus.kubernetes-client.request-timeout

Maximum amount of time to wait for a request to the API server to be completed

Environment variable: QUARKUS_KUBERNETES_CLIENT_REQUEST_TIMEOUT

Duration

quarkus.kubernetes-client.request-retry-backoff-limit

Maximum number of retry attempts for API requests that fail with an HTTP code of >= 500

Environment variable: QUARKUS_KUBERNETES_CLIENT_REQUEST_RETRY_BACKOFF_LIMIT

int

quarkus.kubernetes-client.request-retry-backoff-interval

Time interval between retry attempts for API requests that fail with an HTTP code of >= 500

Environment variable: QUARKUS_KUBERNETES_CLIENT_REQUEST_RETRY_BACKOFF_INTERVAL

Duration

quarkus.kubernetes-client.http-proxy

HTTP proxy used to access the Kubernetes API server

Environment variable: QUARKUS_KUBERNETES_CLIENT_HTTP_PROXY

string

quarkus.kubernetes-client.https-proxy

HTTPS proxy used to access the Kubernetes API server

Environment variable: QUARKUS_KUBERNETES_CLIENT_HTTPS_PROXY

string

quarkus.kubernetes-client.proxy-username

Proxy username

Environment variable: QUARKUS_KUBERNETES_CLIENT_PROXY_USERNAME

string

quarkus.kubernetes-client.proxy-password

Proxy password

Environment variable: QUARKUS_KUBERNETES_CLIENT_PROXY_PASSWORD

string

quarkus.kubernetes-client.no-proxy

IP addresses or hosts to exclude from proxying

Environment variable: QUARKUS_KUBERNETES_CLIENT_NO_PROXY

list of string

quarkus.kubernetes-client.generate-rbac

Enable the generation of the RBAC manifests. If enabled and no other role binding are provided using the properties quarkus.kubernetes.rbac., it will generate a default role binding using the role "view" and the application service account.

Environment variable: QUARKUS_KUBERNETES_CLIENT_GENERATE_RBAC

boolean

true

Dev Services

类型

默认

quarkus.kubernetes-client.devservices.enabled

If Dev Services for Kubernetes should be used. (default to true) If this is true and kubernetes client is not configured then a kubernetes cluster will be started and will be used.

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_ENABLED

boolean

true

quarkus.kubernetes-client.devservices.api-version

The kubernetes api server version to use. If not set, Dev Services for Kubernetes will use the latest supported version of the given flavor. see https://github.com/dajudge/kindcontainer/blob/master/k8s-versions.json

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_API_VERSION

string

quarkus.kubernetes-client.devservices.flavor

The flavor to use (kind, k3s or api-only). Default to api-only.

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_FLAVOR

kindkind (needs priviledge docker), k3sk3s (needs priviledge docker), api-onlyapi only

api-onlyapi only

quarkus.kubernetes-client.devservices.override-kubeconfig

By default, if a kubeconfig is found, Dev Services for Kubernetes will not start. Set this to true to override the kubeconfig config.

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_OVERRIDE_KUBECONFIG

boolean

false

quarkus.kubernetes-client.devservices.shared

Indicates if the Kubernetes cluster managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kubernetes starts a new container.

The discovery uses the quarkus-dev-service-kubernetes label. The value is configured using the service-name property.

Container sharing is only used in dev mode.

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_SHARED

boolean

true

quarkus.kubernetes-client.devservices.service-name

The value of the quarkus-dev-service-kubernetes label attached to the started container. This property is used when shared is set to true. In this case, before starting a container, Dev Services for Kubernetes looks for a container with the quarkus-dev-service-kubernetes label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the quarkus-dev-service-kubernetes label set to the specified value.

This property is used when you need multiple shared Kubernetes clusters.

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_SERVICE_NAME

string

kubernetes

quarkus.kubernetes-client.devservices.container-env."environment-variable-name"

Environment variables that are passed to the container.

Environment variable: QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_CONTAINER_ENV__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

OpenShift

One way to deploy an application to OpenShift is to use s2i (source to image) to create an image stream from the source and then deploy the image stream:

CLI

quarkus extension remove kubernetes,jib
quarkus extension add openshift

oc new-project quarkus-project
quarkus build -Dquarkus.container-image.build=true

oc new-app --name=greeting  quarkus-project/kubernetes-quickstart:1.0.0-SNAPSHOT
oc expose svc/greeting
oc get route
curl <route>/greeting

Maven

./mvnw quarkus:remove-extension -Dextensions="kubernetes, jib"
./mvnw quarkus:add-extension -Dextensions="openshift"

oc new-project quarkus-project
./mvnw clean package -Dquarkus.container-image.build=true

oc new-app --name=greeting  quarkus-project/kubernetes-quickstart:1.0.0-SNAPSHOT
oc expose svc/greeting
oc get route
curl <route>/greeting

Gradle

./gradlew removeExtension --extensions="kubernetes, jib"
./gradlew addExtension --extensions="openshift"

oc new-project quarkus-project
./gradlew build -Dquarkus.container-image.build=true

oc new-app --name=greeting  quarkus-project/kubernetes-quickstart:1.0.0-SNAPSHOT
oc expose svc/greeting
oc get route
curl <route>/greeting

See further information in Deploying to OpenShift.

A description of OpenShift resources and customisable properties is given below alongside Kubernetes resources to show similarities where applicable. This includes an alternative to oc new-app … above, i.e. oc apply -f target/kubernetes/openshift.json .

To enable the generation of OpenShift resources, you need to include OpenShift in the target platforms:

quarkus.kubernetes.deployment-target=openshift

If you need to generate resources for both platforms (vanilla Kubernetes and OpenShift), then you need to include both (comma separated).

quarkus.kubernetes.deployment-target=kubernetes,openshift

Following the execution of ./mvnw package -Dquarkus.container-image.build=true you will notice amongst the other files that are created, two files named openshift.json and openshift.yml in the target/kubernetes/ directory.

These manifests can be deployed as is to a running cluster, using kubectl:

kubectl apply -f target/kubernetes/openshift.json

OpenShift’s users might want to use oc rather than kubectl:

oc apply -f target/kubernetes/openshift.json

For users that prefer to keep the application.properties independent of the deployment platform, the deployment target can be specified directly in the deploy command by adding -Dquarkus.kubernetes.deployment-target=openshift in addition to -Dquarkus.kubernetes.deploy=true. Furthermore, Quarkus allows collapsing the two properties into one: -Dquarkus.openshift.deploy=true.

./mvnw clean package -Dquarkus.openshift.deploy=true

The equivalent with gradle:

./gradlew build -Dquarkus.openshift.deploy=true

In case that both properties are used with conflicting values quarkus.kubernetes.deployment-target is used.

Quarkus also provides the OpenShift extension. This extension is basically a wrapper around the Kubernetes extension and relieves OpenShift users of the necessity of setting the deployment-target property to openshift

The OpenShift resources can be customized in a similar approach with Kubernetes.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	类型	默认
`quarkus.openshift.flavor` The OpenShift flavor / version to use. Older versions of OpenShift have minor differences in the labels and fields they support. This option allows users to have their manifests automatically aligned to the OpenShift 'flavor' they use. Environment variable: `QUARKUS_OPENSHIFT_FLAVOR` Show more	`v3`, `v4`	`v4`
`quarkus.openshift.deployment-kind` The kind of the deployment resource to use. Supported values are 'Deployment', 'StatefulSet', 'Job', 'CronJob' and 'DeploymentConfig'. Defaults to 'DeploymentConfig' if `flavor == v3`, or 'Deployment' otherwise. DeploymentConfig is deprecated as of OpenShift 4.14. See https://access.redhat.com/articles/7041372 for details. Environment variable: `QUARKUS_OPENSHIFT_DEPLOYMENT_KIND` Show more	`deployment`, `deployment-config`, `stateful-set`, `job`, `cron-job`, `knative-service`
`quarkus.openshift.part-of` The name of the group this component belongs too Environment variable: `QUARKUS_OPENSHIFT_PART_OF` Show more	string
`quarkus.openshift.name` The name of the application. This value will be used for naming Kubernetes resources like: 'Deployment', 'Service' and so on… Environment variable: `QUARKUS_OPENSHIFT_NAME` Show more	string
`quarkus.openshift.version` The version of the application. Environment variable: `QUARKUS_OPENSHIFT_VERSION` Show more	string
`quarkus.openshift.namespace` The namespace the generated resources should belong to. If not value is set, then the 'namespace' field will not be added to the 'metadata' section of the generated manifests. This in turn means that when the manifests are applied to a cluster, the namespace will be resolved from the current Kubernetes context (see https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#context for more details). Environment variable: `QUARKUS_OPENSHIFT_NAMESPACE` Show more	string
`quarkus.openshift.labels."label-name"` Custom labels to add to all resources Environment variable: `QUARKUS_OPENSHIFT_LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.annotations."annotation-name"` Custom annotations to add to all resources Environment variable: `QUARKUS_OPENSHIFT_ANNOTATIONS__ANNOTATION_NAME_` Show more	Map<String,String>
`quarkus.openshift.add-build-timestamp` Add the build timestamp to the Kubernetes annotations This is a very useful way to have manifests of successive builds of the same application differ - thus ensuring that Kubernetes will apply the updated resources Environment variable: `QUARKUS_OPENSHIFT_ADD_BUILD_TIMESTAMP` Show more	boolean	`true`
`quarkus.openshift.working-dir` Working directory Environment variable: `QUARKUS_OPENSHIFT_WORKING_DIR` Show more	string
`quarkus.openshift.command` The commands Environment variable: `QUARKUS_OPENSHIFT_COMMAND` Show more	list of string
`quarkus.openshift.arguments` The arguments Environment variable: `QUARKUS_OPENSHIFT_ARGUMENTS` Show more	list of string
`quarkus.openshift.service-account` The service account Environment variable: `QUARKUS_OPENSHIFT_SERVICE_ACCOUNT` Show more	string
`quarkus.openshift.ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_OPENSHIFT_PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.openshift.ports."ports".host-port` The host port. Environment variable: `QUARKUS_OPENSHIFT_PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.openshift.ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_OPENSHIFT_PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.openshift.ports."ports".protocol` The protocol. Environment variable: `QUARKUS_OPENSHIFT_PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.openshift.ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_OPENSHIFT_PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.openshift.ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_OPENSHIFT_PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.openshift.replicas` The number of desired pods Environment variable: `QUARKUS_OPENSHIFT_REPLICAS` Show more	int	`1`
`quarkus.openshift.service-type` The type of service that will be generated for the application Environment variable: `QUARKUS_OPENSHIFT_SERVICE_TYPE` Show more	`cluster-ip`, `node-port`, `load-balancer`, `external-name`	`cluster-ip`
`quarkus.openshift.node-port` The nodePort to set when serviceType is set to nodePort Environment variable: `QUARKUS_OPENSHIFT_NODE_PORT` Show more	int
`quarkus.openshift.image-pull-policy` Image pull policy Environment variable: `QUARKUS_OPENSHIFT_IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.openshift.image-pull-secrets` The image pull secret Environment variable: `QUARKUS_OPENSHIFT_IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.openshift.generate-image-pull-secret` Enable generation of image pull secret, when the container image username and password are provided. Environment variable: `QUARKUS_OPENSHIFT_GENERATE_IMAGE_PULL_SECRET` Show more	boolean	`false`
`quarkus.openshift.liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.startup-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.startup-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.startup-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.startup-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.startup-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.startup-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.startup-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.startup-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.startup-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.startup-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.startup-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.startup-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.startup-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_STARTUP_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.prometheus.annotations` When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary. Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_ANNOTATIONS` Show more	boolean	`true`
`quarkus.openshift.prometheus.generate-service-monitor` When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary. Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_GENERATE_SERVICE_MONITOR` Show more	boolean	`true`
`quarkus.openshift.prometheus.prefix` Define the annotation prefix used for scrape values, this value will be used as the base for other annotation name defaults. Altering the base for generated annotations can make it easier to define re-labeling rules and avoid unexpected knock-on effects. The default value is `prometheus.io` See Prometheus example: https://github.com/prometheus/prometheus/blob/main/documentation/examples/prometheus-kubernetes.yml Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_PREFIX` Show more	string	`prometheus.io`
`quarkus.openshift.prometheus.scrape` Define the annotation used to indicate services that should be scraped. By default, `/scrape` will be appended to the defined prefix. Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_SCRAPE` Show more	string
`quarkus.openshift.prometheus.path` Define the annotation used to indicate the path to scrape. By default, `/path` will be appended to the defined prefix. Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_PATH` Show more	string
`quarkus.openshift.prometheus.port` Define the annotation used to indicate the port to scrape. By default, `/port` will be appended to the defined prefix. Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_PORT` Show more	string
`quarkus.openshift.prometheus.scheme` Define the annotation used to indicate the scheme to use for scraping By default, `/scheme` will be appended to the defined prefix. Environment variable: `QUARKUS_OPENSHIFT_PROMETHEUS_SCHEME` Show more	string
`quarkus.openshift.mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.openshift.mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.openshift.mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.openshift.mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.openshift.secret-volumes."secret-volumes".secret-name` The name of the secret to mount. Environment variable: `QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__SECRET_NAME` Show more	string	required
`quarkus.openshift.secret-volumes."secret-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.openshift.secret-volumes."secret-volumes".items."items".path` The path where the file will be mounted. Environment variable: `QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__PATH` Show more	string	required
`quarkus.openshift.secret-volumes."secret-volumes".items."items".mode` It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used. Environment variable: `QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__MODE` Show more	int	`-1`
`quarkus.openshift.secret-volumes."secret-volumes".optional` Optional Environment variable: `QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.openshift.config-map-volumes."config-map-volumes".config-map-name` The name of the ConfigMap to mount. Environment variable: `QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__CONFIG_MAP_NAME` Show more	string	required
`quarkus.openshift.config-map-volumes."config-map-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.openshift.config-map-volumes."config-map-volumes".items."items".path` The path where the file will be mounted. Environment variable: `QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__PATH` Show more	string	required
`quarkus.openshift.config-map-volumes."config-map-volumes".items."items".mode` It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used. Environment variable: `QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__MODE` Show more	int	`-1`
`quarkus.openshift.config-map-volumes."config-map-volumes".optional` Optional Environment variable: `QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.openshift.empty-dir-volumes` EmptyDir volumes Environment variable: `QUARKUS_OPENSHIFT_EMPTY_DIR_VOLUMES` Show more	list of string
`quarkus.openshift.git-repo-volumes."git-repo-volumes".repository` Git repository URL. Environment variable: `QUARKUS_OPENSHIFT_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REPOSITORY` Show more	string	required
`quarkus.openshift.git-repo-volumes."git-repo-volumes".directory` The directory of the repository to mount. Environment variable: `QUARKUS_OPENSHIFT_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__DIRECTORY` Show more	string
`quarkus.openshift.git-repo-volumes."git-repo-volumes".revision` The commit hash to use. Environment variable: `QUARKUS_OPENSHIFT_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REVISION` Show more	string
`quarkus.openshift.pvc-volumes."pvc-volumes".claim-name` The name of the claim to mount. Environment variable: `QUARKUS_OPENSHIFT_PVC_VOLUMES__PVC_VOLUMES__CLAIM_NAME` Show more	string	required
`quarkus.openshift.pvc-volumes."pvc-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_OPENSHIFT_PVC_VOLUMES__PVC_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.openshift.pvc-volumes."pvc-volumes".optional` Optional Environment variable: `QUARKUS_OPENSHIFT_PVC_VOLUMES__PVC_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".volume-id` The name of the disk to mount. Environment variable: `QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__VOLUME_ID` Show more	string	required
`quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".partition` The partition. Environment variable: `QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__PARTITION` Show more	int
`quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".fs-type` Filesystem type. Environment variable: `QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__FS_TYPE` Show more	string	`ext4`
`quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.openshift.azure-file-volumes."azure-file-volumes".share-name` The share name. Environment variable: `QUARKUS_OPENSHIFT_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SHARE_NAME` Show more	string	required
`quarkus.openshift.azure-file-volumes."azure-file-volumes".secret-name` The secret name. Environment variable: `QUARKUS_OPENSHIFT_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SECRET_NAME` Show more	string	required
`quarkus.openshift.azure-file-volumes."azure-file-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_OPENSHIFT_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.openshift.azure-disk-volumes."azure-disk-volumes".disk-name` The name of the disk to mount. Environment variable: `QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_NAME` Show more	string	required
`quarkus.openshift.azure-disk-volumes."azure-disk-volumes".disk-uri` The URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed Environment variable: `QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_URI` Show more	string	required
`quarkus.openshift.azure-disk-volumes."azure-disk-volumes".kind` Kind of disk. Environment variable: `QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__KIND` Show more	`managed`, `shared`	`managed`
`quarkus.openshift.azure-disk-volumes."azure-disk-volumes".caching-mode` Disk caching mode. Environment variable: `QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__CACHING_MODE` Show more	`read-write`, `read-only`, `none`	`read-write`
`quarkus.openshift.azure-disk-volumes."azure-disk-volumes".fs-type` File system type. Environment variable: `QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__FS_TYPE` Show more	string	`ext4`
`quarkus.openshift.azure-disk-volumes."azure-disk-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.openshift.init-containers."init-containers".image` The container image. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE` Show more	string
`quarkus.openshift.init-containers."init-containers".working-dir` Working directory. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__WORKING_DIR` Show more	string
`quarkus.openshift.init-containers."init-containers".command` The commands Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__COMMAND` Show more	list of string
`quarkus.openshift.init-containers."init-containers".arguments` The arguments Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ARGUMENTS` Show more	list of string
`quarkus.openshift.init-containers."init-containers".service-account` The service account. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__SERVICE_ACCOUNT` Show more	string
`quarkus.openshift.init-containers."init-containers".host` The host under which the application is going to be exposed. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__HOST` Show more	string
`quarkus.openshift.init-containers."init-containers".ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.openshift.init-containers."init-containers".ports."ports".host-port` The host port. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.openshift.init-containers."init-containers".ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.openshift.init-containers."init-containers".ports."ports".protocol` The protocol. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.openshift.init-containers."init-containers".ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.openshift.init-containers."init-containers".ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.openshift.init-containers."init-containers".image-pull-policy` Image pull policy. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.openshift.init-containers."init-containers".image-pull-secrets` The image pull secret Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.init-containers."init-containers".liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.init-containers."init-containers".liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.init-containers."init-containers".liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.init-containers."init-containers".liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.init-containers."init-containers".liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.init-containers."init-containers".liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.init-containers."init-containers".liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.init-containers."init-containers".liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.init-containers."init-containers".liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.init-containers."init-containers".readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.init-containers."init-containers".readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.init-containers."init-containers".readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.init-containers."init-containers".readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.init-containers."init-containers".readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.init-containers."init-containers".readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.init-containers."init-containers".readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.init-containers."init-containers".readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.init-containers."init-containers".readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.init-containers."init-containers".mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.openshift.init-containers."init-containers".mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.openshift.init-containers."init-containers".mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.openshift.init-containers."init-containers".mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.openshift.init-containers."init-containers".resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_CPU` Show more	string
`quarkus.openshift.init-containers."init-containers".resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.openshift.init-containers."init-containers".resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.openshift.init-containers."init-containers".resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.openshift.init-containers."init-containers".env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_SECRETS` Show more	list of string
`quarkus.openshift.init-containers."init-containers".env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_CONFIGMAPS` Show more	list of string
`quarkus.openshift.init-containers."init-containers".env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.openshift.init-containers."init-containers".env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.openshift.init-containers."init-containers".env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.openshift.init-containers."init-containers".env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.openshift.init-containers."init-containers".env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.openshift.init-containers."init-containers".env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.openshift.init-containers."init-containers".env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.openshift.sidecars."sidecars".image` The container image. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__IMAGE` Show more	string
`quarkus.openshift.sidecars."sidecars".working-dir` Working directory. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__WORKING_DIR` Show more	string
`quarkus.openshift.sidecars."sidecars".command` The commands Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__COMMAND` Show more	list of string
`quarkus.openshift.sidecars."sidecars".arguments` The arguments Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ARGUMENTS` Show more	list of string
`quarkus.openshift.sidecars."sidecars".service-account` The service account. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__SERVICE_ACCOUNT` Show more	string
`quarkus.openshift.sidecars."sidecars".host` The host under which the application is going to be exposed. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__HOST` Show more	string
`quarkus.openshift.sidecars."sidecars".ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.openshift.sidecars."sidecars".ports."ports".host-port` The host port. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.openshift.sidecars."sidecars".ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.openshift.sidecars."sidecars".ports."ports".protocol` The protocol. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.openshift.sidecars."sidecars".ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.openshift.sidecars."sidecars".ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.openshift.sidecars."sidecars".image-pull-policy` Image pull policy. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.openshift.sidecars."sidecars".image-pull-secrets` The image pull secret Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.sidecars."sidecars".liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.sidecars."sidecars".liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.sidecars."sidecars".liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.sidecars."sidecars".liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.sidecars."sidecars".liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.sidecars."sidecars".liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.sidecars."sidecars".liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.sidecars."sidecars".liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.sidecars."sidecars".liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.openshift.sidecars."sidecars".readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.openshift.sidecars."sidecars".readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.openshift.sidecars."sidecars".readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.openshift.sidecars."sidecars".readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.openshift.sidecars."sidecars".readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.openshift.sidecars."sidecars".readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.openshift.sidecars."sidecars".readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.openshift.sidecars."sidecars".readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.openshift.sidecars."sidecars".readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.openshift.sidecars."sidecars".mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.openshift.sidecars."sidecars".mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.openshift.sidecars."sidecars".mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.openshift.sidecars."sidecars".mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.openshift.sidecars."sidecars".resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_LIMITS_CPU` Show more	string
`quarkus.openshift.sidecars."sidecars".resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.openshift.sidecars."sidecars".resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.openshift.sidecars."sidecars".resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.openshift.sidecars."sidecars".env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_SECRETS` Show more	list of string
`quarkus.openshift.sidecars."sidecars".env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_CONFIGMAPS` Show more	list of string
`quarkus.openshift.sidecars."sidecars".env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.openshift.sidecars."sidecars".env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.openshift.sidecars."sidecars".env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.openshift.sidecars."sidecars".env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.openshift.sidecars."sidecars".env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.openshift.sidecars."sidecars".env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.openshift.sidecars."sidecars".env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.openshift.host-aliases."host-aliases".ip` The ip address Environment variable: `QUARKUS_OPENSHIFT_HOST_ALIASES__HOST_ALIASES__IP` Show more	string
`quarkus.openshift.host-aliases."host-aliases".hostnames` The hostnames to resolve to the ip Environment variable: `QUARKUS_OPENSHIFT_HOST_ALIASES__HOST_ALIASES__HOSTNAMES` Show more	list of string
`quarkus.openshift.resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_OPENSHIFT_RESOURCES_LIMITS_CPU` Show more	string
`quarkus.openshift.resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_OPENSHIFT_RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.openshift.resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_OPENSHIFT_RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.openshift.resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_OPENSHIFT_RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.openshift.container-name` If set, it will change the name of the container according to the configuration Environment variable: `QUARKUS_OPENSHIFT_CONTAINER_NAME` Show more	string
`quarkus.openshift.route.expose` If true, the service will be exposed Environment variable: `QUARKUS_OPENSHIFT_ROUTE_EXPOSE` Show more	boolean	`false`
`quarkus.openshift.route.host` The host under which the application is going to be exposed Environment variable: `QUARKUS_OPENSHIFT_ROUTE_HOST` Show more	string
`quarkus.openshift.route.target-port` The target named port. If not provided, it will be deducted from the Service resource ports. Options are: "http" and "https". Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TARGET_PORT` Show more	string	`http`
`quarkus.openshift.route.annotations."annotation-name"` Custom annotations to add to exposition (route or ingress) resources Environment variable: `QUARKUS_OPENSHIFT_ROUTE_ANNOTATIONS__ANNOTATION_NAME_` Show more	Map<String,String>
`quarkus.openshift.route.labels."label-name"` Custom labels to add to exposition (route or ingress) resources Environment variable: `QUARKUS_OPENSHIFT_ROUTE_LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.route.tls.ca-certificate` The cert authority certificate contents. Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TLS_CA_CERTIFICATE` Show more	string
`quarkus.openshift.route.tls.certificate` The certificate contents. Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TLS_CERTIFICATE` Show more	string
`quarkus.openshift.route.tls.destination-ca-certificate` The contents of the ca certificate of the final destination. Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TLS_DESTINATION_CA_CERTIFICATE` Show more	string
`quarkus.openshift.route.tls.insecure-edge-termination-policy` The desired behavior for insecure connections to a route. Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TLS_INSECURE_EDGE_TERMINATION_POLICY` Show more	string
`quarkus.openshift.route.tls.key` The key file contents. Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TLS_KEY` Show more	string
`quarkus.openshift.route.tls.termination` The termination type. Environment variable: `QUARKUS_OPENSHIFT_ROUTE_TLS_TERMINATION` Show more	string
`quarkus.openshift.add-version-to-label-selectors` If true, the 'app.kubernetes.io/version' label will be part of the selectors of Service and DeploymentConfig Environment variable: `QUARKUS_OPENSHIFT_ADD_VERSION_TO_LABEL_SELECTORS` Show more	boolean	`true`
`quarkus.openshift.add-name-to-label-selectors` If true, the 'app.kubernetes.io/name' label will be part of the selectors of Service and Deployment Environment variable: `QUARKUS_OPENSHIFT_ADD_NAME_TO_LABEL_SELECTORS` Show more	boolean	`true`
`quarkus.openshift.job.parallelism` Specifies the maximum desired number of pods the job should run at any given time. Environment variable: `QUARKUS_OPENSHIFT_JOB_PARALLELISM` Show more	int
`quarkus.openshift.job.completions` Specifies the desired number of successfully finished pods the job should be run with. Environment variable: `QUARKUS_OPENSHIFT_JOB_COMPLETIONS` Show more	int
`quarkus.openshift.job.completion-mode` CompletionMode specifies how Pod completions are tracked. Environment variable: `QUARKUS_OPENSHIFT_JOB_COMPLETION_MODE` Show more	`non-indexed`, `indexed`	`non-indexed`
`quarkus.openshift.job.backoff-limit` Specifies the number of retries before marking this job failed. Environment variable: `QUARKUS_OPENSHIFT_JOB_BACKOFF_LIMIT` Show more	int
`quarkus.openshift.job.active-deadline-seconds` Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. Environment variable: `QUARKUS_OPENSHIFT_JOB_ACTIVE_DEADLINE_SECONDS` Show more	long
`quarkus.openshift.job.ttl-seconds-after-finished` Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. Environment variable: `QUARKUS_OPENSHIFT_JOB_TTL_SECONDS_AFTER_FINISHED` Show more	int
`quarkus.openshift.job.suspend` Suspend specifies whether the Job controller should create Pods or not. Environment variable: `QUARKUS_OPENSHIFT_JOB_SUSPEND` Show more	boolean	`false`
`quarkus.openshift.job.restart-policy` Restart policy when the job container fails. Environment variable: `QUARKUS_OPENSHIFT_JOB_RESTART_POLICY` Show more	`on-failure`, `never`	`on-failure`
`quarkus.openshift.cron-job.schedule` The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_SCHEDULE` Show more	string
`quarkus.openshift.cron-job.concurrency-policy` ConcurrencyPolicy describes how the job will be handled. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_CONCURRENCY_POLICY` Show more	`allow`, `forbid`, `replace`	`allow`
`quarkus.openshift.cron-job.starting-deadline-seconds` Deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_STARTING_DEADLINE_SECONDS` Show more	long
`quarkus.openshift.cron-job.failed-jobs-history-limit` The number of failed finished jobs to retain. The default value is 1. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_FAILED_JOBS_HISTORY_LIMIT` Show more	int
`quarkus.openshift.cron-job.successful-jobs-history-limit` The number of successful finished jobs to retain. The default value is 3. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_SUCCESSFUL_JOBS_HISTORY_LIMIT` Show more	int
`quarkus.openshift.cron-job.parallelism` Specifies the maximum desired number of pods the job should run at any given time. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_PARALLELISM` Show more	int
`quarkus.openshift.cron-job.completions` Specifies the desired number of successfully finished pods the job should be run with. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_COMPLETIONS` Show more	int
`quarkus.openshift.cron-job.completion-mode` CompletionMode specifies how Pod completions are tracked. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_COMPLETION_MODE` Show more	`non-indexed`, `indexed`	`non-indexed`
`quarkus.openshift.cron-job.backoff-limit` Specifies the number of retries before marking this job failed. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_BACKOFF_LIMIT` Show more	int
`quarkus.openshift.cron-job.active-deadline-seconds` Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_ACTIVE_DEADLINE_SECONDS` Show more	long
`quarkus.openshift.cron-job.ttl-seconds-after-finished` Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_TTL_SECONDS_AFTER_FINISHED` Show more	int
`quarkus.openshift.cron-job.suspend` Suspend specifies whether the Job controller should create Pods or not. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_SUSPEND` Show more	boolean	`false`
`quarkus.openshift.cron-job.restart-policy` Restart policy when the job container fails. Environment variable: `QUARKUS_OPENSHIFT_CRON_JOB_RESTART_POLICY` Show more	`on-failure`, `never`	`on-failure`
`quarkus.openshift.rbac.roles."roles".name` The name of the role. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__NAME` Show more	string
`quarkus.openshift.rbac.roles."roles".namespace` The namespace of the role. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__NAMESPACE` Show more	string
`quarkus.openshift.rbac.roles."roles".labels."label-name"` Labels to add into the Role resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".api-groups` API groups of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS` Show more	list of string
`quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".non-resource-urls` Non resource URLs of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS` Show more	list of string
`quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".resource-names` Resource names of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES` Show more	list of string
`quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".resources` Resources of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCES` Show more	list of string
`quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".verbs` Verbs of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__VERBS` Show more	list of string
`quarkus.openshift.rbac.cluster-roles."cluster-roles".name` The name of the cluster role. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__NAME` Show more	string
`quarkus.openshift.rbac.cluster-roles."cluster-roles".labels."label-name"` Labels to add into the ClusterRole resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".api-groups` API groups of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS` Show more	list of string
`quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".non-resource-urls` Non resource URLs of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS` Show more	list of string
`quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resource-names` Resource names of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES` Show more	list of string
`quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resources` Resources of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCES` Show more	list of string
`quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".verbs` Verbs of the policy rule. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__VERBS` Show more	list of string
`quarkus.openshift.rbac.service-accounts."service-accounts".name` The name of the service account. Environment variable: `QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAME` Show more	string
`quarkus.openshift.rbac.service-accounts."service-accounts".namespace` The namespace of the service account. Environment variable: `QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAMESPACE` Show more	string
`quarkus.openshift.rbac.service-accounts."service-accounts".labels."label-name"` Labels of the service account. Environment variable: `QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.rbac.service-accounts."service-accounts".use-as-default` If true, this service account will be used in the generated Deployment resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__USE_AS_DEFAULT` Show more	boolean
`quarkus.openshift.rbac.role-bindings."role-bindings".name` Name of the RoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__NAME` Show more	string
`quarkus.openshift.rbac.role-bindings."role-bindings".labels."label-name"` Labels to add into the RoleBinding resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.rbac.role-bindings."role-bindings".role-name` The name of the Role resource to use by the RoleRef element in the generated Role Binding resource. By default, it’s "view" role name. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__ROLE_NAME` Show more	string
`quarkus.openshift.rbac.role-bindings."role-bindings".cluster-wide` If the Role sets in the `role-name` property is cluster wide or not. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__CLUSTER_WIDE` Show more	boolean
`quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".name` The "name" resource to use by the Subject element in the generated Role Binding resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME` Show more	string
`quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".kind` The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND` Show more	string	`ServiceAccount`
`quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".api-group` The "apiGroup" resource that matches with the "kind" property. By default, it’s empty. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP` Show more	string
`quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".namespace` The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources. Environment variable: `QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE` Show more	string
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".name` Name of the ClusterRoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__NAME` Show more	string
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".labels."label-name"` Labels to add into the RoleBinding resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".role-name` The name of the ClusterRole resource to use by the RoleRef element in the generated ClusterRoleBinding resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__ROLE_NAME` Show more	string	required
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".name` The "name" resource to use by the Subject element in the generated Role Binding resource. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME` Show more	string
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".kind` The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND` Show more	string	`ServiceAccount`
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".api-group` The "apiGroup" resource that matches with the "kind" property. By default, it’s empty. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP` Show more	string
`quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".namespace` The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources. Environment variable: `QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE` Show more	string
`quarkus.openshift.env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_OPENSHIFT_ENV_SECRETS` Show more	list of string
`quarkus.openshift.env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_OPENSHIFT_ENV_CONFIGMAPS` Show more	list of string
`quarkus.openshift.env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_OPENSHIFT_ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.openshift.env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_OPENSHIFT_ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.openshift.env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_OPENSHIFT_ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.openshift.env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_OPENSHIFT_ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.openshift.env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_OPENSHIFT_ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.openshift.env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_OPENSHIFT_ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.openshift.env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_OPENSHIFT_ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.openshift.app-secret` If set, the secret will mounted to the application container and its contents will be used for application configuration. Environment variable: `QUARKUS_OPENSHIFT_APP_SECRET` Show more	string
`quarkus.openshift.app-config-map` If set, the config amp will be mounted to the application container and its contents will be used for application configuration. Environment variable: `QUARKUS_OPENSHIFT_APP_CONFIG_MAP` Show more	string
`quarkus.openshift.security-context.se-linux-options.level` The SELinux level label that applies to the container. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_LEVEL` Show more	string
`quarkus.openshift.security-context.se-linux-options.role` The SELinux role label that applies to the container. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_ROLE` Show more	string
`quarkus.openshift.security-context.se-linux-options.type` The SELinux type label that applies to the container. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_TYPE` Show more	string
`quarkus.openshift.security-context.se-linux-options.user` The SELinux user label that applies to the container. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_USER` Show more	string
`quarkus.openshift.security-context.windows-options.gmsa-credential-spec-name` The name of the GMSA credential spec to use. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC_NAME` Show more	string
`quarkus.openshift.security-context.windows-options.gmsa-credential-spec` GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC` Show more	string
`quarkus.openshift.security-context.windows-options.run-as-user-name` The UserName in Windows to run the entrypoint of the container process. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_RUN_AS_USER_NAME` Show more	string
`quarkus.openshift.security-context.windows-options.host-process` HostProcess determines if a container should be run as a 'Host Process' container. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_HOST_PROCESS` Show more	boolean
`quarkus.openshift.security-context.run-as-user` The UID to run the entrypoint of the container process. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_RUN_AS_USER` Show more	long
`quarkus.openshift.security-context.run-as-group` The GID to run the entrypoint of the container process. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_RUN_AS_GROUP` Show more	long
`quarkus.openshift.security-context.run-as-non-root` Indicates that the container must run as a non-root user. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_RUN_AS_NON_ROOT` Show more	boolean
`quarkus.openshift.security-context.supplemental-groups` A list of groups applied to the first process run in each container, in addition to the container’s primary GID. If unspecified, no groups will be added to any container. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SUPPLEMENTAL_GROUPS` Show more	list of long
`quarkus.openshift.security-context.fs-group` A special supplemental group that applies to all containers in a pod. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_FS_GROUP` Show more	long
`quarkus.openshift.security-context.sysctls."sysctl-name"` Sysctls hold a list of namespaced sysctls used for the pod. Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SYSCTLS__SYSCTL_NAME_` Show more	Map<String,String>
`quarkus.openshift.security-context.fs-group-change-policy` It holds policies that will be used for applying fsGroup to a volume when volume is mounted. Values: OnRootMismatch, Always Environment variable: `QUARKUS_OPENSHIFT_SECURITY_CONTEXT_FS_GROUP_CHANGE_POLICY` Show more	`on-root-mismatch`It indicates that volume’s ownership and permissions will be changed only when permission and ownership of root directory does not match with expected permissions on the volume., `always`It indicates that volume’s ownership and permissions should always be changed whenever volume is mounted inside a Pod. This the default behavior.
`quarkus.openshift.remote-debug.enabled` If true, the debug mode in pods will be enabled. Environment variable: `QUARKUS_OPENSHIFT_REMOTE_DEBUG_ENABLED` Show more	boolean	`false`
`quarkus.openshift.remote-debug.transport` The transport to use. Environment variable: `QUARKUS_OPENSHIFT_REMOTE_DEBUG_TRANSPORT` Show more	string	`dt_socket`
`quarkus.openshift.remote-debug.suspend` If enabled, it means the JVM will wait for the debugger to attach before executing the main class. If false, the JVM will immediately execute the main class, while listening for the debugger connection. Environment variable: `QUARKUS_OPENSHIFT_REMOTE_DEBUG_SUSPEND` Show more	string	`n`
`quarkus.openshift.remote-debug.address-port` It specifies the address at which the debug socket will listen. Environment variable: `QUARKUS_OPENSHIFT_REMOTE_DEBUG_ADDRESS_PORT` Show more	int	`5005`
`quarkus.openshift.deploy` If set to true, Quarkus will attempt to deploy the application to the target Openshift cluster Environment variable: `QUARKUS_OPENSHIFT_DEPLOY` Show more	boolean	`false`
`quarkus.openshift.deploy-strategy` If deploy is enabled, it will follow this strategy to update the resources to the target OpenShift cluster. Environment variable: `QUARKUS_OPENSHIFT_DEPLOY_STRATEGY` Show more	`create-or-update`, `create`, `replace`, `server-side-apply`	`create-or-update`
`quarkus.openshift.init-tasks."init-tasks".enabled` If true, the init task will be generated. Otherwise, the init task resource generation will be skipped. Environment variable: `QUARKUS_OPENSHIFT_INIT_TASKS__INIT_TASKS__ENABLED` Show more	boolean	`true`
`quarkus.openshift.init-tasks."init-tasks".wait-for-container.image` The init task image to use by the init-container. Environment variable: `QUARKUS_OPENSHIFT_INIT_TASKS__INIT_TASKS__WAIT_FOR_CONTAINER_IMAGE` Show more	string	`groundnuty/k8s-wait-for:no-root-v1.7`
`quarkus.openshift.init-task-defaults.enabled` If true, the init task will be generated. Otherwise, the init task resource generation will be skipped. Environment variable: `QUARKUS_OPENSHIFT_INIT_TASK_DEFAULTS_ENABLED` Show more	boolean	`true`
`quarkus.openshift.init-task-defaults.wait-for-container.image` The init task image to use by the init-container. Environment variable: `QUARKUS_OPENSHIFT_INIT_TASK_DEFAULTS_WAIT_FOR_CONTAINER_IMAGE` Show more	string	`groundnuty/k8s-wait-for:no-root-v1.7`
`quarkus.openshift.idempotent` Switch used to control whether non-idempotent fields are included in generated kubernetes resources to improve git-ops compatibility Environment variable: `QUARKUS_OPENSHIFT_IDEMPOTENT` Show more	boolean	`false`
`quarkus.openshift.vcs-uri.enabled` Whether the vcs-uri annotation should be added to the generated configuration. Environment variable: `QUARKUS_OPENSHIFT_VCS_URI_ENABLED` Show more	boolean	`true`
`quarkus.openshift.vcs-uri.override` Optional override of the vcs-uri annotation. Environment variable: `QUARKUS_OPENSHIFT_VCS_URI_OVERRIDE` Show more	string

Configuration property

类型

默认

quarkus.openshift.flavor

The OpenShift flavor / version to use. Older versions of OpenShift have minor differences in the labels and fields they support. This option allows users to have their manifests automatically aligned to the OpenShift 'flavor' they use.

Environment variable: QUARKUS_OPENSHIFT_FLAVOR

v3, v4

v4

quarkus.openshift.deployment-kind

The kind of the deployment resource to use. Supported values are 'Deployment', 'StatefulSet', 'Job', 'CronJob' and 'DeploymentConfig'. Defaults to 'DeploymentConfig' if flavor == v3, or 'Deployment' otherwise. DeploymentConfig is deprecated as of OpenShift 4.14. See https://access.redhat.com/articles/7041372 for details.

Environment variable: QUARKUS_OPENSHIFT_DEPLOYMENT_KIND

deployment, deployment-config, stateful-set, job, cron-job, knative-service

quarkus.openshift.part-of

The name of the group this component belongs too

Environment variable: QUARKUS_OPENSHIFT_PART_OF

string

quarkus.openshift.name

The name of the application. This value will be used for naming Kubernetes resources like: 'Deployment', 'Service' and so on…

Environment variable: QUARKUS_OPENSHIFT_NAME

string

quarkus.openshift.version

The version of the application.

Environment variable: QUARKUS_OPENSHIFT_VERSION

string

quarkus.openshift.namespace

Environment variable: QUARKUS_OPENSHIFT_NAMESPACE

string

quarkus.openshift.labels."label-name"

Custom labels to add to all resources

Environment variable: QUARKUS_OPENSHIFT_LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.annotations."annotation-name"

Custom annotations to add to all resources

Environment variable: QUARKUS_OPENSHIFT_ANNOTATIONS__ANNOTATION_NAME_

Map<String,String>

quarkus.openshift.add-build-timestamp

Add the build timestamp to the Kubernetes annotations This is a very useful way to have manifests of successive builds of the same application differ - thus ensuring that Kubernetes will apply the updated resources

Environment variable: QUARKUS_OPENSHIFT_ADD_BUILD_TIMESTAMP

boolean

true

quarkus.openshift.working-dir

Working directory

Environment variable: QUARKUS_OPENSHIFT_WORKING_DIR

string

quarkus.openshift.command

The commands

Environment variable: QUARKUS_OPENSHIFT_COMMAND

list of string

quarkus.openshift.arguments

The arguments

Environment variable: QUARKUS_OPENSHIFT_ARGUMENTS

list of string

quarkus.openshift.service-account

The service account

Environment variable: QUARKUS_OPENSHIFT_SERVICE_ACCOUNT

string

quarkus.openshift.ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_OPENSHIFT_PORTS__PORTS__CONTAINER_PORT

int

quarkus.openshift.ports."ports".host-port

The host port.

Environment variable: QUARKUS_OPENSHIFT_PORTS__PORTS__HOST_PORT

int

quarkus.openshift.ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_OPENSHIFT_PORTS__PORTS__PATH

string

/

quarkus.openshift.ports."ports".protocol

The protocol.

Environment variable: QUARKUS_OPENSHIFT_PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.openshift.ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_OPENSHIFT_PORTS__PORTS__NODE_PORT

int

quarkus.openshift.ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_OPENSHIFT_PORTS__PORTS__TLS

boolean

false

quarkus.openshift.replicas

The number of desired pods

Environment variable: QUARKUS_OPENSHIFT_REPLICAS

int

1

quarkus.openshift.service-type

The type of service that will be generated for the application

Environment variable: QUARKUS_OPENSHIFT_SERVICE_TYPE

cluster-ip, node-port, load-balancer, external-name

cluster-ip

quarkus.openshift.node-port

The nodePort to set when serviceType is set to nodePort

Environment variable: QUARKUS_OPENSHIFT_NODE_PORT

int

quarkus.openshift.image-pull-policy

Image pull policy

Environment variable: QUARKUS_OPENSHIFT_IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.openshift.image-pull-secrets

The image pull secret

Environment variable: QUARKUS_OPENSHIFT_IMAGE_PULL_SECRETS

list of string

quarkus.openshift.generate-image-pull-secret

Enable generation of image pull secret, when the container image username and password are provided.

Environment variable: QUARKUS_OPENSHIFT_GENERATE_IMAGE_PULL_SECRET

boolean

false

quarkus.openshift.liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.liveness-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_EXEC_ACTION

string

quarkus.openshift.liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_GRPC_ACTION

string

quarkus.openshift.liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.openshift.liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.readiness-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_EXEC_ACTION

string

quarkus.openshift.readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_GRPC_ACTION

string

quarkus.openshift.readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_PERIOD

Duration

10S

quarkus.openshift.readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.startup-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.startup-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.startup-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.startup-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.startup-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_EXEC_ACTION

string

quarkus.openshift.startup-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.startup-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_GRPC_ACTION

string

quarkus.openshift.startup-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.startup-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.startup-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_PERIOD

Duration

10S

quarkus.openshift.startup-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.startup-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.startup-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_STARTUP_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.prometheus.annotations

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_ANNOTATIONS

boolean

true

quarkus.openshift.prometheus.generate-service-monitor

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_GENERATE_SERVICE_MONITOR

boolean

true

quarkus.openshift.prometheus.prefix

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_PREFIX

string

prometheus.io

quarkus.openshift.prometheus.scrape

Define the annotation used to indicate services that should be scraped. By default, /scrape will be appended to the defined prefix.

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_SCRAPE

string

quarkus.openshift.prometheus.path

Define the annotation used to indicate the path to scrape. By default, /path will be appended to the defined prefix.

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_PATH

string

quarkus.openshift.prometheus.port

Define the annotation used to indicate the port to scrape. By default, /port will be appended to the defined prefix.

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_PORT

string

quarkus.openshift.prometheus.scheme

Define the annotation used to indicate the scheme to use for scraping By default, /scheme will be appended to the defined prefix.

Environment variable: QUARKUS_OPENSHIFT_PROMETHEUS_SCHEME

string

quarkus.openshift.mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__NAME

string

quarkus.openshift.mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__PATH

string

quarkus.openshift.mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__SUB_PATH

string

quarkus.openshift.mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_OPENSHIFT_MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.openshift.secret-volumes."secret-volumes".secret-name

The name of the secret to mount.

Environment variable: QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__SECRET_NAME

string

required

quarkus.openshift.secret-volumes."secret-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__DEFAULT_MODE

string

0600

quarkus.openshift.secret-volumes."secret-volumes".items."items".path

The path where the file will be mounted.

Environment variable: QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__PATH

string

required

quarkus.openshift.secret-volumes."secret-volumes".items."items".mode

It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used.

Environment variable: QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__MODE

int

-1

quarkus.openshift.secret-volumes."secret-volumes".optional

Optional

Environment variable: QUARKUS_OPENSHIFT_SECRET_VOLUMES__SECRET_VOLUMES__OPTIONAL

boolean

false

quarkus.openshift.config-map-volumes."config-map-volumes".config-map-name

The name of the ConfigMap to mount.

Environment variable: QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__CONFIG_MAP_NAME

string

required

quarkus.openshift.config-map-volumes."config-map-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__DEFAULT_MODE

string

0600

quarkus.openshift.config-map-volumes."config-map-volumes".items."items".path

The path where the file will be mounted.

Environment variable: QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__PATH

string

required

quarkus.openshift.config-map-volumes."config-map-volumes".items."items".mode

It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used.

Environment variable: QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__MODE

int

-1

quarkus.openshift.config-map-volumes."config-map-volumes".optional

Optional

Environment variable: QUARKUS_OPENSHIFT_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__OPTIONAL

boolean

false

quarkus.openshift.empty-dir-volumes

EmptyDir volumes

Environment variable: QUARKUS_OPENSHIFT_EMPTY_DIR_VOLUMES

list of string

quarkus.openshift.git-repo-volumes."git-repo-volumes".repository

Git repository URL.

Environment variable: QUARKUS_OPENSHIFT_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REPOSITORY

string

required

quarkus.openshift.git-repo-volumes."git-repo-volumes".directory

The directory of the repository to mount.

Environment variable: QUARKUS_OPENSHIFT_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__DIRECTORY

string

quarkus.openshift.git-repo-volumes."git-repo-volumes".revision

The commit hash to use.

Environment variable: QUARKUS_OPENSHIFT_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REVISION

string

quarkus.openshift.pvc-volumes."pvc-volumes".claim-name

The name of the claim to mount.

Environment variable: QUARKUS_OPENSHIFT_PVC_VOLUMES__PVC_VOLUMES__CLAIM_NAME

string

required

quarkus.openshift.pvc-volumes."pvc-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_OPENSHIFT_PVC_VOLUMES__PVC_VOLUMES__DEFAULT_MODE

string

0600

quarkus.openshift.pvc-volumes."pvc-volumes".optional

Optional

Environment variable: QUARKUS_OPENSHIFT_PVC_VOLUMES__PVC_VOLUMES__OPTIONAL

boolean

false

quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".volume-id

The name of the disk to mount.

Environment variable: QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__VOLUME_ID

string

required

quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".partition

The partition.

Environment variable: QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__PARTITION

int

quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".fs-type

Filesystem type.

Environment variable: QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__FS_TYPE

string

ext4

quarkus.openshift.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_OPENSHIFT_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__READ_ONLY

boolean

false

quarkus.openshift.azure-file-volumes."azure-file-volumes".share-name

The share name.

Environment variable: QUARKUS_OPENSHIFT_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SHARE_NAME

string

required

quarkus.openshift.azure-file-volumes."azure-file-volumes".secret-name

The secret name.

Environment variable: QUARKUS_OPENSHIFT_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SECRET_NAME

string

required

quarkus.openshift.azure-file-volumes."azure-file-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_OPENSHIFT_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__READ_ONLY

boolean

false

quarkus.openshift.azure-disk-volumes."azure-disk-volumes".disk-name

The name of the disk to mount.

Environment variable: QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_NAME

string

required

quarkus.openshift.azure-disk-volumes."azure-disk-volumes".disk-uri

The URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed

Environment variable: QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_URI

string

required

quarkus.openshift.azure-disk-volumes."azure-disk-volumes".kind

Kind of disk.

Environment variable: QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__KIND

managed, shared

managed

quarkus.openshift.azure-disk-volumes."azure-disk-volumes".caching-mode

Disk caching mode.

Environment variable: QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__CACHING_MODE

read-write, read-only, none

read-write

quarkus.openshift.azure-disk-volumes."azure-disk-volumes".fs-type

File system type.

Environment variable: QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__FS_TYPE

string

ext4

quarkus.openshift.azure-disk-volumes."azure-disk-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_OPENSHIFT_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__READ_ONLY

boolean

false

quarkus.openshift.init-containers."init-containers".image

The container image.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE

string

quarkus.openshift.init-containers."init-containers".working-dir

Working directory.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__WORKING_DIR

string

quarkus.openshift.init-containers."init-containers".command

The commands

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__COMMAND

list of string

quarkus.openshift.init-containers."init-containers".arguments

The arguments

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ARGUMENTS

list of string

quarkus.openshift.init-containers."init-containers".service-account

The service account.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__SERVICE_ACCOUNT

string

quarkus.openshift.init-containers."init-containers".host

The host under which the application is going to be exposed.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__HOST

string

quarkus.openshift.init-containers."init-containers".ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__CONTAINER_PORT

int

quarkus.openshift.init-containers."init-containers".ports."ports".host-port

The host port.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__HOST_PORT

int

quarkus.openshift.init-containers."init-containers".ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PATH

string

/

quarkus.openshift.init-containers."init-containers".ports."ports".protocol

The protocol.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.openshift.init-containers."init-containers".ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__NODE_PORT

int

quarkus.openshift.init-containers."init-containers".ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__TLS

boolean

false

quarkus.openshift.init-containers."init-containers".image-pull-policy

Image pull policy.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.openshift.init-containers."init-containers".image-pull-secrets

The image pull secret

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_SECRETS

list of string

quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.init-containers."init-containers".liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.init-containers."init-containers".liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_EXEC_ACTION

string

quarkus.openshift.init-containers."init-containers".liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.init-containers."init-containers".liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION

string

quarkus.openshift.init-containers."init-containers".liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.init-containers."init-containers".liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.init-containers."init-containers".liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.openshift.init-containers."init-containers".liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.init-containers."init-containers".liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.init-containers."init-containers".liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.init-containers."init-containers".readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.init-containers."init-containers".readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_EXEC_ACTION

string

quarkus.openshift.init-containers."init-containers".readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.init-containers."init-containers".readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION

string

quarkus.openshift.init-containers."init-containers".readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.init-containers."init-containers".readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.init-containers."init-containers".readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_PERIOD

Duration

10S

quarkus.openshift.init-containers."init-containers".readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.init-containers."init-containers".readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.init-containers."init-containers".readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.init-containers."init-containers".mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__NAME

string

quarkus.openshift.init-containers."init-containers".mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__PATH

string

quarkus.openshift.init-containers."init-containers".mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__SUB_PATH

string

quarkus.openshift.init-containers."init-containers".mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.openshift.init-containers."init-containers".resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_CPU

string

quarkus.openshift.init-containers."init-containers".resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_MEMORY

string

quarkus.openshift.init-containers."init-containers".resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_CPU

string

quarkus.openshift.init-containers."init-containers".resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_MEMORY

string

quarkus.openshift.init-containers."init-containers".env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_SECRETS

list of string

quarkus.openshift.init-containers."init-containers".env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_CONFIGMAPS

list of string

quarkus.openshift.init-containers."init-containers".env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.openshift.init-containers."init-containers".env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.openshift.init-containers."init-containers".env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.openshift.init-containers."init-containers".env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.openshift.init-containers."init-containers".env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.openshift.init-containers."init-containers".env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.openshift.init-containers."init-containers".env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_OPENSHIFT_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.openshift.sidecars."sidecars".image

The container image.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__IMAGE

string

quarkus.openshift.sidecars."sidecars".working-dir

Working directory.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__WORKING_DIR

string

quarkus.openshift.sidecars."sidecars".command

The commands

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__COMMAND

list of string

quarkus.openshift.sidecars."sidecars".arguments

The arguments

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ARGUMENTS

list of string

quarkus.openshift.sidecars."sidecars".service-account

The service account.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__SERVICE_ACCOUNT

string

quarkus.openshift.sidecars."sidecars".host

The host under which the application is going to be exposed.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__HOST

string

quarkus.openshift.sidecars."sidecars".ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__CONTAINER_PORT

int

quarkus.openshift.sidecars."sidecars".ports."ports".host-port

The host port.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__HOST_PORT

int

quarkus.openshift.sidecars."sidecars".ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__PATH

string

/

quarkus.openshift.sidecars."sidecars".ports."ports".protocol

The protocol.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.openshift.sidecars."sidecars".ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__NODE_PORT

int

quarkus.openshift.sidecars."sidecars".ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__PORTS__PORTS__TLS

boolean

false

quarkus.openshift.sidecars."sidecars".image-pull-policy

Image pull policy.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.openshift.sidecars."sidecars".image-pull-secrets

The image pull secret

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__IMAGE_PULL_SECRETS

list of string

quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.sidecars."sidecars".liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.sidecars."sidecars".liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_EXEC_ACTION

string

quarkus.openshift.sidecars."sidecars".liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.sidecars."sidecars".liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION

string

quarkus.openshift.sidecars."sidecars".liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.sidecars."sidecars".liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.sidecars."sidecars".liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.openshift.sidecars."sidecars".liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.sidecars."sidecars".liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.sidecars."sidecars".liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-path

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.openshift.sidecars."sidecars".readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.openshift.sidecars."sidecars".readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_EXEC_ACTION

string

quarkus.openshift.sidecars."sidecars".readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.openshift.sidecars."sidecars".readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION

string

quarkus.openshift.sidecars."sidecars".readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.openshift.sidecars."sidecars".readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.openshift.sidecars."sidecars".readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_PERIOD

Duration

10S

quarkus.openshift.sidecars."sidecars".readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.openshift.sidecars."sidecars".readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.openshift.sidecars."sidecars".readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.openshift.sidecars."sidecars".mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__NAME

string

quarkus.openshift.sidecars."sidecars".mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__PATH

string

quarkus.openshift.sidecars."sidecars".mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__SUB_PATH

string

quarkus.openshift.sidecars."sidecars".mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.openshift.sidecars."sidecars".resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_LIMITS_CPU

string

quarkus.openshift.sidecars."sidecars".resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_LIMITS_MEMORY

string

quarkus.openshift.sidecars."sidecars".resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_REQUESTS_CPU

string

quarkus.openshift.sidecars."sidecars".resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__RESOURCES_REQUESTS_MEMORY

string

quarkus.openshift.sidecars."sidecars".env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_SECRETS

list of string

quarkus.openshift.sidecars."sidecars".env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_CONFIGMAPS

list of string

quarkus.openshift.sidecars."sidecars".env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.openshift.sidecars."sidecars".env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.openshift.sidecars."sidecars".env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.openshift.sidecars."sidecars".env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.openshift.sidecars."sidecars".env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.openshift.sidecars."sidecars".env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.openshift.sidecars."sidecars".env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_OPENSHIFT_SIDECARS__SIDECARS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.openshift.host-aliases."host-aliases".ip

The ip address

Environment variable: QUARKUS_OPENSHIFT_HOST_ALIASES__HOST_ALIASES__IP

string

quarkus.openshift.host-aliases."host-aliases".hostnames

The hostnames to resolve to the ip

Environment variable: QUARKUS_OPENSHIFT_HOST_ALIASES__HOST_ALIASES__HOSTNAMES

list of string

quarkus.openshift.resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_OPENSHIFT_RESOURCES_LIMITS_CPU

string

quarkus.openshift.resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_OPENSHIFT_RESOURCES_LIMITS_MEMORY

string

quarkus.openshift.resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_OPENSHIFT_RESOURCES_REQUESTS_CPU

string

quarkus.openshift.resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_OPENSHIFT_RESOURCES_REQUESTS_MEMORY

string

quarkus.openshift.container-name

If set, it will change the name of the container according to the configuration

Environment variable: QUARKUS_OPENSHIFT_CONTAINER_NAME

string

quarkus.openshift.route.expose

If true, the service will be exposed

Environment variable: QUARKUS_OPENSHIFT_ROUTE_EXPOSE

boolean

false

quarkus.openshift.route.host

The host under which the application is going to be exposed

Environment variable: QUARKUS_OPENSHIFT_ROUTE_HOST

string

quarkus.openshift.route.target-port

The target named port. If not provided, it will be deducted from the Service resource ports. Options are: "http" and "https".

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TARGET_PORT

string

http

quarkus.openshift.route.annotations."annotation-name"

Custom annotations to add to exposition (route or ingress) resources

Environment variable: QUARKUS_OPENSHIFT_ROUTE_ANNOTATIONS__ANNOTATION_NAME_

Map<String,String>

quarkus.openshift.route.labels."label-name"

Custom labels to add to exposition (route or ingress) resources

Environment variable: QUARKUS_OPENSHIFT_ROUTE_LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.route.tls.ca-certificate

The cert authority certificate contents.

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TLS_CA_CERTIFICATE

string

quarkus.openshift.route.tls.certificate

The certificate contents.

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TLS_CERTIFICATE

string

quarkus.openshift.route.tls.destination-ca-certificate

The contents of the ca certificate of the final destination.

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TLS_DESTINATION_CA_CERTIFICATE

string

quarkus.openshift.route.tls.insecure-edge-termination-policy

The desired behavior for insecure connections to a route.

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TLS_INSECURE_EDGE_TERMINATION_POLICY

string

quarkus.openshift.route.tls.key

The key file contents.

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TLS_KEY

string

quarkus.openshift.route.tls.termination

The termination type.

Environment variable: QUARKUS_OPENSHIFT_ROUTE_TLS_TERMINATION

string

quarkus.openshift.add-version-to-label-selectors

If true, the 'app.kubernetes.io/version' label will be part of the selectors of Service and DeploymentConfig

Environment variable: QUARKUS_OPENSHIFT_ADD_VERSION_TO_LABEL_SELECTORS

boolean

true

quarkus.openshift.add-name-to-label-selectors

If true, the 'app.kubernetes.io/name' label will be part of the selectors of Service and Deployment

Environment variable: QUARKUS_OPENSHIFT_ADD_NAME_TO_LABEL_SELECTORS

boolean

true

quarkus.openshift.job.parallelism

Specifies the maximum desired number of pods the job should run at any given time.

Environment variable: QUARKUS_OPENSHIFT_JOB_PARALLELISM

int

quarkus.openshift.job.completions

Specifies the desired number of successfully finished pods the job should be run with.

Environment variable: QUARKUS_OPENSHIFT_JOB_COMPLETIONS

int

quarkus.openshift.job.completion-mode

CompletionMode specifies how Pod completions are tracked.

Environment variable: QUARKUS_OPENSHIFT_JOB_COMPLETION_MODE

non-indexed, indexed

non-indexed

quarkus.openshift.job.backoff-limit

Specifies the number of retries before marking this job failed.

Environment variable: QUARKUS_OPENSHIFT_JOB_BACKOFF_LIMIT

int

quarkus.openshift.job.active-deadline-seconds

Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer.

Environment variable: QUARKUS_OPENSHIFT_JOB_ACTIVE_DEADLINE_SECONDS

long

quarkus.openshift.job.ttl-seconds-after-finished

Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted.

Environment variable: QUARKUS_OPENSHIFT_JOB_TTL_SECONDS_AFTER_FINISHED

int

quarkus.openshift.job.suspend

Suspend specifies whether the Job controller should create Pods or not.

Environment variable: QUARKUS_OPENSHIFT_JOB_SUSPEND

boolean

false

quarkus.openshift.job.restart-policy

Restart policy when the job container fails.

Environment variable: QUARKUS_OPENSHIFT_JOB_RESTART_POLICY

on-failure, never

on-failure

quarkus.openshift.cron-job.schedule

The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_SCHEDULE

string

quarkus.openshift.cron-job.concurrency-policy

ConcurrencyPolicy describes how the job will be handled.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_CONCURRENCY_POLICY

allow, forbid, replace

allow

quarkus.openshift.cron-job.starting-deadline-seconds

Deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_STARTING_DEADLINE_SECONDS

long

quarkus.openshift.cron-job.failed-jobs-history-limit

The number of failed finished jobs to retain. The default value is 1.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_FAILED_JOBS_HISTORY_LIMIT

int

quarkus.openshift.cron-job.successful-jobs-history-limit

The number of successful finished jobs to retain. The default value is 3.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_SUCCESSFUL_JOBS_HISTORY_LIMIT

int

quarkus.openshift.cron-job.parallelism

Specifies the maximum desired number of pods the job should run at any given time.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_PARALLELISM

int

quarkus.openshift.cron-job.completions

Specifies the desired number of successfully finished pods the job should be run with.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_COMPLETIONS

int

quarkus.openshift.cron-job.completion-mode

CompletionMode specifies how Pod completions are tracked.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_COMPLETION_MODE

non-indexed, indexed

non-indexed

quarkus.openshift.cron-job.backoff-limit

Specifies the number of retries before marking this job failed.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_BACKOFF_LIMIT

int

quarkus.openshift.cron-job.active-deadline-seconds

Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_ACTIVE_DEADLINE_SECONDS

long

quarkus.openshift.cron-job.ttl-seconds-after-finished

Limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_TTL_SECONDS_AFTER_FINISHED

int

quarkus.openshift.cron-job.suspend

Suspend specifies whether the Job controller should create Pods or not.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_SUSPEND

boolean

false

quarkus.openshift.cron-job.restart-policy

Restart policy when the job container fails.

Environment variable: QUARKUS_OPENSHIFT_CRON_JOB_RESTART_POLICY

on-failure, never

on-failure

quarkus.openshift.rbac.roles."roles".name

The name of the role.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__NAME

string

quarkus.openshift.rbac.roles."roles".namespace

The namespace of the role.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__NAMESPACE

string

quarkus.openshift.rbac.roles."roles".labels."label-name"

Labels to add into the Role resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".api-groups

API groups of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS

list of string

quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".non-resource-urls

Non resource URLs of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS

list of string

quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".resource-names

Resource names of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES

list of string

quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".resources

Resources of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCES

list of string

quarkus.openshift.rbac.roles."roles".policy-rules."policy-rules".verbs

Verbs of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__VERBS

list of string

quarkus.openshift.rbac.cluster-roles."cluster-roles".name

The name of the cluster role.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__NAME

string

quarkus.openshift.rbac.cluster-roles."cluster-roles".labels."label-name"

Labels to add into the ClusterRole resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".api-groups

API groups of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS

list of string

quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".non-resource-urls

Non resource URLs of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS

list of string

quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resource-names

Resource names of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES

list of string

quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resources

Resources of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCES

list of string

quarkus.openshift.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".verbs

Verbs of the policy rule.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__VERBS

list of string

quarkus.openshift.rbac.service-accounts."service-accounts".name

The name of the service account.

Environment variable: QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAME

string

quarkus.openshift.rbac.service-accounts."service-accounts".namespace

The namespace of the service account.

Environment variable: QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAMESPACE

string

quarkus.openshift.rbac.service-accounts."service-accounts".labels."label-name"

Labels of the service account.

Environment variable: QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.rbac.service-accounts."service-accounts".use-as-default

If true, this service account will be used in the generated Deployment resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__USE_AS_DEFAULT

boolean

quarkus.openshift.rbac.role-bindings."role-bindings".name

Name of the RoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__NAME

string

quarkus.openshift.rbac.role-bindings."role-bindings".labels."label-name"

Labels to add into the RoleBinding resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.rbac.role-bindings."role-bindings".role-name

The name of the Role resource to use by the RoleRef element in the generated Role Binding resource. By default, it’s "view" role name.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__ROLE_NAME

string

quarkus.openshift.rbac.role-bindings."role-bindings".cluster-wide

If the Role sets in the role-name property is cluster wide or not.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__CLUSTER_WIDE

boolean

quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".name

The "name" resource to use by the Subject element in the generated Role Binding resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME

string

quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".kind

The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND

string

ServiceAccount

quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".api-group

The "apiGroup" resource that matches with the "kind" property. By default, it’s empty.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP

string

quarkus.openshift.rbac.role-bindings."role-bindings".subjects."subjects".namespace

The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources.

Environment variable: QUARKUS_OPENSHIFT_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE

string

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".name

Name of the ClusterRoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__NAME

string

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".labels."label-name"

Labels to add into the RoleBinding resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".role-name

The name of the ClusterRole resource to use by the RoleRef element in the generated ClusterRoleBinding resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__ROLE_NAME

string

required

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".name

The "name" resource to use by the Subject element in the generated Role Binding resource.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME

string

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".kind

The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND

string

ServiceAccount

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".api-group

The "apiGroup" resource that matches with the "kind" property. By default, it’s empty.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP

string

quarkus.openshift.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".namespace

The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources.

Environment variable: QUARKUS_OPENSHIFT_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE

string

quarkus.openshift.env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_OPENSHIFT_ENV_SECRETS

list of string

quarkus.openshift.env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_OPENSHIFT_ENV_CONFIGMAPS

list of string

quarkus.openshift.env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_OPENSHIFT_ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.openshift.env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_OPENSHIFT_ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.openshift.env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_OPENSHIFT_ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.openshift.env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_OPENSHIFT_ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.openshift.env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_OPENSHIFT_ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.openshift.env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_OPENSHIFT_ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.openshift.env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_OPENSHIFT_ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.openshift.app-secret

If set, the secret will mounted to the application container and its contents will be used for application configuration.

Environment variable: QUARKUS_OPENSHIFT_APP_SECRET

string

quarkus.openshift.app-config-map

If set, the config amp will be mounted to the application container and its contents will be used for application configuration.

Environment variable: QUARKUS_OPENSHIFT_APP_CONFIG_MAP

string

quarkus.openshift.security-context.se-linux-options.level

The SELinux level label that applies to the container.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_LEVEL

string

quarkus.openshift.security-context.se-linux-options.role

The SELinux role label that applies to the container.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_ROLE

string

quarkus.openshift.security-context.se-linux-options.type

The SELinux type label that applies to the container.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_TYPE

string

quarkus.openshift.security-context.se-linux-options.user

The SELinux user label that applies to the container.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SE_LINUX_OPTIONS_USER

string

quarkus.openshift.security-context.windows-options.gmsa-credential-spec-name

The name of the GMSA credential spec to use.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC_NAME

string

quarkus.openshift.security-context.windows-options.gmsa-credential-spec

GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC

string

quarkus.openshift.security-context.windows-options.run-as-user-name

The UserName in Windows to run the entrypoint of the container process.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_RUN_AS_USER_NAME

string

quarkus.openshift.security-context.windows-options.host-process

HostProcess determines if a container should be run as a 'Host Process' container.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_WINDOWS_OPTIONS_HOST_PROCESS

boolean

quarkus.openshift.security-context.run-as-user

The UID to run the entrypoint of the container process.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_RUN_AS_USER

long

quarkus.openshift.security-context.run-as-group

The GID to run the entrypoint of the container process.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_RUN_AS_GROUP

long

quarkus.openshift.security-context.run-as-non-root

Indicates that the container must run as a non-root user.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_RUN_AS_NON_ROOT

boolean

quarkus.openshift.security-context.supplemental-groups

A list of groups applied to the first process run in each container, in addition to the container’s primary GID. If unspecified, no groups will be added to any container.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SUPPLEMENTAL_GROUPS

list of long

quarkus.openshift.security-context.fs-group

A special supplemental group that applies to all containers in a pod.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_FS_GROUP

long

quarkus.openshift.security-context.sysctls."sysctl-name"

Sysctls hold a list of namespaced sysctls used for the pod.

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_SYSCTLS__SYSCTL_NAME_

Map<String,String>

quarkus.openshift.security-context.fs-group-change-policy

It holds policies that will be used for applying fsGroup to a volume when volume is mounted. Values: OnRootMismatch, Always

Environment variable: QUARKUS_OPENSHIFT_SECURITY_CONTEXT_FS_GROUP_CHANGE_POLICY

quarkus.openshift.remote-debug.enabled

If true, the debug mode in pods will be enabled.

Environment variable: QUARKUS_OPENSHIFT_REMOTE_DEBUG_ENABLED

boolean

false

quarkus.openshift.remote-debug.transport

The transport to use.

Environment variable: QUARKUS_OPENSHIFT_REMOTE_DEBUG_TRANSPORT

string

dt_socket

quarkus.openshift.remote-debug.suspend

Environment variable: QUARKUS_OPENSHIFT_REMOTE_DEBUG_SUSPEND

string

n

quarkus.openshift.remote-debug.address-port

It specifies the address at which the debug socket will listen.

Environment variable: QUARKUS_OPENSHIFT_REMOTE_DEBUG_ADDRESS_PORT

int

5005

quarkus.openshift.deploy

If set to true, Quarkus will attempt to deploy the application to the target Openshift cluster

Environment variable: QUARKUS_OPENSHIFT_DEPLOY

boolean

false

quarkus.openshift.deploy-strategy

If deploy is enabled, it will follow this strategy to update the resources to the target OpenShift cluster.

Environment variable: QUARKUS_OPENSHIFT_DEPLOY_STRATEGY

create-or-update, create, replace, server-side-apply

create-or-update

quarkus.openshift.init-tasks."init-tasks".enabled

If true, the init task will be generated. Otherwise, the init task resource generation will be skipped.

Environment variable: QUARKUS_OPENSHIFT_INIT_TASKS__INIT_TASKS__ENABLED

boolean

true

quarkus.openshift.init-tasks."init-tasks".wait-for-container.image

The init task image to use by the init-container.

Environment variable: QUARKUS_OPENSHIFT_INIT_TASKS__INIT_TASKS__WAIT_FOR_CONTAINER_IMAGE

string

groundnuty/k8s-wait-for:no-root-v1.7

quarkus.openshift.init-task-defaults.enabled

If true, the init task will be generated. Otherwise, the init task resource generation will be skipped.

Environment variable: QUARKUS_OPENSHIFT_INIT_TASK_DEFAULTS_ENABLED

boolean

true

quarkus.openshift.init-task-defaults.wait-for-container.image

The init task image to use by the init-container.

Environment variable: QUARKUS_OPENSHIFT_INIT_TASK_DEFAULTS_WAIT_FOR_CONTAINER_IMAGE

string

groundnuty/k8s-wait-for:no-root-v1.7

quarkus.openshift.idempotent

Switch used to control whether non-idempotent fields are included in generated kubernetes resources to improve git-ops compatibility

Environment variable: QUARKUS_OPENSHIFT_IDEMPOTENT

boolean

false

quarkus.openshift.vcs-uri.enabled

Whether the vcs-uri annotation should be added to the generated configuration.

Environment variable: QUARKUS_OPENSHIFT_VCS_URI_ENABLED

boolean

true

quarkus.openshift.vcs-uri.override

Optional override of the vcs-uri annotation.

Environment variable: QUARKUS_OPENSHIFT_VCS_URI_OVERRIDE

string

Knative

To enable the generation of Knative resources, you need to include Knative in the target platforms:

quarkus.kubernetes.deployment-target=knative

Following the execution of ./mvnw package you will notice amongst the other files that are created, two files named knative.json and knative.yml in the target/kubernetes/ directory.

If you look at either file you will see that it contains a Knative Service.

The full source of the knative.json file looks something like this:

{
  {
    "apiVersion" : "serving.quarkus.knative.dev/v1alpha1",
    "kind" : "Service",
    "metadata" : {
      "annotations": {
       "app.quarkus.io/vcs-uri" : "<some url>",
       "app.quarkus.io/commit-id" : "<some git SHA>"
      },
      "labels" : {
        "app.kubernetes.io/name" : "test-quarkus-app",
        "app.kubernetes.io/version" : "1.0.0-SNAPSHOT"
      },
      "name" : "knative"
    },
    "spec" : {
      "runLatest" : {
        "configuration" : {
          "revisionTemplate" : {
            "spec" : {
              "container" : {
                "image" : "dev.local/yourDockerUsername/test-quarkus-app:1.0.0-SNAPSHOT",
                "imagePullPolicy" : "Always"
              }
            }
          }
        }
      }
    }
  }
}

The generated manifest can be deployed as is to a running cluster, using kubectl:

kubectl apply -f target/kubernetes/knative.json

The generated service can be customized using the following properties:

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	类型	默认
`quarkus.knative.part-of` The name of the group this component belongs too Environment variable: `QUARKUS_KNATIVE_PART_OF` Show more	string
`quarkus.knative.name` The name of the application. This value will be used for naming Kubernetes resources like: - Deployment - Service and so on … Environment variable: `QUARKUS_KNATIVE_NAME` Show more	string
`quarkus.knative.version` The version of the application. Environment variable: `QUARKUS_KNATIVE_VERSION` Show more	string
`quarkus.knative.namespace` The namespace the generated resources should belong to. If not value is set, then the 'namespace' field will not be added to the 'metadata' section of the generated manifests. This in turn means that when the manifests are applied to a cluster, the namespace will be resolved from the current Kubernetes context (see https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#context for more details). Environment variable: `QUARKUS_KNATIVE_NAMESPACE` Show more	string
`quarkus.knative.labels."label-name"` Custom labels to add to all resources Environment variable: `QUARKUS_KNATIVE_LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.knative.annotations."annotation-name"` Custom annotations to add to all resources Environment variable: `QUARKUS_KNATIVE_ANNOTATIONS__ANNOTATION_NAME_` Show more	Map<String,String>
`quarkus.knative.add-build-timestamp` Whether to add the build timestamp to the Kubernetes annotations This is a very useful way to have manifests of successive builds of the same application differ - thus ensuring that Kubernetes will apply the updated resources Environment variable: `QUARKUS_KNATIVE_ADD_BUILD_TIMESTAMP` Show more	boolean	`true`
`quarkus.knative.working-dir` Working directory Environment variable: `QUARKUS_KNATIVE_WORKING_DIR` Show more	string
`quarkus.knative.command` The commands Environment variable: `QUARKUS_KNATIVE_COMMAND` Show more	list of string
`quarkus.knative.arguments` The arguments Environment variable: `QUARKUS_KNATIVE_ARGUMENTS` Show more	list of string
`quarkus.knative.service-account` The service account Environment variable: `QUARKUS_KNATIVE_SERVICE_ACCOUNT` Show more	string
`quarkus.knative.ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_KNATIVE_PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.knative.ports."ports".host-port` The host port. Environment variable: `QUARKUS_KNATIVE_PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.knative.ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_KNATIVE_PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.knative.ports."ports".protocol` The protocol. Environment variable: `QUARKUS_KNATIVE_PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.knative.ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_KNATIVE_PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.knative.ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_KNATIVE_PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.knative.service-type` The type of service that will be generated for the application Environment variable: `QUARKUS_KNATIVE_SERVICE_TYPE` Show more	`cluster-ip`, `node-port`, `load-balancer`, `external-name`	`cluster-ip`
`quarkus.knative.image-pull-policy` Image pull policy Environment variable: `QUARKUS_KNATIVE_IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.knative.image-pull-secrets` The image pull secret Environment variable: `QUARKUS_KNATIVE_IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.knative.generate-image-pull-secret` Enable generation of image pull secret, when the container image username and password are provided. Environment variable: `QUARKUS_KNATIVE_GENERATE_IMAGE_PULL_SECRET` Show more	boolean	`false`
`quarkus.knative.liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.startup-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.startup-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.startup-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.startup-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.startup-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.startup-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.startup-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.startup-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.startup-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.startup-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.startup-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.startup-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.startup-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_STARTUP_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.prometheus.annotations` When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary. Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_ANNOTATIONS` Show more	boolean	`true`
`quarkus.knative.prometheus.generate-service-monitor` When true (the default), emit a set of annotations to identify services that should be scraped by prometheus for metrics. In configurations that use the Prometheus operator with ServiceMonitor, annotations may not be necessary. Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_GENERATE_SERVICE_MONITOR` Show more	boolean	`true`
`quarkus.knative.prometheus.prefix` Define the annotation prefix used for scrape values, this value will be used as the base for other annotation name defaults. Altering the base for generated annotations can make it easier to define re-labeling rules and avoid unexpected knock-on effects. The default value is `prometheus.io` See Prometheus example: https://github.com/prometheus/prometheus/blob/main/documentation/examples/prometheus-kubernetes.yml Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_PREFIX` Show more	string	`prometheus.io`
`quarkus.knative.prometheus.scrape` Define the annotation used to indicate services that should be scraped. By default, `/scrape` will be appended to the defined prefix. Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_SCRAPE` Show more	string
`quarkus.knative.prometheus.path` Define the annotation used to indicate the path to scrape. By default, `/path` will be appended to the defined prefix. Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_PATH` Show more	string
`quarkus.knative.prometheus.port` Define the annotation used to indicate the port to scrape. By default, `/port` will be appended to the defined prefix. Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_PORT` Show more	string
`quarkus.knative.prometheus.scheme` Define the annotation used to indicate the scheme to use for scraping By default, `/scheme` will be appended to the defined prefix. Environment variable: `QUARKUS_KNATIVE_PROMETHEUS_SCHEME` Show more	string
`quarkus.knative.mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_KNATIVE_MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.knative.mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_KNATIVE_MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.knative.mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_KNATIVE_MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.knative.mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_KNATIVE_MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.knative.secret-volumes."secret-volumes".secret-name` The name of the secret to mount. Environment variable: `QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__SECRET_NAME` Show more	string	required
`quarkus.knative.secret-volumes."secret-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.knative.secret-volumes."secret-volumes".items."items".path` The path where the file will be mounted. Environment variable: `QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__PATH` Show more	string	required
`quarkus.knative.secret-volumes."secret-volumes".items."items".mode` It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used. Environment variable: `QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__MODE` Show more	int	`-1`
`quarkus.knative.secret-volumes."secret-volumes".optional` Optional Environment variable: `QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.knative.config-map-volumes."config-map-volumes".config-map-name` The name of the ConfigMap to mount. Environment variable: `QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__CONFIG_MAP_NAME` Show more	string	required
`quarkus.knative.config-map-volumes."config-map-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.knative.config-map-volumes."config-map-volumes".items."items".path` The path where the file will be mounted. Environment variable: `QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__PATH` Show more	string	required
`quarkus.knative.config-map-volumes."config-map-volumes".items."items".mode` It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used. Environment variable: `QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__MODE` Show more	int	`-1`
`quarkus.knative.config-map-volumes."config-map-volumes".optional` Optional Environment variable: `QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.knative.empty-dir-volumes` EmptyDir volumes Environment variable: `QUARKUS_KNATIVE_EMPTY_DIR_VOLUMES` Show more	list of string
`quarkus.knative.git-repo-volumes."git-repo-volumes".repository` Git repository URL. Environment variable: `QUARKUS_KNATIVE_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REPOSITORY` Show more	string	required
`quarkus.knative.git-repo-volumes."git-repo-volumes".directory` The directory of the repository to mount. Environment variable: `QUARKUS_KNATIVE_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__DIRECTORY` Show more	string
`quarkus.knative.git-repo-volumes."git-repo-volumes".revision` The commit hash to use. Environment variable: `QUARKUS_KNATIVE_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REVISION` Show more	string
`quarkus.knative.pvc-volumes."pvc-volumes".claim-name` The name of the claim to mount. Environment variable: `QUARKUS_KNATIVE_PVC_VOLUMES__PVC_VOLUMES__CLAIM_NAME` Show more	string	required
`quarkus.knative.pvc-volumes."pvc-volumes".default-mode` Default mode. When specifying an octal number, leading zero must be present. Environment variable: `QUARKUS_KNATIVE_PVC_VOLUMES__PVC_VOLUMES__DEFAULT_MODE` Show more	string	`0600`
`quarkus.knative.pvc-volumes."pvc-volumes".optional` Optional Environment variable: `QUARKUS_KNATIVE_PVC_VOLUMES__PVC_VOLUMES__OPTIONAL` Show more	boolean	`false`
`quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".volume-id` The name of the disk to mount. Environment variable: `QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__VOLUME_ID` Show more	string	required
`quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".partition` The partition. Environment variable: `QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__PARTITION` Show more	int
`quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".fs-type` Filesystem type. Environment variable: `QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__FS_TYPE` Show more	string	`ext4`
`quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.knative.azure-file-volumes."azure-file-volumes".share-name` The share name. Environment variable: `QUARKUS_KNATIVE_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SHARE_NAME` Show more	string	required
`quarkus.knative.azure-file-volumes."azure-file-volumes".secret-name` The secret name. Environment variable: `QUARKUS_KNATIVE_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SECRET_NAME` Show more	string	required
`quarkus.knative.azure-file-volumes."azure-file-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_KNATIVE_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.knative.azure-disk-volumes."azure-disk-volumes".disk-name` The name of the disk to mount. Environment variable: `QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_NAME` Show more	string	required
`quarkus.knative.azure-disk-volumes."azure-disk-volumes".disk-uri` The URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed Environment variable: `QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_URI` Show more	string	required
`quarkus.knative.azure-disk-volumes."azure-disk-volumes".kind` Kind of disk. Environment variable: `QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__KIND` Show more	`managed`, `shared`	`managed`
`quarkus.knative.azure-disk-volumes."azure-disk-volumes".caching-mode` Disk caching mode. Environment variable: `QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__CACHING_MODE` Show more	`read-write`, `read-only`, `none`	`read-write`
`quarkus.knative.azure-disk-volumes."azure-disk-volumes".fs-type` File system type. Environment variable: `QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__FS_TYPE` Show more	string	`ext4`
`quarkus.knative.azure-disk-volumes."azure-disk-volumes".read-only` Whether the volumeName is read only or not. Environment variable: `QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__READ_ONLY` Show more	boolean	`false`
`quarkus.knative.container-name` If set, it will change the name of the container according to the configuration Environment variable: `QUARKUS_KNATIVE_CONTAINER_NAME` Show more	string
`quarkus.knative.init-containers."init-containers".image` The container image. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE` Show more	string
`quarkus.knative.init-containers."init-containers".working-dir` Working directory. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__WORKING_DIR` Show more	string
`quarkus.knative.init-containers."init-containers".command` The commands Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__COMMAND` Show more	list of string
`quarkus.knative.init-containers."init-containers".arguments` The arguments Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ARGUMENTS` Show more	list of string
`quarkus.knative.init-containers."init-containers".service-account` The service account. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__SERVICE_ACCOUNT` Show more	string
`quarkus.knative.init-containers."init-containers".host` The host under which the application is going to be exposed. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__HOST` Show more	string
`quarkus.knative.init-containers."init-containers".ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.knative.init-containers."init-containers".ports."ports".host-port` The host port. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.knative.init-containers."init-containers".ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.knative.init-containers."init-containers".ports."ports".protocol` The protocol. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.knative.init-containers."init-containers".ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.knative.init-containers."init-containers".ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.knative.init-containers."init-containers".image-pull-policy` Image pull policy. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.knative.init-containers."init-containers".image-pull-secrets` The image pull secret Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.knative.init-containers."init-containers".liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.init-containers."init-containers".liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.init-containers."init-containers".liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.init-containers."init-containers".liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.init-containers."init-containers".liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.init-containers."init-containers".liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.init-containers."init-containers".liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.init-containers."init-containers".liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.init-containers."init-containers".liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.init-containers."init-containers".liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.init-containers."init-containers".liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.init-containers."init-containers".liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.init-containers."init-containers".liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.init-containers."init-containers".readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.init-containers."init-containers".readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.init-containers."init-containers".readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.init-containers."init-containers".readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.init-containers."init-containers".readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.init-containers."init-containers".readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.init-containers."init-containers".readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.init-containers."init-containers".readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.init-containers."init-containers".readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.init-containers."init-containers".readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.init-containers."init-containers".readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.init-containers."init-containers".readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.init-containers."init-containers".readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.init-containers."init-containers".mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.knative.init-containers."init-containers".mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.knative.init-containers."init-containers".mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.knative.init-containers."init-containers".mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.knative.init-containers."init-containers".resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_CPU` Show more	string
`quarkus.knative.init-containers."init-containers".resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.knative.init-containers."init-containers".resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.knative.init-containers."init-containers".resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.knative.init-containers."init-containers".env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_SECRETS` Show more	list of string
`quarkus.knative.init-containers."init-containers".env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_CONFIGMAPS` Show more	list of string
`quarkus.knative.init-containers."init-containers".env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.knative.init-containers."init-containers".env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.knative.init-containers."init-containers".env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.knative.init-containers."init-containers".env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.knative.init-containers."init-containers".env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.knative.init-containers."init-containers".env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.knative.init-containers."init-containers".env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.knative.containers."containers".image` The container image. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__IMAGE` Show more	string
`quarkus.knative.containers."containers".working-dir` Working directory. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__WORKING_DIR` Show more	string
`quarkus.knative.containers."containers".command` The commands Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__COMMAND` Show more	list of string
`quarkus.knative.containers."containers".arguments` The arguments Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ARGUMENTS` Show more	list of string
`quarkus.knative.containers."containers".service-account` The service account. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__SERVICE_ACCOUNT` Show more	string
`quarkus.knative.containers."containers".host` The host under which the application is going to be exposed. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__HOST` Show more	string
`quarkus.knative.containers."containers".ports."ports".container-port` The port number. Refers to the container port. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__CONTAINER_PORT` Show more	int
`quarkus.knative.containers."containers".ports."ports".host-port` The host port. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__HOST_PORT` Show more	int
`quarkus.knative.containers."containers".ports."ports".path` The application path (refers to web application path). Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__PATH` Show more	string	`/`
`quarkus.knative.containers."containers".ports."ports".protocol` The protocol. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__PROTOCOL` Show more	`tcp`, `udp`, `sctp`, `http`, `proxy`	`tcp`
`quarkus.knative.containers."containers".ports."ports".node-port` The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__NODE_PORT` Show more	int
`quarkus.knative.containers."containers".ports."ports".tls` If enabled, the port will be configured to use the schema HTTPS. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__TLS` Show more	boolean	`false`
`quarkus.knative.containers."containers".image-pull-policy` Image pull policy. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__IMAGE_PULL_POLICY` Show more	`always`, `if-not-present`, `never`	`always`
`quarkus.knative.containers."containers".image-pull-secrets` The image pull secret Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__IMAGE_PULL_SECRETS` Show more	list of string
`quarkus.knative.containers."containers".liveness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.containers."containers".liveness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.containers."containers".liveness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.containers."containers".liveness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.containers."containers".liveness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.containers."containers".liveness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.containers."containers".liveness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.containers."containers".liveness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.containers."containers".liveness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.containers."containers".liveness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.containers."containers".liveness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.containers."containers".liveness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.containers."containers".liveness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.containers."containers".readiness-probe.http-action-port` The port number to use when configuring the `http get` action. If not configured, the port corresponding to the `httpActionPortName` will be used. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT` Show more	int
`quarkus.knative.containers."containers".readiness-probe.http-action-port-name` The port name for selecting the port of the `HTTP get` action. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME` Show more	string
`quarkus.knative.containers."containers".readiness-probe.http-action-path` The http path to use for the probe. For this to work, the container port also needs to be set. Assuming the container port has been set (as per above comment), if execAction or tcpSocketAction are not set, an HTTP probe will be used automatically even if no path is set (which will result in the root path being used). If Smallrye Health is used, the path will automatically be set according to the health check path. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH` Show more	string
`quarkus.knative.containers."containers".readiness-probe.http-action-scheme` The scheme of the `HTTP get` action. Can be either "HTTP" or "HTTPS". Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME` Show more	string
`quarkus.knative.containers."containers".readiness-probe.exec-action` The command to use for the probe. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_EXEC_ACTION` Show more	string
`quarkus.knative.containers."containers".readiness-probe.tcp-socket-action` The tcp socket to use for the probe (the format is host:port). Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION` Show more	string
`quarkus.knative.containers."containers".readiness-probe.grpc-action` The gRPC port to use for the probe (the format is either port or port:service). Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_GRPC_ACTION` Show more	string
`quarkus.knative.containers."containers".readiness-probe.grpc-action-enabled` If enabled and `grpc-action` is not provided, it will use the generated service name and the gRPC port. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED` Show more	boolean	`false`
`quarkus.knative.containers."containers".readiness-probe.initial-delay` The amount of time to wait before starting to probe. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_INITIAL_DELAY` Show more	Duration	`5S`
`quarkus.knative.containers."containers".readiness-probe.period` The period in which the action should be called. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_PERIOD` Show more	Duration	`10S`
`quarkus.knative.containers."containers".readiness-probe.timeout` The amount of time to wait for each action. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_TIMEOUT` Show more	Duration	`10S`
`quarkus.knative.containers."containers".readiness-probe.success-threshold` The success threshold to use. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD` Show more	int	`1`
`quarkus.knative.containers."containers".readiness-probe.failure-threshold` The failure threshold to use. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD` Show more	int	`3`
`quarkus.knative.containers."containers".mounts."mounts".name` The name of the volumeName to mount. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__NAME` Show more	string
`quarkus.knative.containers."containers".mounts."mounts".path` The path to mount. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__PATH` Show more	string
`quarkus.knative.containers."containers".mounts."mounts".sub-path` Path within the volumeName from which the container’s volumeName should be mounted. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__SUB_PATH` Show more	string
`quarkus.knative.containers."containers".mounts."mounts".read-only` ReadOnly Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__READ_ONLY` Show more	boolean	`false`
`quarkus.knative.containers."containers".resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_LIMITS_CPU` Show more	string
`quarkus.knative.containers."containers".resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.knative.containers."containers".resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.knative.containers."containers".resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.knative.containers."containers".env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_SECRETS` Show more	list of string
`quarkus.knative.containers."containers".env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_CONFIGMAPS` Show more	list of string
`quarkus.knative.containers."containers".env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.knative.containers."containers".env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.knative.containers."containers".env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.knative.containers."containers".env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.knative.containers."containers".env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.knative.containers."containers".env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.knative.containers."containers".env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.knative.host-aliases."host-aliases".ip` The ip address Environment variable: `QUARKUS_KNATIVE_HOST_ALIASES__HOST_ALIASES__IP` Show more	string
`quarkus.knative.host-aliases."host-aliases".hostnames` The hostnames to resolve to the ip Environment variable: `QUARKUS_KNATIVE_HOST_ALIASES__HOST_ALIASES__HOSTNAMES` Show more	list of string
`quarkus.knative.resources.limits.cpu` CPU Requirements Environment variable: `QUARKUS_KNATIVE_RESOURCES_LIMITS_CPU` Show more	string
`quarkus.knative.resources.limits.memory` Memory Requirements Environment variable: `QUARKUS_KNATIVE_RESOURCES_LIMITS_MEMORY` Show more	string
`quarkus.knative.resources.requests.cpu` CPU Requirements Environment variable: `QUARKUS_KNATIVE_RESOURCES_REQUESTS_CPU` Show more	string
`quarkus.knative.resources.requests.memory` Memory Requirements Environment variable: `QUARKUS_KNATIVE_RESOURCES_REQUESTS_MEMORY` Show more	string
`quarkus.knative.rbac.roles."roles".name` The name of the role. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__NAME` Show more	string
`quarkus.knative.rbac.roles."roles".namespace` The namespace of the role. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__NAMESPACE` Show more	string
`quarkus.knative.rbac.roles."roles".labels."label-name"` Labels to add into the Role resource. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".api-groups` API groups of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS` Show more	list of string
`quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".non-resource-urls` Non resource URLs of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS` Show more	list of string
`quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".resource-names` Resource names of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES` Show more	list of string
`quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".resources` Resources of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCES` Show more	list of string
`quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".verbs` Verbs of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__VERBS` Show more	list of string
`quarkus.knative.rbac.cluster-roles."cluster-roles".name` The name of the cluster role. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__NAME` Show more	string
`quarkus.knative.rbac.cluster-roles."cluster-roles".labels."label-name"` Labels to add into the ClusterRole resource. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".api-groups` API groups of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS` Show more	list of string
`quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".non-resource-urls` Non resource URLs of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS` Show more	list of string
`quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resource-names` Resource names of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES` Show more	list of string
`quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resources` Resources of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCES` Show more	list of string
`quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".verbs` Verbs of the policy rule. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__VERBS` Show more	list of string
`quarkus.knative.rbac.service-accounts."service-accounts".name` The name of the service account. Environment variable: `QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAME` Show more	string
`quarkus.knative.rbac.service-accounts."service-accounts".namespace` The namespace of the service account. Environment variable: `QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAMESPACE` Show more	string
`quarkus.knative.rbac.service-accounts."service-accounts".labels."label-name"` Labels of the service account. Environment variable: `QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.knative.rbac.service-accounts."service-accounts".use-as-default` If true, this service account will be used in the generated Deployment resource. Environment variable: `QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__USE_AS_DEFAULT` Show more	boolean
`quarkus.knative.rbac.role-bindings."role-bindings".name` Name of the RoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__NAME` Show more	string
`quarkus.knative.rbac.role-bindings."role-bindings".labels."label-name"` Labels to add into the RoleBinding resource. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.knative.rbac.role-bindings."role-bindings".role-name` The name of the Role resource to use by the RoleRef element in the generated Role Binding resource. By default, it’s "view" role name. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__ROLE_NAME` Show more	string
`quarkus.knative.rbac.role-bindings."role-bindings".cluster-wide` If the Role sets in the `role-name` property is cluster wide or not. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__CLUSTER_WIDE` Show more	boolean
`quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".name` The "name" resource to use by the Subject element in the generated Role Binding resource. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME` Show more	string
`quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".kind` The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND` Show more	string	`ServiceAccount`
`quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".api-group` The "apiGroup" resource that matches with the "kind" property. By default, it’s empty. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP` Show more	string
`quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".namespace` The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources. Environment variable: `QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE` Show more	string
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".name` Name of the ClusterRoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__NAME` Show more	string
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".labels."label-name"` Labels to add into the RoleBinding resource. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__LABELS__LABEL_NAME_` Show more	Map<String,String>
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".role-name` The name of the ClusterRole resource to use by the RoleRef element in the generated ClusterRoleBinding resource. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__ROLE_NAME` Show more	string	required
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".name` The "name" resource to use by the Subject element in the generated Role Binding resource. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME` Show more	string
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".kind` The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND` Show more	string	`ServiceAccount`
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".api-group` The "apiGroup" resource that matches with the "kind" property. By default, it’s empty. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP` Show more	string
`quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".namespace` The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources. Environment variable: `QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE` Show more	string
`quarkus.knative.add-version-to-label-selectors` If true, the 'app.kubernetes.io/version' label will be part of the selectors of Service and Deployment Environment variable: `QUARKUS_KNATIVE_ADD_VERSION_TO_LABEL_SELECTORS` Show more	boolean	`true`
`quarkus.knative.add-name-to-label-selectors` If true, the 'app.kubernetes.io/name' label will be part of the selectors of Service and Deployment Environment variable: `QUARKUS_KNATIVE_ADD_NAME_TO_LABEL_SELECTORS` Show more	boolean	`true`
`quarkus.knative.idempotent` Switch used to control whether non-idempotent fields are included in generated kubernetes resources to improve git-ops compatibility Environment variable: `QUARKUS_KNATIVE_IDEMPOTENT` Show more	boolean	`false`
`quarkus.knative.vcs-uri.enabled` Whether the vcs-uri annotation should be added to the generated configuration. Environment variable: `QUARKUS_KNATIVE_VCS_URI_ENABLED` Show more	boolean	`true`
`quarkus.knative.vcs-uri.override` Optional override of the vcs-uri annotation. Environment variable: `QUARKUS_KNATIVE_VCS_URI_OVERRIDE` Show more	string
`quarkus.knative.env.secrets` The optional list of Secret names to load environment variables from. Environment variable: `QUARKUS_KNATIVE_ENV_SECRETS` Show more	list of string
`quarkus.knative.env.configmaps` The optional list of ConfigMap names to load environment variables from. Environment variable: `QUARKUS_KNATIVE_ENV_CONFIGMAPS` Show more	list of string
`quarkus.knative.env.fields."environment-variable-name"` The map associating environment variable names to their associated field references they take their value from. Environment variable: `QUARKUS_KNATIVE_ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_` Show more	Map<String,String>
`quarkus.knative.env.vars."vars"` The map associating environment name to its associated value. Environment variable: `QUARKUS_KNATIVE_ENV_VARS__VARS_` Show more	Map<String,Optional<String>>
`quarkus.knative.env.mapping."mapping".from-secret` The optional name of the Secret from which a value is to be extracted. Mutually exclusive with `from-configmap`. Environment variable: `QUARKUS_KNATIVE_ENV_MAPPING__MAPPING__FROM_SECRET` Show more	string
`quarkus.knative.env.mapping."mapping".from-configmap` The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with `from-secret`. Environment variable: `QUARKUS_KNATIVE_ENV_MAPPING__MAPPING__FROM_CONFIGMAP` Show more	string
`quarkus.knative.env.mapping."mapping".with-key` The key identifying the field from which the value is extracted. Environment variable: `QUARKUS_KNATIVE_ENV_MAPPING__MAPPING__WITH_KEY` Show more	string	required
`quarkus.knative.env.using-prefix."prefixes".for-secret` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KNATIVE_ENV_USING_PREFIX__PREFIXES__FOR_SECRET` Show more	string
`quarkus.knative.env.using-prefix."prefixes".for-configmap` The optional prefix to use when adding the environment variable to the container. Environment variable: `QUARKUS_KNATIVE_ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP` Show more	string
`quarkus.knative.cluster-local` Whether this service is cluster-local. Cluster local services are not exposed to the outside world. More information in this link. Environment variable: `QUARKUS_KNATIVE_CLUSTER_LOCAL` Show more	boolean	`false`
`quarkus.knative.min-scale` This value controls the minimum number of replicas each revision should have. Knative will attempt to never have less than this number of replicas at any point in time. Environment variable: `QUARKUS_KNATIVE_MIN_SCALE` Show more	int
`quarkus.knative.max-scale` This value controls the maximum number of replicas each revision should have. Knative will attempt to never have more than this number of replicas running, or in the process of being created, at any point in time. Environment variable: `QUARKUS_KNATIVE_MAX_SCALE` Show more	int
`quarkus.knative.scale-to-zero-enabled` The scale-to-zero values control whether Knative allows revisions to scale down to zero, or stops at “1”. Environment variable: `QUARKUS_KNATIVE_SCALE_TO_ZERO_ENABLED` Show more	boolean	`true`
`quarkus.knative.revision-auto-scaling.auto-scaler-class` The Autoscaler class. Knative Serving comes with its own autoscaler, the KPA (Knative Pod Autoscaler) but can also be configured to use Kubernetes’ HPA (Horizontal Pod Autoscaler) or even a custom third-party autoscaler. Possible values (kpa, hpa, default: kpa). Environment variable: `QUARKUS_KNATIVE_REVISION_AUTO_SCALING_AUTO_SCALER_CLASS` Show more	`kpa`Kubernetes Pod Autoscaler, `hpa`Horizontal Pod Autoscaler
`quarkus.knative.revision-auto-scaling.metric` The autoscaling metric to use. Possible values (concurrency, rps, cpu). Environment variable: `QUARKUS_KNATIVE_REVISION_AUTO_SCALING_METRIC` Show more	`concurrency`Concurrency, `rps`Requests per second, `cpu`CPU
`quarkus.knative.revision-auto-scaling.target` The autoscaling target. Environment variable: `QUARKUS_KNATIVE_REVISION_AUTO_SCALING_TARGET` Show more	int
`quarkus.knative.revision-auto-scaling.container-concurrency` The exact amount of requests allowed to the replica at a time. Its default value is “0”, which means an unlimited number of requests are allowed to flow into the replica. Environment variable: `QUARKUS_KNATIVE_REVISION_AUTO_SCALING_CONTAINER_CONCURRENCY` Show more	int
`quarkus.knative.revision-auto-scaling.target-utilization-percentage` This value specifies a percentage of the target to actually be targeted by the autoscaler. Environment variable: `QUARKUS_KNATIVE_REVISION_AUTO_SCALING_TARGET_UTILIZATION_PERCENTAGE` Show more	int
`quarkus.knative.global-auto-scaling.auto-scaler-class` The Autoscaler class. Knative Serving comes with its own autoscaler, the KPA (Knative Pod Autoscaler) but can also be configured to use Kubernetes’ HPA (Horizontal Pod Autoscaler) or even a custom third-party autoscaler. Possible values (kpa, hpa, default: kpa). Environment variable: `QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_AUTO_SCALER_CLASS` Show more	`kpa`Kubernetes Pod Autoscaler, `hpa`Horizontal Pod Autoscaler
`quarkus.knative.global-auto-scaling.container-concurrency` The exact amount of requests allowed to the replica at a time. Its default value is “0”, which means an unlimited number of requests are allowed to flow Integer>o the replica. Environment variable: `QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_CONTAINER_CONCURRENCY` Show more	int
`quarkus.knative.global-auto-scaling.target-utilization-percentage` This value specifies a percentage of the target to actually be targeted by the autoscaler. Environment variable: `QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_TARGET_UTILIZATION_PERCENTAGE` Show more	int
`quarkus.knative.global-auto-scaling.requests-per-second` The requests per second per replica. Environment variable: `QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_REQUESTS_PER_SECOND` Show more	int
`quarkus.knative.revision-name` The name of the revision. Environment variable: `QUARKUS_KNATIVE_REVISION_NAME` Show more	string
`quarkus.knative.traffic."traffic".tag` Tag is optionally used to expose a dedicated url for referencing this target exclusively. Environment variable: `QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__TAG` Show more	string
`quarkus.knative.traffic."traffic".revision-name` RevisionName of a specific revision to which to send this portion of traffic. Environment variable: `QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__REVISION_NAME` Show more	string
`quarkus.knative.traffic."traffic".latest-revision` LatestRevision may be optionally provided to indicate that the latest ready Revision of the Configuration should be used for this traffic target. When provided LatestRevision must be true if RevisionName is empty. Environment variable: `QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__LATEST_REVISION` Show more	boolean	`false`
`quarkus.knative.traffic."traffic".percent` Percent indicates that percentage based routing should be used and the value indicates the percent of traffic that is to be routed to this Revision or Configuration. `0` (zero) mean no traffic, `100` means all traffic. Environment variable: `QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__PERCENT` Show more	long	`100`
`quarkus.knative.app-secret` If set, the secret will mounted to the application container and its contents will be used for application configuration. Environment variable: `QUARKUS_KNATIVE_APP_SECRET` Show more	string
`quarkus.knative.app-config-map` If set, the config map will be mounted to the application container and its contents will be used for application configuration. Environment variable: `QUARKUS_KNATIVE_APP_CONFIG_MAP` Show more	string
`quarkus.knative.security-context.se-linux-options.level` The SELinux level label that applies to the container. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_LEVEL` Show more	string
`quarkus.knative.security-context.se-linux-options.role` The SELinux role label that applies to the container. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_ROLE` Show more	string
`quarkus.knative.security-context.se-linux-options.type` The SELinux type label that applies to the container. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_TYPE` Show more	string
`quarkus.knative.security-context.se-linux-options.user` The SELinux user label that applies to the container. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_USER` Show more	string
`quarkus.knative.security-context.windows-options.gmsa-credential-spec-name` The name of the GMSA credential spec to use. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC_NAME` Show more	string
`quarkus.knative.security-context.windows-options.gmsa-credential-spec` GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC` Show more	string
`quarkus.knative.security-context.windows-options.run-as-user-name` The UserName in Windows to run the entrypoint of the container process. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_RUN_AS_USER_NAME` Show more	string
`quarkus.knative.security-context.windows-options.host-process` HostProcess determines if a container should be run as a 'Host Process' container. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_HOST_PROCESS` Show more	boolean
`quarkus.knative.security-context.run-as-user` The UID to run the entrypoint of the container process. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_RUN_AS_USER` Show more	long
`quarkus.knative.security-context.run-as-group` The GID to run the entrypoint of the container process. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_RUN_AS_GROUP` Show more	long
`quarkus.knative.security-context.run-as-non-root` Indicates that the container must run as a non-root user. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_RUN_AS_NON_ROOT` Show more	boolean
`quarkus.knative.security-context.supplemental-groups` A list of groups applied to the first process run in each container, in addition to the container’s primary GID. If unspecified, no groups will be added to any container. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_SUPPLEMENTAL_GROUPS` Show more	list of long
`quarkus.knative.security-context.fs-group` A special supplemental group that applies to all containers in a pod. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_FS_GROUP` Show more	long
`quarkus.knative.security-context.sysctls."sysctl-name"` Sysctls hold a list of namespaced sysctls used for the pod. Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_SYSCTLS__SYSCTL_NAME_` Show more	Map<String,String>
`quarkus.knative.security-context.fs-group-change-policy` It holds policies that will be used for applying fsGroup to a volume when volume is mounted. Values: OnRootMismatch, Always Environment variable: `QUARKUS_KNATIVE_SECURITY_CONTEXT_FS_GROUP_CHANGE_POLICY` Show more	`on-root-mismatch`It indicates that volume’s ownership and permissions will be changed only when permission and ownership of root directory does not match with expected permissions on the volume., `always`It indicates that volume’s ownership and permissions should always be changed whenever volume is mounted inside a Pod. This the default behavior.
`quarkus.knative.deploy` If set to true, Quarkus will attempt to deploy the application to the target knative cluster Environment variable: `QUARKUS_KNATIVE_DEPLOY` Show more	boolean	`false`
`quarkus.knative.deploy-strategy` If deploy is enabled, it will follow this strategy to update the resources to the target Knative cluster. Environment variable: `QUARKUS_KNATIVE_DEPLOY_STRATEGY` Show more	`create-or-update`, `create`, `replace`, `server-side-apply`	`create-or-update`

Configuration property

类型

默认

quarkus.knative.part-of

The name of the group this component belongs too

Environment variable: QUARKUS_KNATIVE_PART_OF

string

quarkus.knative.name

The name of the application. This value will be used for naming Kubernetes resources like: - Deployment - Service and so on …

Environment variable: QUARKUS_KNATIVE_NAME

string

quarkus.knative.version

The version of the application.

Environment variable: QUARKUS_KNATIVE_VERSION

string

quarkus.knative.namespace

Environment variable: QUARKUS_KNATIVE_NAMESPACE

string

quarkus.knative.labels."label-name"

Custom labels to add to all resources

Environment variable: QUARKUS_KNATIVE_LABELS__LABEL_NAME_

Map<String,String>

quarkus.knative.annotations."annotation-name"

Custom annotations to add to all resources

Environment variable: QUARKUS_KNATIVE_ANNOTATIONS__ANNOTATION_NAME_

Map<String,String>

quarkus.knative.add-build-timestamp

Environment variable: QUARKUS_KNATIVE_ADD_BUILD_TIMESTAMP

boolean

true

quarkus.knative.working-dir

Working directory

Environment variable: QUARKUS_KNATIVE_WORKING_DIR

string

quarkus.knative.command

The commands

Environment variable: QUARKUS_KNATIVE_COMMAND

list of string

quarkus.knative.arguments

The arguments

Environment variable: QUARKUS_KNATIVE_ARGUMENTS

list of string

quarkus.knative.service-account

The service account

Environment variable: QUARKUS_KNATIVE_SERVICE_ACCOUNT

string

quarkus.knative.ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_KNATIVE_PORTS__PORTS__CONTAINER_PORT

int

quarkus.knative.ports."ports".host-port

The host port.

Environment variable: QUARKUS_KNATIVE_PORTS__PORTS__HOST_PORT

int

quarkus.knative.ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_KNATIVE_PORTS__PORTS__PATH

string

/

quarkus.knative.ports."ports".protocol

The protocol.

Environment variable: QUARKUS_KNATIVE_PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.knative.ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_KNATIVE_PORTS__PORTS__NODE_PORT

int

quarkus.knative.ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_KNATIVE_PORTS__PORTS__TLS

boolean

false

quarkus.knative.service-type

The type of service that will be generated for the application

Environment variable: QUARKUS_KNATIVE_SERVICE_TYPE

cluster-ip, node-port, load-balancer, external-name

cluster-ip

quarkus.knative.image-pull-policy

Image pull policy

Environment variable: QUARKUS_KNATIVE_IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.knative.image-pull-secrets

The image pull secret

Environment variable: QUARKUS_KNATIVE_IMAGE_PULL_SECRETS

list of string

quarkus.knative.generate-image-pull-secret

Enable generation of image pull secret, when the container image username and password are provided.

Environment variable: QUARKUS_KNATIVE_GENERATE_IMAGE_PULL_SECRET

boolean

false

quarkus.knative.liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.liveness-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_EXEC_ACTION

string

quarkus.knative.liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_GRPC_ACTION

string

quarkus.knative.liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.knative.liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.knative.liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.readiness-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_EXEC_ACTION

string

quarkus.knative.readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_GRPC_ACTION

string

quarkus.knative.readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_PERIOD

Duration

10S

quarkus.knative.readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.knative.readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.startup-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.startup-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.startup-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.startup-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.startup-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_EXEC_ACTION

string

quarkus.knative.startup-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.startup-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_GRPC_ACTION

string

quarkus.knative.startup-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.startup-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.startup-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_PERIOD

Duration

10S

quarkus.knative.startup-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_TIMEOUT

Duration

10S

quarkus.knative.startup-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.startup-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_STARTUP_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.prometheus.annotations

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_ANNOTATIONS

boolean

true

quarkus.knative.prometheus.generate-service-monitor

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_GENERATE_SERVICE_MONITOR

boolean

true

quarkus.knative.prometheus.prefix

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_PREFIX

string

prometheus.io

quarkus.knative.prometheus.scrape

Define the annotation used to indicate services that should be scraped. By default, /scrape will be appended to the defined prefix.

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_SCRAPE

string

quarkus.knative.prometheus.path

Define the annotation used to indicate the path to scrape. By default, /path will be appended to the defined prefix.

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_PATH

string

quarkus.knative.prometheus.port

Define the annotation used to indicate the port to scrape. By default, /port will be appended to the defined prefix.

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_PORT

string

quarkus.knative.prometheus.scheme

Define the annotation used to indicate the scheme to use for scraping By default, /scheme will be appended to the defined prefix.

Environment variable: QUARKUS_KNATIVE_PROMETHEUS_SCHEME

string

quarkus.knative.mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_KNATIVE_MOUNTS__MOUNTS__NAME

string

quarkus.knative.mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_KNATIVE_MOUNTS__MOUNTS__PATH

string

quarkus.knative.mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_KNATIVE_MOUNTS__MOUNTS__SUB_PATH

string

quarkus.knative.mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_KNATIVE_MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.knative.secret-volumes."secret-volumes".secret-name

The name of the secret to mount.

Environment variable: QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__SECRET_NAME

string

required

quarkus.knative.secret-volumes."secret-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__DEFAULT_MODE

string

0600

quarkus.knative.secret-volumes."secret-volumes".items."items".path

The path where the file will be mounted.

Environment variable: QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__PATH

string

required

quarkus.knative.secret-volumes."secret-volumes".items."items".mode

It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used.

Environment variable: QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__ITEMS__ITEMS__MODE

int

-1

quarkus.knative.secret-volumes."secret-volumes".optional

Optional

Environment variable: QUARKUS_KNATIVE_SECRET_VOLUMES__SECRET_VOLUMES__OPTIONAL

boolean

false

quarkus.knative.config-map-volumes."config-map-volumes".config-map-name

The name of the ConfigMap to mount.

Environment variable: QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__CONFIG_MAP_NAME

string

required

quarkus.knative.config-map-volumes."config-map-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__DEFAULT_MODE

string

0600

quarkus.knative.config-map-volumes."config-map-volumes".items."items".path

The path where the file will be mounted.

Environment variable: QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__PATH

string

required

quarkus.knative.config-map-volumes."config-map-volumes".items."items".mode

It must be a value between 0000 and 0777. If not specified, the volume defaultMode will be used.

Environment variable: QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__ITEMS__ITEMS__MODE

int

-1

quarkus.knative.config-map-volumes."config-map-volumes".optional

Optional

Environment variable: QUARKUS_KNATIVE_CONFIG_MAP_VOLUMES__CONFIG_MAP_VOLUMES__OPTIONAL

boolean

false

quarkus.knative.empty-dir-volumes

EmptyDir volumes

Environment variable: QUARKUS_KNATIVE_EMPTY_DIR_VOLUMES

list of string

quarkus.knative.git-repo-volumes."git-repo-volumes".repository

Git repository URL.

Environment variable: QUARKUS_KNATIVE_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REPOSITORY

string

required

quarkus.knative.git-repo-volumes."git-repo-volumes".directory

The directory of the repository to mount.

Environment variable: QUARKUS_KNATIVE_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__DIRECTORY

string

quarkus.knative.git-repo-volumes."git-repo-volumes".revision

The commit hash to use.

Environment variable: QUARKUS_KNATIVE_GIT_REPO_VOLUMES__GIT_REPO_VOLUMES__REVISION

string

quarkus.knative.pvc-volumes."pvc-volumes".claim-name

The name of the claim to mount.

Environment variable: QUARKUS_KNATIVE_PVC_VOLUMES__PVC_VOLUMES__CLAIM_NAME

string

required

quarkus.knative.pvc-volumes."pvc-volumes".default-mode

Default mode. When specifying an octal number, leading zero must be present.

Environment variable: QUARKUS_KNATIVE_PVC_VOLUMES__PVC_VOLUMES__DEFAULT_MODE

string

0600

quarkus.knative.pvc-volumes."pvc-volumes".optional

Optional

Environment variable: QUARKUS_KNATIVE_PVC_VOLUMES__PVC_VOLUMES__OPTIONAL

boolean

false

quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".volume-id

The name of the disk to mount.

Environment variable: QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__VOLUME_ID

string

required

quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".partition

The partition.

Environment variable: QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__PARTITION

int

quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".fs-type

Filesystem type.

Environment variable: QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__FS_TYPE

string

ext4

quarkus.knative.aws-elastic-block-store-volumes."aws-elastic-block-store-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_KNATIVE_AWS_ELASTIC_BLOCK_STORE_VOLUMES__AWS_ELASTIC_BLOCK_STORE_VOLUMES__READ_ONLY

boolean

false

quarkus.knative.azure-file-volumes."azure-file-volumes".share-name

The share name.

Environment variable: QUARKUS_KNATIVE_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SHARE_NAME

string

required

quarkus.knative.azure-file-volumes."azure-file-volumes".secret-name

The secret name.

Environment variable: QUARKUS_KNATIVE_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__SECRET_NAME

string

required

quarkus.knative.azure-file-volumes."azure-file-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_KNATIVE_AZURE_FILE_VOLUMES__AZURE_FILE_VOLUMES__READ_ONLY

boolean

false

quarkus.knative.azure-disk-volumes."azure-disk-volumes".disk-name

The name of the disk to mount.

Environment variable: QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_NAME

string

required

quarkus.knative.azure-disk-volumes."azure-disk-volumes".disk-uri

The URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed

Environment variable: QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__DISK_URI

string

required

quarkus.knative.azure-disk-volumes."azure-disk-volumes".kind

Kind of disk.

Environment variable: QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__KIND

managed, shared

managed

quarkus.knative.azure-disk-volumes."azure-disk-volumes".caching-mode

Disk caching mode.

Environment variable: QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__CACHING_MODE

read-write, read-only, none

read-write

quarkus.knative.azure-disk-volumes."azure-disk-volumes".fs-type

File system type.

Environment variable: QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__FS_TYPE

string

ext4

quarkus.knative.azure-disk-volumes."azure-disk-volumes".read-only

Whether the volumeName is read only or not.

Environment variable: QUARKUS_KNATIVE_AZURE_DISK_VOLUMES__AZURE_DISK_VOLUMES__READ_ONLY

boolean

false

quarkus.knative.container-name

If set, it will change the name of the container according to the configuration

Environment variable: QUARKUS_KNATIVE_CONTAINER_NAME

string

quarkus.knative.init-containers."init-containers".image

The container image.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE

string

quarkus.knative.init-containers."init-containers".working-dir

Working directory.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__WORKING_DIR

string

quarkus.knative.init-containers."init-containers".command

The commands

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__COMMAND

list of string

quarkus.knative.init-containers."init-containers".arguments

The arguments

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ARGUMENTS

list of string

quarkus.knative.init-containers."init-containers".service-account

The service account.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__SERVICE_ACCOUNT

string

quarkus.knative.init-containers."init-containers".host

The host under which the application is going to be exposed.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__HOST

string

quarkus.knative.init-containers."init-containers".ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__CONTAINER_PORT

int

quarkus.knative.init-containers."init-containers".ports."ports".host-port

The host port.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__HOST_PORT

int

quarkus.knative.init-containers."init-containers".ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PATH

string

/

quarkus.knative.init-containers."init-containers".ports."ports".protocol

The protocol.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.knative.init-containers."init-containers".ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__NODE_PORT

int

quarkus.knative.init-containers."init-containers".ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__PORTS__PORTS__TLS

boolean

false

quarkus.knative.init-containers."init-containers".image-pull-policy

Image pull policy.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.knative.init-containers."init-containers".image-pull-secrets

The image pull secret

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__IMAGE_PULL_SECRETS

list of string

quarkus.knative.init-containers."init-containers".liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.init-containers."init-containers".liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.init-containers."init-containers".liveness-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.init-containers."init-containers".liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.init-containers."init-containers".liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_EXEC_ACTION

string

quarkus.knative.init-containers."init-containers".liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.init-containers."init-containers".liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION

string

quarkus.knative.init-containers."init-containers".liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.init-containers."init-containers".liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.init-containers."init-containers".liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.knative.init-containers."init-containers".liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.knative.init-containers."init-containers".liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.init-containers."init-containers".liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.init-containers."init-containers".readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.init-containers."init-containers".readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.init-containers."init-containers".readiness-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.init-containers."init-containers".readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.init-containers."init-containers".readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_EXEC_ACTION

string

quarkus.knative.init-containers."init-containers".readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.init-containers."init-containers".readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION

string

quarkus.knative.init-containers."init-containers".readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.init-containers."init-containers".readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.init-containers."init-containers".readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_PERIOD

Duration

10S

quarkus.knative.init-containers."init-containers".readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.knative.init-containers."init-containers".readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.init-containers."init-containers".readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.init-containers."init-containers".mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__NAME

string

quarkus.knative.init-containers."init-containers".mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__PATH

string

quarkus.knative.init-containers."init-containers".mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__SUB_PATH

string

quarkus.knative.init-containers."init-containers".mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.knative.init-containers."init-containers".resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_CPU

string

quarkus.knative.init-containers."init-containers".resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_LIMITS_MEMORY

string

quarkus.knative.init-containers."init-containers".resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_CPU

string

quarkus.knative.init-containers."init-containers".resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__RESOURCES_REQUESTS_MEMORY

string

quarkus.knative.init-containers."init-containers".env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_SECRETS

list of string

quarkus.knative.init-containers."init-containers".env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_CONFIGMAPS

list of string

quarkus.knative.init-containers."init-containers".env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.knative.init-containers."init-containers".env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.knative.init-containers."init-containers".env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.knative.init-containers."init-containers".env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.knative.init-containers."init-containers".env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.knative.init-containers."init-containers".env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.knative.init-containers."init-containers".env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KNATIVE_INIT_CONTAINERS__INIT_CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.knative.containers."containers".image

The container image.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__IMAGE

string

quarkus.knative.containers."containers".working-dir

Working directory.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__WORKING_DIR

string

quarkus.knative.containers."containers".command

The commands

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__COMMAND

list of string

quarkus.knative.containers."containers".arguments

The arguments

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ARGUMENTS

list of string

quarkus.knative.containers."containers".service-account

The service account.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__SERVICE_ACCOUNT

string

quarkus.knative.containers."containers".host

The host under which the application is going to be exposed.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__HOST

string

quarkus.knative.containers."containers".ports."ports".container-port

The port number. Refers to the container port.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__CONTAINER_PORT

int

quarkus.knative.containers."containers".ports."ports".host-port

The host port.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__HOST_PORT

int

quarkus.knative.containers."containers".ports."ports".path

The application path (refers to web application path).

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__PATH

string

/

quarkus.knative.containers."containers".ports."ports".protocol

The protocol.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__PROTOCOL

tcp, udp, sctp, http, proxy

tcp

quarkus.knative.containers."containers".ports."ports".node-port

The nodePort to which this port should be mapped to. This only takes affect when the serviceType is set to node-port.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__NODE_PORT

int

quarkus.knative.containers."containers".ports."ports".tls

If enabled, the port will be configured to use the schema HTTPS.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__PORTS__PORTS__TLS

boolean

false

quarkus.knative.containers."containers".image-pull-policy

Image pull policy.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__IMAGE_PULL_POLICY

always, if-not-present, never

always

quarkus.knative.containers."containers".image-pull-secrets

The image pull secret

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__IMAGE_PULL_SECRETS

list of string

quarkus.knative.containers."containers".liveness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.containers."containers".liveness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.containers."containers".liveness-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.containers."containers".liveness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.containers."containers".liveness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_EXEC_ACTION

string

quarkus.knative.containers."containers".liveness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.containers."containers".liveness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_GRPC_ACTION

string

quarkus.knative.containers."containers".liveness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.containers."containers".liveness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.containers."containers".liveness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_PERIOD

Duration

10S

quarkus.knative.containers."containers".liveness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_TIMEOUT

Duration

10S

quarkus.knative.containers."containers".liveness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.containers."containers".liveness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__LIVENESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.containers."containers".readiness-probe.http-action-port

The port number to use when configuring the http get action. If not configured, the port corresponding to the httpActionPortName will be used.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT

int

quarkus.knative.containers."containers".readiness-probe.http-action-port-name

The port name for selecting the port of the HTTP get action.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_PORT_NAME

string

quarkus.knative.containers."containers".readiness-probe.http-action-path

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_PATH

string

quarkus.knative.containers."containers".readiness-probe.http-action-scheme

The scheme of the HTTP get action. Can be either "HTTP" or "HTTPS".

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_HTTP_ACTION_SCHEME

string

quarkus.knative.containers."containers".readiness-probe.exec-action

The command to use for the probe.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_EXEC_ACTION

string

quarkus.knative.containers."containers".readiness-probe.tcp-socket-action

The tcp socket to use for the probe (the format is host:port).

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_TCP_SOCKET_ACTION

string

quarkus.knative.containers."containers".readiness-probe.grpc-action

The gRPC port to use for the probe (the format is either port or port:service).

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_GRPC_ACTION

string

quarkus.knative.containers."containers".readiness-probe.grpc-action-enabled

If enabled and grpc-action is not provided, it will use the generated service name and the gRPC port.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_GRPC_ACTION_ENABLED

boolean

false

quarkus.knative.containers."containers".readiness-probe.initial-delay

The amount of time to wait before starting to probe.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_INITIAL_DELAY

Duration

5S

quarkus.knative.containers."containers".readiness-probe.period

The period in which the action should be called.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_PERIOD

Duration

10S

quarkus.knative.containers."containers".readiness-probe.timeout

The amount of time to wait for each action.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_TIMEOUT

Duration

10S

quarkus.knative.containers."containers".readiness-probe.success-threshold

The success threshold to use.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_SUCCESS_THRESHOLD

int

1

quarkus.knative.containers."containers".readiness-probe.failure-threshold

The failure threshold to use.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__READINESS_PROBE_FAILURE_THRESHOLD

int

3

quarkus.knative.containers."containers".mounts."mounts".name

The name of the volumeName to mount.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__NAME

string

quarkus.knative.containers."containers".mounts."mounts".path

The path to mount.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__PATH

string

quarkus.knative.containers."containers".mounts."mounts".sub-path

Path within the volumeName from which the container’s volumeName should be mounted.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__SUB_PATH

string

quarkus.knative.containers."containers".mounts."mounts".read-only

ReadOnly

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__MOUNTS__MOUNTS__READ_ONLY

boolean

false

quarkus.knative.containers."containers".resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_LIMITS_CPU

string

quarkus.knative.containers."containers".resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_LIMITS_MEMORY

string

quarkus.knative.containers."containers".resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_REQUESTS_CPU

string

quarkus.knative.containers."containers".resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__RESOURCES_REQUESTS_MEMORY

string

quarkus.knative.containers."containers".env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_SECRETS

list of string

quarkus.knative.containers."containers".env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_CONFIGMAPS

list of string

quarkus.knative.containers."containers".env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.knative.containers."containers".env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.knative.containers."containers".env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.knative.containers."containers".env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.knative.containers."containers".env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.knative.containers."containers".env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.knative.containers."containers".env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KNATIVE_CONTAINERS__CONTAINERS__ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.knative.host-aliases."host-aliases".ip

The ip address

Environment variable: QUARKUS_KNATIVE_HOST_ALIASES__HOST_ALIASES__IP

string

quarkus.knative.host-aliases."host-aliases".hostnames

The hostnames to resolve to the ip

Environment variable: QUARKUS_KNATIVE_HOST_ALIASES__HOST_ALIASES__HOSTNAMES

list of string

quarkus.knative.resources.limits.cpu

CPU Requirements

Environment variable: QUARKUS_KNATIVE_RESOURCES_LIMITS_CPU

string

quarkus.knative.resources.limits.memory

Memory Requirements

Environment variable: QUARKUS_KNATIVE_RESOURCES_LIMITS_MEMORY

string

quarkus.knative.resources.requests.cpu

CPU Requirements

Environment variable: QUARKUS_KNATIVE_RESOURCES_REQUESTS_CPU

string

quarkus.knative.resources.requests.memory

Memory Requirements

Environment variable: QUARKUS_KNATIVE_RESOURCES_REQUESTS_MEMORY

string

quarkus.knative.rbac.roles."roles".name

The name of the role.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__NAME

string

quarkus.knative.rbac.roles."roles".namespace

The namespace of the role.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__NAMESPACE

string

quarkus.knative.rbac.roles."roles".labels."label-name"

Labels to add into the Role resource.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__LABELS__LABEL_NAME_

Map<String,String>

quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".api-groups

API groups of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS

list of string

quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".non-resource-urls

Non resource URLs of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS

list of string

quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".resource-names

Resource names of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES

list of string

quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".resources

Resources of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__RESOURCES

list of string

quarkus.knative.rbac.roles."roles".policy-rules."policy-rules".verbs

Verbs of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLES__ROLES__POLICY_RULES__POLICY_RULES__VERBS

list of string

quarkus.knative.rbac.cluster-roles."cluster-roles".name

The name of the cluster role.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__NAME

string

quarkus.knative.rbac.cluster-roles."cluster-roles".labels."label-name"

Labels to add into the ClusterRole resource.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__LABELS__LABEL_NAME_

Map<String,String>

quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".api-groups

API groups of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__API_GROUPS

list of string

quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".non-resource-urls

Non resource URLs of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__NON_RESOURCE_URLS

list of string

quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resource-names

Resource names of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCE_NAMES

list of string

quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".resources

Resources of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__RESOURCES

list of string

quarkus.knative.rbac.cluster-roles."cluster-roles".policy-rules."policy-rules".verbs

Verbs of the policy rule.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLES__CLUSTER_ROLES__POLICY_RULES__POLICY_RULES__VERBS

list of string

quarkus.knative.rbac.service-accounts."service-accounts".name

The name of the service account.

Environment variable: QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAME

string

quarkus.knative.rbac.service-accounts."service-accounts".namespace

The namespace of the service account.

Environment variable: QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__NAMESPACE

string

quarkus.knative.rbac.service-accounts."service-accounts".labels."label-name"

Labels of the service account.

Environment variable: QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.knative.rbac.service-accounts."service-accounts".use-as-default

If true, this service account will be used in the generated Deployment resource.

Environment variable: QUARKUS_KNATIVE_RBAC_SERVICE_ACCOUNTS__SERVICE_ACCOUNTS__USE_AS_DEFAULT

boolean

quarkus.knative.rbac.role-bindings."role-bindings".name

Name of the RoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__NAME

string

quarkus.knative.rbac.role-bindings."role-bindings".labels."label-name"

Labels to add into the RoleBinding resource.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.knative.rbac.role-bindings."role-bindings".role-name

The name of the Role resource to use by the RoleRef element in the generated Role Binding resource. By default, it’s "view" role name.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__ROLE_NAME

string

quarkus.knative.rbac.role-bindings."role-bindings".cluster-wide

If the Role sets in the role-name property is cluster wide or not.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__CLUSTER_WIDE

boolean

quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".name

The "name" resource to use by the Subject element in the generated Role Binding resource.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME

string

quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".kind

The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND

string

ServiceAccount

quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".api-group

The "apiGroup" resource that matches with the "kind" property. By default, it’s empty.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP

string

quarkus.knative.rbac.role-bindings."role-bindings".subjects."subjects".namespace

The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources.

Environment variable: QUARKUS_KNATIVE_RBAC_ROLE_BINDINGS__ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE

string

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".name

Name of the ClusterRoleBinding resource to be generated. If not provided, it will use the application name plus the role ref name.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__NAME

string

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".labels."label-name"

Labels to add into the RoleBinding resource.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__LABELS__LABEL_NAME_

Map<String,String>

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".role-name

The name of the ClusterRole resource to use by the RoleRef element in the generated ClusterRoleBinding resource.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__ROLE_NAME

string

required

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".name

The "name" resource to use by the Subject element in the generated Role Binding resource.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAME

string

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".kind

The "kind" resource to use by the Subject element in the generated Role Binding resource. By default, it uses the "ServiceAccount" kind.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__KIND

string

ServiceAccount

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".api-group

The "apiGroup" resource that matches with the "kind" property. By default, it’s empty.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__API_GROUP

string

quarkus.knative.rbac.cluster-role-bindings."cluster-role-bindings".subjects."subjects".namespace

The "namespace" resource to use by the Subject element in the generated Role Binding resource. By default, it will use the same as provided in the generated resources.

Environment variable: QUARKUS_KNATIVE_RBAC_CLUSTER_ROLE_BINDINGS__CLUSTER_ROLE_BINDINGS__SUBJECTS__SUBJECTS__NAMESPACE

string

quarkus.knative.add-version-to-label-selectors

If true, the 'app.kubernetes.io/version' label will be part of the selectors of Service and Deployment

Environment variable: QUARKUS_KNATIVE_ADD_VERSION_TO_LABEL_SELECTORS

boolean

true

quarkus.knative.add-name-to-label-selectors

If true, the 'app.kubernetes.io/name' label will be part of the selectors of Service and Deployment

Environment variable: QUARKUS_KNATIVE_ADD_NAME_TO_LABEL_SELECTORS

boolean

true

quarkus.knative.idempotent

Switch used to control whether non-idempotent fields are included in generated kubernetes resources to improve git-ops compatibility

Environment variable: QUARKUS_KNATIVE_IDEMPOTENT

boolean

false

quarkus.knative.vcs-uri.enabled

Whether the vcs-uri annotation should be added to the generated configuration.

Environment variable: QUARKUS_KNATIVE_VCS_URI_ENABLED

boolean

true

quarkus.knative.vcs-uri.override

Optional override of the vcs-uri annotation.

Environment variable: QUARKUS_KNATIVE_VCS_URI_OVERRIDE

string

quarkus.knative.env.secrets

The optional list of Secret names to load environment variables from.

Environment variable: QUARKUS_KNATIVE_ENV_SECRETS

list of string

quarkus.knative.env.configmaps

The optional list of ConfigMap names to load environment variables from.

Environment variable: QUARKUS_KNATIVE_ENV_CONFIGMAPS

list of string

quarkus.knative.env.fields."environment-variable-name"

The map associating environment variable names to their associated field references they take their value from.

Environment variable: QUARKUS_KNATIVE_ENV_FIELDS__ENVIRONMENT_VARIABLE_NAME_

Map<String,String>

quarkus.knative.env.vars."vars"

The map associating environment name to its associated value.

Environment variable: QUARKUS_KNATIVE_ENV_VARS__VARS_

Map<String,Optional<String>>

quarkus.knative.env.mapping."mapping".from-secret

The optional name of the Secret from which a value is to be extracted. Mutually exclusive with from-configmap.

Environment variable: QUARKUS_KNATIVE_ENV_MAPPING__MAPPING__FROM_SECRET

string

quarkus.knative.env.mapping."mapping".from-configmap

The optional name of the ConfigMap from which a value is to be extracted. Mutually exclusive with from-secret.

Environment variable: QUARKUS_KNATIVE_ENV_MAPPING__MAPPING__FROM_CONFIGMAP

string

quarkus.knative.env.mapping."mapping".with-key

The key identifying the field from which the value is extracted.

Environment variable: QUARKUS_KNATIVE_ENV_MAPPING__MAPPING__WITH_KEY

string

required

quarkus.knative.env.using-prefix."prefixes".for-secret

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KNATIVE_ENV_USING_PREFIX__PREFIXES__FOR_SECRET

string

quarkus.knative.env.using-prefix."prefixes".for-configmap

The optional prefix to use when adding the environment variable to the container.

Environment variable: QUARKUS_KNATIVE_ENV_USING_PREFIX__PREFIXES__FOR_CONFIGMAP

string

quarkus.knative.cluster-local

Whether this service is cluster-local. Cluster local services are not exposed to the outside world. More information in this link.

Environment variable: QUARKUS_KNATIVE_CLUSTER_LOCAL

boolean

false

quarkus.knative.min-scale

This value controls the minimum number of replicas each revision should have. Knative will attempt to never have less than this number of replicas at any point in time.

Environment variable: QUARKUS_KNATIVE_MIN_SCALE

int

quarkus.knative.max-scale

This value controls the maximum number of replicas each revision should have. Knative will attempt to never have more than this number of replicas running, or in the process of being created, at any point in time.

Environment variable: QUARKUS_KNATIVE_MAX_SCALE

int

quarkus.knative.scale-to-zero-enabled

The scale-to-zero values control whether Knative allows revisions to scale down to zero, or stops at “1”.

Environment variable: QUARKUS_KNATIVE_SCALE_TO_ZERO_ENABLED

boolean

true

quarkus.knative.revision-auto-scaling.auto-scaler-class

The Autoscaler class. Knative Serving comes with its own autoscaler, the KPA (Knative Pod Autoscaler) but can also be configured to use Kubernetes’ HPA (Horizontal Pod Autoscaler) or even a custom third-party autoscaler. Possible values (kpa, hpa, default: kpa).

Environment variable: QUARKUS_KNATIVE_REVISION_AUTO_SCALING_AUTO_SCALER_CLASS

kpaKubernetes Pod Autoscaler, hpaHorizontal Pod Autoscaler

quarkus.knative.revision-auto-scaling.metric

The autoscaling metric to use. Possible values (concurrency, rps, cpu).

Environment variable: QUARKUS_KNATIVE_REVISION_AUTO_SCALING_METRIC

concurrencyConcurrency, rpsRequests per second, cpuCPU

quarkus.knative.revision-auto-scaling.target

The autoscaling target.

Environment variable: QUARKUS_KNATIVE_REVISION_AUTO_SCALING_TARGET

int

quarkus.knative.revision-auto-scaling.container-concurrency

The exact amount of requests allowed to the replica at a time. Its default value is “0”, which means an unlimited number of requests are allowed to flow into the replica.

Environment variable: QUARKUS_KNATIVE_REVISION_AUTO_SCALING_CONTAINER_CONCURRENCY

int

quarkus.knative.revision-auto-scaling.target-utilization-percentage

This value specifies a percentage of the target to actually be targeted by the autoscaler.

Environment variable: QUARKUS_KNATIVE_REVISION_AUTO_SCALING_TARGET_UTILIZATION_PERCENTAGE

int

quarkus.knative.global-auto-scaling.auto-scaler-class

Environment variable: QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_AUTO_SCALER_CLASS

kpaKubernetes Pod Autoscaler, hpaHorizontal Pod Autoscaler

quarkus.knative.global-auto-scaling.container-concurrency

The exact amount of requests allowed to the replica at a time. Its default value is “0”, which means an unlimited number of requests are allowed to flow Integer>o the replica.

Environment variable: QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_CONTAINER_CONCURRENCY

int

quarkus.knative.global-auto-scaling.target-utilization-percentage

This value specifies a percentage of the target to actually be targeted by the autoscaler.

Environment variable: QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_TARGET_UTILIZATION_PERCENTAGE

int

quarkus.knative.global-auto-scaling.requests-per-second

The requests per second per replica.

Environment variable: QUARKUS_KNATIVE_GLOBAL_AUTO_SCALING_REQUESTS_PER_SECOND

int

quarkus.knative.revision-name

The name of the revision.

Environment variable: QUARKUS_KNATIVE_REVISION_NAME

string

quarkus.knative.traffic."traffic".tag

Tag is optionally used to expose a dedicated url for referencing this target exclusively.

Environment variable: QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__TAG

string

quarkus.knative.traffic."traffic".revision-name

RevisionName of a specific revision to which to send this portion of traffic.

Environment variable: QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__REVISION_NAME

string

quarkus.knative.traffic."traffic".latest-revision

LatestRevision may be optionally provided to indicate that the latest ready Revision of the Configuration should be used for this traffic target. When provided LatestRevision must be true if RevisionName is empty.

Environment variable: QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__LATEST_REVISION

boolean

false

quarkus.knative.traffic."traffic".percent

Percent indicates that percentage based routing should be used and the value indicates the percent of traffic that is to be routed to this Revision or Configuration. 0 (zero) mean no traffic, 100 means all traffic.

Environment variable: QUARKUS_KNATIVE_TRAFFIC__TRAFFIC__PERCENT

long

100

quarkus.knative.app-secret

If set, the secret will mounted to the application container and its contents will be used for application configuration.

Environment variable: QUARKUS_KNATIVE_APP_SECRET

string

quarkus.knative.app-config-map

If set, the config map will be mounted to the application container and its contents will be used for application configuration.

Environment variable: QUARKUS_KNATIVE_APP_CONFIG_MAP

string

quarkus.knative.security-context.se-linux-options.level

The SELinux level label that applies to the container.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_LEVEL

string

quarkus.knative.security-context.se-linux-options.role

The SELinux role label that applies to the container.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_ROLE

string

quarkus.knative.security-context.se-linux-options.type

The SELinux type label that applies to the container.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_TYPE

string

quarkus.knative.security-context.se-linux-options.user

The SELinux user label that applies to the container.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_SE_LINUX_OPTIONS_USER

string

quarkus.knative.security-context.windows-options.gmsa-credential-spec-name

The name of the GMSA credential spec to use.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC_NAME

string

quarkus.knative.security-context.windows-options.gmsa-credential-spec

GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_GMSA_CREDENTIAL_SPEC

string

quarkus.knative.security-context.windows-options.run-as-user-name

The UserName in Windows to run the entrypoint of the container process.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_RUN_AS_USER_NAME

string

quarkus.knative.security-context.windows-options.host-process

HostProcess determines if a container should be run as a 'Host Process' container.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_WINDOWS_OPTIONS_HOST_PROCESS

boolean

quarkus.knative.security-context.run-as-user

The UID to run the entrypoint of the container process.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_RUN_AS_USER

long

quarkus.knative.security-context.run-as-group

The GID to run the entrypoint of the container process.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_RUN_AS_GROUP

long

quarkus.knative.security-context.run-as-non-root

Indicates that the container must run as a non-root user.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_RUN_AS_NON_ROOT

boolean

quarkus.knative.security-context.supplemental-groups

A list of groups applied to the first process run in each container, in addition to the container’s primary GID. If unspecified, no groups will be added to any container.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_SUPPLEMENTAL_GROUPS

list of long

quarkus.knative.security-context.fs-group

A special supplemental group that applies to all containers in a pod.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_FS_GROUP

long

quarkus.knative.security-context.sysctls."sysctl-name"

Sysctls hold a list of namespaced sysctls used for the pod.

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_SYSCTLS__SYSCTL_NAME_

Map<String,String>

quarkus.knative.security-context.fs-group-change-policy

It holds policies that will be used for applying fsGroup to a volume when volume is mounted. Values: OnRootMismatch, Always

Environment variable: QUARKUS_KNATIVE_SECURITY_CONTEXT_FS_GROUP_CHANGE_POLICY

quarkus.knative.deploy

If set to true, Quarkus will attempt to deploy the application to the target knative cluster

Environment variable: QUARKUS_KNATIVE_DEPLOY

boolean

false

quarkus.knative.deploy-strategy

If deploy is enabled, it will follow this strategy to update the resources to the target Knative cluster.

Environment variable: QUARKUS_KNATIVE_DEPLOY_STRATEGY

create-or-update, create, replace, server-side-apply

create-or-update

Deployment targets

Mentioned in the previous sections was the concept of deployment-target. This concept allows users to control which Kubernetes manifests will be generated and deployed to a cluster (if quarkus.kubernetes.deploy has been set to true).

By default, when no deployment-target is set, then only vanilla Kubernetes resources are generated and deployed. When multiple values are set (for example quarkus.kubernetes.deployment-target=kubernetes,openshift) then the resources for all targets are generated, but only the resources that correspond to the first target are applied to the cluster (if deployment is enabled).

For users that prefer to keep the application.properties independent of the deployment platform, the deployment target can be specified directly in the deploy command by adding -Dquarkus.kubernetes.deployment-target=knative in addition to -Dquarkus.knative.deploy=true. Furthermore, Quarkus allows collapsing the two properties into one: -Dquarkus.knative.deploy=true.

./mvnw clean package -Dquarkus.knative.deploy=true

The equivalent with gradle:

./gradlew build -Dquarkus.knative.deploy=true

In case that both properties are used with conflicting values -Dquarkus.kubernetes.deployment-target is used.

In the case of wrapper extensions like OpenShift and Minikube, when these extensions have been explicitly added to the project, the default deployment-target is set by those extensions. For example if quarkus-minikube has been added to a project, then minikube becomes the default deployment target and its resources will be applied to the Kubernetes cluster when deployment via quarkus.kubernetes.deploy has been set. Users can still override the deployment-targets manually using quarkus.kubernetes.deployment-target.

Deprecated configuration

The following categories of configuration properties have been deprecated.

Properties without the quarkus prefix

In earlier versions of the extension, the quarkus. was missing from those properties. These properties are now deprecated.

Docker and S2i properties

The properties for configuring docker and s2i are also deprecated in favor of the new container-image extensions.

Config group arrays

Properties referring to config group arrays (e.g. kubernetes.labels[0], kubernetes.env-vars[0] etc) have been converted to Maps to align with the rest of the Quarkus ecosystem.

The code below demonstrates the change in labels config:

# Old labels config:
kubernetes.labels[0].name=foo
kubernetes.labels[0].value=bar

# New labels
quarkus.kubernetes.labels.foo=bar

The code below demonstrates the change in env-vars config:

# Old env-vars config:
kubernetes.env-vars[0].name=foo
kubernetes.env-vars[0].configmap=my-configmap

# New env-vars
quarkus.kubernetes.env-vars.foo.configmap=myconfigmap

`env-vars` properties

quarkus.kubernetes.env-vars are deprecated (though still currently supported as of this writing) and the new declaration style should be used instead. See Environment variables and more specifically Backwards compatibility for more details.

Deployment

To trigger building and deploying a container image you need to enable the quarkus.kubernetes.deploy flag (the flag is disabled by default - furthermore it has no effect during test runs or dev mode). This can be easily done with the command line:

./mvnw clean package -Dquarkus.kubernetes.deploy=true

Building a container image

Building a container image is possible, using any of the 3 available container-image extensions:

Each time deployment is requested, a container image build will be implicitly triggered (no additional properties are required when the Kubernetes deployment has been enabled).

Deploying

When deployment is enabled, the Kubernetes extension will select the resources specified by quarkus.kubernetes.deployment-target and deploy them. This assumes that a .kube/config is available in your user directory that points to the target Kubernetes cluster. In other words the extension will use whatever cluster kubectl uses. The same applies to credentials.

At the moment no additional options are provided for further customization.

Remote Debugging

To remotely debug applications that are running on a kubernetes environment, we need to deploy the application as described in the previous section and add as new property: quarkus.kubernetes.remote-debug.enabled=true. This property will automatically configure the Java application to append the java agent configuration (for example: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005) and also the service resource to listen using the java agent port.

After your application has been deployed with the debug enabled, next you need to tunnel the traffic from your local host machine to the specified port of the java agent:

kubectl port-forward svc/<application name> 5005:5005

Using this command, you’ll forward the traffic from the "localhost:5005" to the kubernetes service running the java agent using the port "5005" which is the one that the java agent uses by default for remote debugging. You can also configure another java agent port using the property quarkus.kubernetes.remote-debug.address-port.

Finally, all you need to do is to configure your favorite IDE to attach the java agent process that is forwarded to localhost:5005 and start to debug your application. For example, in IntelliJ IDEA, you can follow this tutorial to debug remote applications.

Using existing resources

Sometimes it’s desirable to either provide additional resources (e.g. a ConfigMap, a Secret, a Deployment for a database) or provide custom ones that will be used as a base for the generation process. Those resources can be added under src/main/kubernetes directory and can be named after the target environment (e.g. kubernetes.json, openshift.json, knative.json, or the yml equivalents). The correlation between provided and generated files is done by file name. So, a kubernetes.json/kubernetes.yml file added in src/main/kubernetes will only affect the generated kubernetes.json/kubernetes.yml. An openshift.json/openshift.yml file added in src/main/kubernetes will only affect the generated openshift.json/openshift.yml. A knative.json/knative.yml file added in src/main/kubernetes will only affect the generated knative.json/knative.yml and so on. The provided file may be either in json or yaml format and may contain one or more resources. These resources will end up in both generated formats (json and yaml). For example, a secret added in src/main/kubernetes/kubernetes.yml will be added to both the generated kubernetes.yml and kubernetes.json.

Note: At the time of writing there is no mechanism in place that allows a one-to-many relationship between provided and generated files. Minikube is not an exception to the rule above, so if you want to customize the generated minikube manifests, the file placed under src/main/kubernetes will have to be named minikube.json or minikube.yml (naming it kubernetes.yml or kubernetes.json will result in having only the generated kubernetes.yml and kubernetes.json affected).

Any resource found will be added in the generated manifests. Global modifications (e.g. labels, annotations) will also be applied to those resources. If one of the provided resources has the same name as one of the generated ones, then the generated resource will be created on top of the provided resource, respecting existing content when possible (e.g. existing labels, annotations, environment variables, mounts, replicas etc).

The name of the resource is determined by the application name and may be overridden by quarkus.kubernetes.name, quarkus.openshift.name and quarkus.knative.name.

For example, in the kubernetes-quickstart application, we can add a kubernetes.yml file in the src/main/kubernetes that looks like:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: kubernetes-quickstart
  labels:
    app: quickstart
spec:
  replicas: 3
  selector:
    matchLabels:
      app: quickstart
  template:
    metadata:
      labels:
        app: quickstart
    spec:
      containers:
      - name: kubernetes-quickstart
        image: someimage:latest
        ports:
        - containerPort: 80
        env:
        - name: FOO
          value: BAR

The generated kubernetes.yml will look like:

apiVersion: "apps/v1"
kind: "Deployment"
metadata:
  annotations:
    app.quarkus.io/build-timestamp: "2020-04-10 - 12:54:37 +0000"
  labels:
    app: "quickstart"
  name: "kubernetes-quickstart"
spec:
  replicas: 3 (1)
  selector:
    matchLabels:
      app.kubernetes.io/name: "kubernetes-quickstart"
      app.kubernetes.io/version: "1.0.0-SNAPSHOT"
  template:
    metadata:
      annotations:
        app.quarkus.io/build-timestamp: "2020-04-10 - 12:54:37 +0000"
      labels:
        app: "quickstart" (2)
    spec:
      containers:
      - env:
        - name: "FOO" (3)
          value: "BAR"
        image: "<<yourDockerUsername>>/kubernetes-quickstart:1.0.0-SNAPSHOT" (4)
        imagePullPolicy: "Always"
        name: "kubernetes-quickstart"
        ports:
        - containerPort: 8080 (5)
          name: "http"
          protocol: "TCP"
      serviceAccount: "kubernetes-quickstart"

1	The provided replicas,
2	labels and
3	environment variables were retained.
4	However, the image and
5	the container port were modified.

Moreover, the default annotations have been added.

When the resource name does not match the application name (or the overridden name) rather than reusing the resource a new one will be added. Same goes for the container.
When the name of the container does not match the application name (or the overridden name), container specific configuration will be ignored.

Using common resources

When generating the manifests for multiple deployment targets like Kubernetes, OpenShift or Knative, we can place the common resources in src/main/kubernetes/common.yml, so these resources will be integrated into the generated kubernetes.json/kubernetes.yml, and openshift.json/openshift.yml files (if you configure the Kubernetes and OpenShift extensions at the same time).

For example, we can write a ConfigMap resource only once in the file src/main/kubernetes/common.yml:

apiVersion: v1
kind: ConfigMap
metadata:
  name: common-configmap
data:
  hello: world

And this config map resource will be integrated into the generated kubernetes.json/kubernetes.yml, and openshift.json/openshift.yml files.

Service Binding

Quarkus supports the Service Binding Specification for Kubernetes to bind services to applications.

Specifically, Quarkus implements the Workload Projection part of the specification, therefore allowing applications to bind to services, such as a Database or a Broker, without the need for user configuration.

To enable Service Binding for supported extensions, add the quarkus-kubernetes-service-binding extension to the application dependencies.

The following extensions can be used with Service Binding and are supported for Workload Projection:
- quarkus-jdbc-mariadb
- quarkus-jdbc-mssql
- quarkus-jdbc-mysql
- quarkus-jdbc-postgresql
- quarkus-mongodb-client
- quarkus-kafka-client
- quarkus-messaging-kafka
- quarkus-reactive-db2-client
- quarkus-reactive-mssql-client
- quarkus-reactive-mysql-client
- quarkus-reactive-oracle-client
- quarkus-reactive-pg-client
- quarkus-infinispan-client

Workload Projection

Workload Projection is a process of obtaining the configuration for services from the Kubernetes cluster. This configuration takes the form of directory structures that follow certain conventions and is attached to an application or to a service as a mounted volume. The kubernetes-service-binding extension uses this directory structure to create configuration sources, which allows you to configure additional modules, such as databases or message brokers.

During application development, users can use workload projection to connect their application to a development database, or other locally-run services, without changing the actual application code or configuration.

For an example of a workload projection where the directory structure is included in the test resources and passed to integration test, see the Kubernetes Service Binding datasource GitHub repository.

The k8s-sb directory is the root of all service bindings. In this example, only one database called fruit-db is intended to be bound. This binding database has the type file, that indicates postgresql as the database type, while the other files in the directory provide the necessary information to establish the connection.
After your Quarkus project obtains information from SERVICE_BINDING_ROOT environment variables that are set by OpenShift, you can locate generated configuration files that are present in the file system and use them to map the configuration-file values to properties of certain extensions.

Introduction to the Service Binding Operator

The Service Binding Operator is an Operator that implements Service Binding Specification for Kubernetes and is meant to simplify the binding of services to an application. Containerized applications that support Workload Projection obtain service binding information in the form of volume mounts. The Service Binding Operator reads binding service information and mounts it to the application containers that need it.

The correlation between application and bound services is expressed through the ServiceBinding resources, which declares the intent of what services are meant to be bound to what application.

The Service Binding Operator watches for ServiceBinding resources, which inform the Operator what applications are meant to be bound with what services. When a listed application is deployed, the Service Binding Operator collects all the binding information that must be passed to the application, then upgrades the application container by attaching a volume mount with the binding information.

The Service Binding Operator completes the following actions:

Observes ServiceBinding resources for workloads intended to be bound to a particular service
Applies the binding information to the workload using volume mounts

The following chapter describes the automatic and semi-automatic service binding approaches and their use cases. With either approach, the kubernetes-service-binding extension generates a ServiceBinding resource. With the semi-automatic approach, users must provide a configuration for target services manually. With the automatic approach, for a limited set of services generating the ServiceBinding resource, no additional configuration is needed.

Semi-automatic service binding

A service binding process starts with a user specification of required services that will be bound to a certain application. This expression is summarized in the ServiceBinding resource that is generated by the kubernetes-service-binding extension. The use of the kubernetes-service-binding extensions helps users to generate ServiceBinding resources with minimal configuration, therefore simplifying the process overall.

The Service Binding Operator responsible for the binding process then reads the information from the ServiceBinding resource and mounts the required files to a container accordingly.

An example of the ServiceBinding resource:

apiVersion: binding.operators.coreos.com/v1beta1
kind: ServiceBinding
metadata:
 name: binding-request
 namespace: service-binding-demo
spec:
 application:
   name: java-app
   group: apps
   version: v1
   resource: deployments
 services:
 - group: postgres-operator.crunchydata.com
   version: v1beta1
   kind: Database
   name: db-demo
   id: postgresDB

The quarkus-kubernetes-service-binding extension provides a more compact way of expressing the same information. For example:

quarkus.kubernetes-service-binding.services.db-demo.api-version=postgres-operator.crunchydata.com/v1beta1
quarkus.kubernetes-service-binding.services.db-demo.kind=Database

After adding the earlier configuration properties inside your application.properties, the quarkus-kubernetes, in combination with the quarkus-kubernetes-service-binding extension, automatically generates the ServiceBinding resource.

The earlier mentioned db-demo property-configuration identifier now has a double role and also completes the following actions:

Correlates and groups api-version and kind properties together

Defines the name property for the custom resource with a possibility for a later edit. For example:

quarkus.kubernetes-service-binding.services.db-demo.api-version=postgres-operator.crunchydata.com/v1beta1
quarkus.kubernetes-service-binding.services.db-demo.kind=Database
quarkus.kubernetes-service-binding.services.db-demo.name=my-db

Additional resources

For a semi-automatic service binding demonstration, see How to use Quarkus with the Service Binding Operator
List of bindable Operators

Automatic service binding

The quarkus-kubernetes-service-binding extension can generate the ServiceBinding resource automatically after detecting that an application requires access to the external services that are provided by available bindable Operators.

Automatic service binding can be generated for a limited number of service types. To be consistent with established terminology for Kubernetes and Quarkus services, this chapter refers to these service types as kinds.

Table 2. Operators that support the service auto-binding
	Operator	API Version	Kind
`postgresql`	CrunchyData Postgres	postgres-operator.crunchydata.com/v1beta1	PostgresCluster
`mysql`	Percona XtraDB Cluster	pxc.percona.com/v1-9-0	PerconaXtraDBCluster
`mongo`	Percona Mongo	psmdb.percona.com/v1-9-0	PerconaServerMongoDB

Automatic datasource binding

For traditional databases, automatic binding is initiated whenever a datasource is configured as follows:

quarkus.datasource.db-kind=postgresql

The previous configuration, combined with the presence of quarkus-datasource, quarkus-jdbc-postgresql, quarkus-kubernetes, and quarkus-kubernetes-service-binding properties in the application, results in the generation of the ServiceBinding resource for the postgresql database type.

By using the apiVersion and kind properties of the Operator resource, which matches the used postgresql Operator, the generated ServiceBinding resource binds the service or resource to the application.

When you do not specify a name for your database service, the value of the db-kind property is used as the default name.

 services:
 - apiVersion: postgres-operator.crunchydata.com/v1beta1
   kind: PostgresCluster
   name: postgresql

Specified the name of the datasource as follows:

quarkus.datasource.fruits-db.db-kind=postgresql

The service in the generated ServiceBinding then displays as follows:

 services:
 - apiVersion: postgres-operator.crunchydata.com/v1beta1
   kind: PostgresCluster
   name: fruits-db

Similarly, if you use mysql, the name of the datasource can be specified as follows:

quarkus.datasource.fruits-db.db-kind=mysql

The generated service contains the following:

 services:
 - apiVersion: pxc.percona.com/v1-9-0
   kind: PerconaXtraDBCluster
   name: fruits-db

Customizing Automatic Service Binding

Even though automatic binding was developed to eliminate as much manual configuration as possible, there are cases where modifying the generated ServiceBinding resource might still be needed. The generation process exclusively relies on information extracted from the application and the knowledge of the supported Operators, which may not reflect what is deployed in the cluster. The generated resource is based purely on the knowledge of the supported bindable Operators for popular service kinds and a set of conventions that were developed to prevent possible mismatches, such as:

The target resource name does not match the datasource name
A specific Operator needs to be used rather than the default Operator for that service kind
Version conflicts that occur when a user needs to use any other version than default or latest

Conventions

The target resource coordinates are determined based on the type of Operator and the kind of service.
The target resource name is set by default to match the service kind, such as postgresql, mysql, mongo.
For named datasources, the name of the datasource is used.
For named mongo clients, the name of the client is used.

Example 1 - Name mismatch

For cases in which you need to modify the generated ServiceBinding to fix a name mismatch, use the quarkus.kubernetes-service-binding.services properties and specify the service’s name as the service key.

The service key is usually the name of the service, for example the name of the datasource, or the name of the mongo client. When this value is not available, the datasource type, such as postgresql, mysql, mongo, is used instead.

To avoid naming conflicts between different types of services, prefix the service key with a specific datasource type, such as postgresql-<person>.

The following example shows how to customize the apiVersion property of the PostgresCluster resource:

quarkus.datasource.db-kind=postgresql
quarkus.kubernetes-service-binding.services.postgresql.api-version=postgres-operator.crunchydata.com/v1beta2

Example 2: Application of a custom name for a datasource

In Example 1, the db-kind(postgresql) was used as a service key. In this example, because the datasource is named, according to convention, the datasource name (fruits-db) is used instead.

The following example shows that for a named datasource, the datasource name is used as the name of the target resource:

quarkus.datasource.fruits-db.db-kind=postgresql

This has the same effect as the following configuration:

quarkus.kubernetes-service-binding.services.fruits-db.api-version=postgres-operator.crunchydata.com/v1beta1
quarkus.kubernetes-service-binding.services.fruits-db.kind=PostgresCluster
quarkus.kubernetes-service-binding.services.fruits-db.name=fruits-db

Additional resources

For more details about the available properties and how do they work, see the Workload Projection part of the Service Binding specification.

先决条件
Kubernetes
Tuning the generated resources using application.properties
Deployment
Using existing resources
- Using common resources
Service Binding
- Workload Projection
Introduction to the Service Binding Operator

Kubernetes extension

先决条件

Kubernetes

Generating idempotent resources

Changing the generated deployment resource

Generating Job resources

Generating CronJob resources

Namespace

Defining a Docker registry

Automatic generation of pull secrets

Labels and Annotations

Labels

Custom Labels

Annotations

Custom Annotations

Environment variables

Environment variables from key/value pairs

Environment variables from Secret

Environment variables from ConfigMap

Environment variables from fields

Validation

Backwards compatibility

Mounting volumes

Secret volumes

ConfigMap volumes

Passing application configuration

Changing the number of replicas

Add readiness and liveness probes

Customizing the readiness probe

Add hostAliases

Container Resources Management

Exposing your application in Kubernetes

Adding Ingress rules

Securing the Ingress resource

Using the Kubernetes client

Generating RBAC resources

Deploying to local Kubernetes

Deploying to Minikube

Deploying to Kind

Tuning the generated resources using application.properties

Configuration options

Client Connection Configuration

OpenShift

Knative

Deployment targets

Deprecated configuration

Properties without the quarkus prefix

Docker and S2i properties

Config group arrays

env-vars properties

Deployment

Building a container image

Deploying

Remote Debugging

Using existing resources

Using common resources

Service Binding

Workload Projection

Introduction to the Service Binding Operator

Semi-automatic service binding

Automatic service binding

Automatic datasource binding

Customizing Automatic Service Binding

Related content

On the same extensions

On the same topics

`env-vars` properties