argocd deploy keda helm chart with values files from a different repository

Argocd implementation is so much simpler compare to flux. All you need is to create an Application object and then configure the helm charts and where to get your value files. 

Please also note under the Application -> Spec -> sources -> helm -> valueFiles - i included the path there too. No additional row. Done. 

The only thing i need to do is create the keda namespace.


apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: keda-deployment
  namespace: argocd
spec:
  project: default
  destination:
    server: https://kubernetes.default.svc
    namespace: keda
  sources:
    # Source 1: The Helm Chart (e.g., KEDA)
    - repoURL: https://kedacore.github.io/charts
      chart: keda
      targetRevision: 2.15.0  # Use the specific chart version
      helm:
        valueFiles:
          # Reference the second source using $ + the 'ref' name
          - $values-repo/keda/values.yaml
   
    # Source 2: Your Git Repository containing the values file
    - repoURL: https://github.com/kepungnzai/keda-aks-deploy
      targetRevision: main
      ref: values-repo  # This name is used as the variable prefix above
 
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

And my keda is up and running








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