Kubee Kustomize Project Support

A Kubee Helmet chart supports kustomization project.

Project Structure

Your kustomization file:

• can reference Helm templates directly. They will be rendered before passing them to kustomize
• should be in the Chart project directory
• can include the ${KUBEE_NAMESPACE} environment variable. Why? To support this case

Example of Kustomization File

#file: noinspection KubernetesUnknownValues
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ${KUBEE_NAMESPACE}
patches:
  - path: templates/patches/secret-patch.yml
  - patch: |-
      - op: replace
        path: /subjects/0/namespace
        value: ${KUBEE_NAMESPACE}
    target:
      kind: ClusterRoleBinding
resources:
  - https://raw.githubusercontent.com/orga/project/xxx/manifests/install.yaml
  - templates/resources/ingress.yml

[!NOTE] Kustomize won’t let you have multiple resources with the same GVK, name, and namespace because it expects each resource to be unique. If a resource template reports an error, setting it as a patch template, may resolve the problem.

Example of Kustomization Project

Check the kubee-argocd chart for a kustomization example.