helm-charts
Jenkins helm charts (by jenkinsci)
opta
The next generation of Infrastructure-as-Code. Work with high-level constructs instead of getting lost in low-level cloud configuration. (by run-x)
Our great sponsors
helm-charts | opta | |
---|---|---|
7 | 18 | |
539 | 907 | |
2.8% | 0.1% | |
9.0 | 0.0 | |
8 days ago | about 1 year ago | |
Mustache | Python | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
helm-charts
Posts with mentions or reviews of helm-charts.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-07-28.
-
Why is argocd complaining about my ApplicationSet saying: error parsing value as string <nil>
I have no clue of what is wrong. The applicationset yaml looks like (somewhat cut-down): apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myjenkins namespace: argocd spec: generators: - list: elements: - namespace: "development" ingressHostName: "myjenkins-dev.scs.domain" limitsMemory: "12Gi" template: metadata: name: myjenkins spec: destination: namespace: '{{namespace}}' server: https://kubernetes.default.svc project: default syncPolicy: {} sources: - chart: jenkins repoURL: https://github.com/jenkinsci/helm-charts/tree/main/charts targetRevision: 4.3.9 helm: releaseName: myjenkins parameters: - name: extraLabels value: slice1 - name: controller.resources.limits.cpu value: '8' - name: controller.resources.limits.memory value: '{{limitsMemory}}' valueFiles: - $values/deployments/jenkins/global/common.values - $values/deployments/jenkins/global/shared-libs.values - $values/deployments/jenkins/global/job-dsl-seed.values - $values/deployments/jenkins/global/ssh-credentials.values - $values/deployments/jenkins/global/kubernetes-cloud.values - repoURL: 'ssh://[email protected]:29418/kubernetes' targetRevision: master ref: values
-
Jenkins CASC and Jenkins Community helm chart issues
Here is what I'm deploying.. I have a very small GKE cluster up and running right now with terraform. I'm on a budget, so I'm trying to containerize as many of the services we need for development as possible. I am using this Jenkins helm chart for deployment: https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/README.md
- Deploying Jenkins on Google Cloud
-
Jenkins on Kubernetes - Can't Use PodTemplates Defined In Clouds
I've updated my post with the error logs and some descriptions. The "Additional Agents" thing is part of the Helm chart. The Adding Pod Templates Using additionalAgents section of the Helm Chart's README gives an example of how to declare them. I initially tried using a direct copy of the example in the README (adapted to use with the Ansible module) but that displayed roughly the same behaviour
-
Should we be using Jenkins for our Kubernetes CI/CD pipeline needs in 2021?
https://github.com/jenkinsci/helm-charts/tree/main/charts/jenkins Using offical chart
- Battle-tested way to configure a Jenkins server on AWS using IaC/CaC?
opta
Posts with mentions or reviews of opta.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-07-28.
-
Discussion: Terraform usability and documentation has declined considerably in the past several years
Shamless plug here for Opta, the open-source abstraction for Infrastructure-as-code. It builds on Terraform to make modularization a lot easier. https://github.com/run-x/opta
- run-x/opta: Infrastructure-as-code where you work with high-level constructs instead of getting lost in low level cloud configuration
- deploy NocoDB on AWS with the open source Infrastructure-as-code tool Opta (sorry the banner image looks so bad, I'm a sysadmin not an artist)
- Running Minecraft on Kubernetes with Opta
- Opta, a high level abstraction for Infrastructure-as-Code
- Show HN: Opta, a high level abstraction for Infrastructure-as-Code
- Minecraft on a Kubernetes Cluster
- Deploying Minecraft to AWS
- Deploying Minecraft on k8s
What are some alternatives?
When comparing helm-charts and opta you can also consider the following projects:
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
charts - ⚠️(OBSOLETE) Curated applications for Kubernetes
kubernetes-operator - Kubernetes native Jenkins Operator
awesome-kubernetes - A curated list for awesome kubernetes projects, tools and resources.
terraform-provider-jenkins - Jenkins Terraform Provider
otp-gitops
optscale - FinOps and MLOps platform to run ML/AI and regular cloud workloads with optimal performance and cost.
kubernetes-plugin - Jenkins plugin to run dynamic agents in a Kubernetes/Docker environment
nebari - 🪴 Nebari - your open source data science platform
synapse
helm-charts - Helm chart repository containing the jenkins-infra public charts.
helm-charts vs actions-runner-controller
opta vs charts
helm-charts vs kubernetes-operator
opta vs awesome-kubernetes
helm-charts vs terraform-provider-jenkins
opta vs otp-gitops
helm-charts vs charts
opta vs optscale
helm-charts vs kubernetes-plugin
opta vs nebari
helm-charts vs synapse
helm-charts vs helm-charts