Kubernetes Release Manager

17 Results

• annotationsOptionalmap of string to stringmap of string to string

  Annotations to be applied to the kube service

• contextOptionalstringstring

  the kubectl context to use, as defined in the kubeconfig file

• ingressOptionalcategorycategory

  Configuration to set up an ingress resource to route traffic to the given application from an ingress controller An ingress resource can be created on release that will route traffic to the Kubernetes service. Note that before this happens, the Kubernetes cluster must already be configured with an Ingress controller. Otherwise there won't be a way for inbound traffic to be routed to the ingress resource.

  ---

  • ingress.annotationsOptionalmap of string to stringmap of string to string

    Annotations to be applied to the ingress resource

  • ingress.defaultOptionalboolbool

    sets the ingress resource to be the default backend for any traffic that doesn't match existing ingress rule paths

  • ingress.hostOptionalstringstring

    If set, will configure the ingress resource to have the ingress controller route traffic for any inbound requests that match this host. IP addresses are not allowed, nor are ':' delimiters. Wildcards are allowed to a certain extent. For more details check out the Kubernetes documentation

  • ingress.pathOptionalstringstring

    The route rule that should be used to route requests to this ingress resource. A path must begin with a '/'.

  • ingress.path_typeOptionalstringstring

    defines the kind of rule the path will be for the ingress controller. Valid path types are 'Exact', 'Prefix', and 'ImplementationSpecific'.

  • ingress.tlsOptionalcategorycategory

    A stanza of TLS configuration options for traffic to the ingress resource

    • ingress.tls.hostsRequired

      A list of hosts included in the TLS certificate

    • ingress.tls.secret_nameRequired

      The Kubernetes secret name that should be used to look up or store TLS configs

• kubeconfigOptionalstringstring

  path to the kubeconfig file to use by default uses from current user's home directory

• load_balancerOptionalboolbool

  indicates if the Kubernetes Service should LoadBalancer type if the Kubernetes Service is not a LoadBalancer and node_port is not set, then the Service uses ClusterIP

• namespaceOptionalstringstring

  namespace to create Service in namespace is the name of the Kubernetes namespace to create the deployment in This is useful to create Services in non-default namespaces without creating kubeconfig contexts for each

• node_portOptionaluintuint

  the TCP port that the Service should consume as a NodePort if this is set but load_balancer is not, the service will be NodePort type, but if load_balancer is also set, it will be LoadBalancer

• portOptionaluintuint

  the TCP port that the application is listening on

• portsOptionallist of map of string to stringlist of map of string to string

  a map of ports and options that the application is listening on used to define and configure multiple ports that the application is listening on. Available keys are 'port', 'node_port', 'name', and 'target_port'. If 'node_port' is set but 'load_balancer' is not, the service will be NodePort type. If 'load_balancer' is also set, it will be LoadBalancer. Ports defined will be TCP protocol. Note that 'name' is required if defining more than one port.