fluxcd example of deploying keda charts helm release with value files from another repository

This is a typical setup for everyone trying to use helm to deploy keda. This deploy keda using chart. A twist to that is getting our values files from another repository. In this setup, we will do this.

Given helmrelease in flux won't be able to read value files directly, we use kustomization.

 

You can get access to the file here

https://github.com/kepungnzai/keda-flux-chart-demo/blob/main/README.md

Value files repository :- https://github.com/kepungnzai/keda-aks-deploy



So you need to run the following in sequence (important) 

kubectl apply -f keda-values-gitrepo.yaml

kubectl apply -f keda-values-kustomization.yaml

kubectl apply -f keda-helmrepo.yaml

kubectl apply -f keda-helmrelease.yaml


keda-values-gitrepo.yaml


apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: keda-values
  namespace: flux-system
spec:
  interval: 1m
  url: https://github.com/kepungnzai/keda-aks-deploy
  ref:
    branch: main


keda-values-kustomization.yaml

apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: keda-values
  namespace: flux-system
spec:
  interval: 5m
  sourceRef:
    kind: GitRepository
    name: keda-values
  path: ./keda
  prune: true
  targetNamespace: keda


keda-helmrepo.yaml

apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmRepository
metadata:
  name: kedacore
  namespace: flux-system
spec:
  interval: 1h
  url: https://kedacore.github.io/charts

keda-helmrelease.yaml

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: keda
  namespace: keda
spec:
  interval: 5m
  releaseName: keda

  chart:
    spec:
      chart: keda
      version: "2.14.0"
      sourceRef:
        kind: HelmRepository
        name: kedacore
        namespace: flux-system

  install:
    createNamespace: true

  upgrade:
    remediation:
      retries: 3

  valuesFrom:
    - kind: ConfigMap
      name: keda-values
      valuesKey: values.yaml

You can see keda is being deployed


And then to check out other resources 





Comments

Post a Comment

Popular posts from this blog

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

android studio kotlin source is null error

Image
This org.jetbrains.kotlin.util.FileAnalysisException with a java.lang.IllegalArgumentException: source must not be null is a known issue that can sometimes occur with the Kotlin compiler. It seems to be related to how the compiler analyzes certain source code structures. When this happens, you need to go clean your project and do another rebuild.  For my case, I was trying to test out the databinding = true feature. 
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