understanding flux build command line

With flux build cli we can try to do a dry-run to see how the yaml gets generated without doing actual deployment. --path is a bases template of your deployment. Then --kustomization-file  is the overlay (cherry on top) or customization that you would like to add on top of your --path base template.  The command line looks like this. ./cluster/devtest/external-dns must exist. 



flux build kustomization external-dns \

  --path ./clusters/devtest/external-dns \

  --kustomization-file ./clusters/devtest/external-dns-ks.yaml \

  --dry-run


./cluster/devtest/external-dns/kustomization.yaml



apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: kube-system
resources:
  - release.yaml

./cluster/devtest/external-dns/release.yaml

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: keda
  namespace: keda
spec:
  releaseName: keda
  targetNamespace: keda
  chart:
    spec:
      chart: keda
      sourceRef:
        kind: HelmRepository
        name: keda
        namespace: flux-system
      version: "2.18.3"
  interval: 5m0s
  install:
    remediation:
      retries: 3
    crds: CreateReplace
  upgrade:
    crds: CreateReplace
  values:
    prometheus:
      metricServer:
        enabled: true
        port: 3000
        path: /metrics
    tolerations:
    - key: CriticalAddonsOnly
      operator: Exists

 ./clusters/devtest/external-dns-ks.yaml - this are further customization that you want to make on your based template.


apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: external-dns
  namespace: flux-system
spec:
  interval: 5m0s
  dependsOn:
    - name: sources
  path: ./clusters/wwnzdevtest/external-dns
  prune: true
  sourceRef:
    kind: GitRepository
    name: flux-system
  patches:
  - patch: |-
      apiVersion: helm.toolkit.fluxcd.io/v2
      kind: HelmRelease
      metadata:
        name: external-dns
      spec:
        values:
          resources:
            requests:
              cpu: 350m
            limits:
              cpu: 550m
          sources:
          - service
    target:
      kind: HelmRelease
     

And the final output would look something like this, it looks like it has been merged.



https://fluxcd.io/flux/components/helm/helmreleases/





Comments

Post a Comment

Popular posts from this blog

mongosh install properly

To install mongosh property on ubuntu 24.04, we need to wget -qO- https://www.mongodb.org/static/pgp/server-8.0.asc | sudo tee /etc/apt/trusted.gpg.d/server-8.0.asc Then run  echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu noble/mongodb-org/8.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-8.0.list Next we will run  sudo apt-get update And then finally install it using  sudo apt-get install -y mongodb-mongosh To verify if it is running we run  mongosh --version
Read more

gemini cli getting file not defined error

Image
 While trying to run gemini cli on my windows linux subsystem, i bump into this error here - "/Roaming/npm/node_modules/@google/gemini-cli/node_modules/undici/lib/web/webidl/index.js:512 webidl.is.File = webidl.util.MakeTypeAssertion(File)"  "ReferenceError: File is not defined" In Node.js, there’s no built-in File (until very recent Node 20+ with experimental WHATWG APIs). So, unless polyfilled, File is undefined, leading to the ReferenceError. And to resolve this, I had to upgrade to node 22 (might work for node 20) and then I was able to run it.
Read more

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more