Servicios de desarrollo para Kubernetes

Dev Services para Kubernetes se activa automáticamente a menos que:

Dev Services for Kubernetes relies on Docker to start the API server. If your environment does not support Docker, you will need to start the Kubernetes cluster manually, or connect to an already running Kubernetes cluster. You can configure the Kubernetes cluster access using either a Kube config file or the various properties available in the KubernetesClientBuildConfig class.

Most of the time you need to share the cluster between applications. Dev Services for Kubernetes implements a service discovery mechanism for your multiple Quarkus applications running in dev mode to share a single cluster.

If you need multiple (shared) clusters, you can configure the quarkus.kubernetes-client.devservices.service-name configuration property and indicate the cluster name. It looks for a container with the name defined, or starts a new one if none can be found. The default service name is kubernetes.

Sharing is enabled by default in dev mode, but disabled in test mode. You can disable the sharing with quarkus.kubernetes-client.devservices.shared=false.

Dev Services for Kubernetes provides three different flavors of Kubernetes cluster. Each flavor supports different Kubernetes API versions. You can configure the flavor and version using the quarkus.kubernetes-client.devservices.flavor and quarkus.kubernetes-client.devservices.api-version properties:

api-only sólo inicia un servidor API Kubernetes. Si necesita un clúster Kubernetes con todas las funciones que puede girar Pods, puede utilizar k3s o kind. Tenga en cuenta que ambos requieren para ejecutar en modo privilegiado Docker.

Si no se define api-version, se utilizará la versión más reciente para el tipo dado. De lo contrario, la versión debe coincidir con una versión soportada por el sabor dado.