aqua
ingress-nginx
aqua | ingress-nginx | |
---|---|---|
19 | 203 | |
707 | 16,664 | |
4.7% | 0.7% | |
9.9 | 9.6 | |
2 days ago | 8 days ago | |
Go | Go | |
- | 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.
aqua
- Aqua – Declarative CLI Version Manager Written in Go
- Aqua – Declarative CLI Version Manager
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
Instead I use https://github.com/aquaproj/aqua.
- Aqua: Declarative CLI Version Manager
-
Update of aqua CLI Version Manager in 2022
In this post, I describe the update of aqua in 2022.
- Checksum Verification by aqua
-
Long time zinit user looking to trim down my configuration while maintaining easy plugin/binary setup
Aqua is a packaging tool that I'm testing out. Very interesting conceptually, and if you like chezmoi (I use it, too), then I think you'll find it worth a peek.
-
aqua supports building tools with Go
$ aqua init $ aqua g -i mitchellh/gox $ cat aqua.yaml --- # aqua - Declarative CLI Version Manager # https://aquaproj.github.io/ registries: - type: standard ref: v2.19.0 # renovate: depName=aquaproj/aqua-registry packages: - name: mitchellh/[email protected] $ aqua i INFO[0000] create a symbolic link aqua_version=1.9.0 env=darwin/arm64 link_file=/Users/shunsukesuzuki/.local/share/aquaproj-aqua/bin/gox new=aqua-proxy package_name=mitchellh/gox package_version=v1.0.1 program=aqua registry=standard registry_ref=v2.19.0 INFO[0000] download and unarchive the package aqua_version=1.9.0 env=darwin/arm64 package_name=mitchellh/gox package_version=v1.0.1 program=aqua registry=standard registry_ref=v2.19.0 INFO[0000] building Go tool aqua_version=1.9.0 env=darwin/arm64 exe_path=/Users/shunsukesuzuki/.local/share/aquaproj-aqua/pkgs/go/github.com/mitchellh/gox/v1.0.1/bin/gox file_name=gox go_build_dir=/Users/shunsukesuzuki/.local/share/aquaproj-aqua/pkgs/go/github.com/mitchellh/gox/v1.0.1/src/gox-1.0.1 go_src=. package_name=mitchellh/gox package_version=v1.0.1 program=aqua registry=standard registry_ref=v2.19.0 go: downloading github.com/hashicorp/go-version v1.0.0 go: downloading github.com/mitchellh/iochan v1.0.0
- Aqua – Declarative CLI Version Manager. Install Tools Easily and Quickly
-
tfcmt - Improve Terraform Workflow with PR Comment and Label
For the version control, we recommend aqua.
ingress-nginx
-
Automating EKS Deployment and NGINX Setup Using Helm with AWS CDK in Python
# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )
-
deploying a minio service to kubernetes
ingress-nginx
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
[06/52] Accessible Kubernetes with Terraform and DigitalOcean
resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }
-
Deploy Ghost with MySQL DB replication using helm chart
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml
-
Kubernetes Gateway API v1.0: Should You Switch?
For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.
- nginx ingress controller installation
-
IP-Whitlisting: Is adjusting nginx-ingress-controller service a solution?
The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list
-
☸️ Kubernetes NGINX Ingress Controller: 10+ Complementary Configurations for Web Applications
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
What are some alternatives?
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
traefik - The Cloud Native Application Proxy
github-action
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
mise - dev tools, env vars, task runner
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
renovate-approve
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
json5-spec - The JSON5 Data Interchange Format
haproxy-ingress - HAProxy Ingress
github-comment - CLI to create and hide GitHub comments
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.