webui
kamus
Our great sponsors
webui | kamus | |
---|---|---|
3 | 3 | |
137 | 913 | |
- | 0.7% | |
3.0 | 0.0 | |
almost 2 years ago | 7 months ago | |
TypeScript | C# | |
Apache License 2.0 | Apache License 2.0 |
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.
webui
-
GitOps using Flux and Flagger
There is no UI for Flux. It does have an experimental UI that is not in an active development state at the time of writing this.
-
Automation assistants: GitOps tools in comparison
This allows the developer to analyze their deployments and correct errors all without having to access the cluster. For authentication , there are interfaces for common protocols, such as LDAP and OIDC. Via configurable roles and groups, users can granted access the projects and applications for which they are responsible. The developers of Flux v2 are currently working on a web interface. However, it is still in an experimental state.
-
Deploying to different namespaces via Jenkins in k8s (and secrets mgmt)
That's what I said: "I'm a Flux guy." I agree that Flux v2 is much better than Flux v1. But setting up ArgoCD is a drag. With Flux, you just run the CLI command and everything is committed to the repo and deployed in the cluster. Flux is only missing the UI but I think that this will change soon (https://github.com/fluxcd/webui).
kamus
-
helm upgrade error "Error: This command needs 2 arguments: release name, chart path"
I tried using the idea at https://stackoverflow.com/questions/54190837/helm-install-in-kuberneres-error-this-command-needs-2-arguments-release-name but it didn't help. Can you spot what I am doing wrong? Thank you.
- Open source, Git-ops, zero-trust secret encryption/decryption solution for K8s
-
Automation assistants: GitOps tools in comparison
Kamus may represent a compromise between Sealed Secrets and SOPS. It was created especially for the GitOps use case and includes an operator. It can either manage the key material itself or obtain it from the KMS of the cloud providers. Another special feature is that Kamus encrypts secrets directly for an application. They are then decrypted by the application itself or by an init container. This means that the unencrypted secret is never present on the API server and ideally also not in an environment variable with in the container.
What are some alternatives?
Flux - Successor: https://github.com/fluxcd/flux2
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
argo-cd - Declarative Continuous Deployment for Kubernetes
KMSpico - Microsoft Windows & Office activation tools (copy from internet)
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
sops - Simple and flexible tool for managing secrets
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)