proxmox-k8s
gateway-api
proxmox-k8s | gateway-api | |
---|---|---|
7 | 30 | |
15 | 1,589 | |
- | 3.8% | |
0.0 | 9.8 | |
7 months ago | 4 days ago | |
Shell | 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.
proxmox-k8s
- Suggest container Linux distro go to deploy Kubernetes on a Bare Metal Server
-
My K8S installer now has an Ansible role for Proxmox
I've been working on a Kubernetes "installer" that creates an ISO derived from Fedora CoreOS that when booted from, installs Kubernetes. This can be found at https://github.com/alexpdp7/proxmox-k8s .
- Ansible playbook to provision a K8S cluster on Proxmox in about 10 minutes
- Personal project: a script to deploy a convenient single-node K8S cluster
- Suggestions for an Ingress controller
-
Single-node storage recommendations
So I'm setting up FCOS + k0S. I got the basic install working, but I don't have a fully operative setup.
- Which k8s are you using?
gateway-api
-
cert-manager: All-in-One Kubernetes TLS Certificate Manager
# cilium/playbook.yml - name: Bootstrap the Kubernetes cluster hosts: localhost gather_facts: false become: true environment: KUBECONFIG: ~/.kube/config vars: helm_version: v3.14.4 kube_context: k3d-k3s-default tasks: - name: Install Kubernetes library ansible.builtin.pip: name: kubernetes<30 state: present - name: Install helm binary ansible.builtin.shell: cmd: "{{ lookup('ansible.builtin.url', 'https://git.io/get_helm.sh', split_lines=false) }}" creates: /usr/local/bin/helm environment: DESIRED_VERSION: "{{ helm_version }}" - name: Install Kubernetes gateway CRDs kubernetes.core.k8s: src: "{{ item }}" state: present context: "{{ kube_context }}" loop: - https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml - https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/experimental-install.yaml - name: Install cilium block: - name: Add cilium helm repository kubernetes.core.helm_repository: name: cilium repo_url: https://helm.cilium.io - name: Install cilium helm release kubernetes.core.helm: name: cilium chart_ref: cilium/cilium namespace: kube-system state: present chart_version: 1.15.x kube_context: "{{ kube_context }}" values: gatewayAPI: enabled: true kubeProxyReplacement: true encryption: enabled: true type: wireguard operator: replicas: 1
-
ArgoCD Deployment on RKE2 with Cilium Gateway API
It has already been a couple of years since the Kubernetes Ingress was defined as a “frozen” feature while further development will be added to the Gateway API.
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
Kubernetes provides two APIs to achieve this, the Ingress API and the Gateway API.
-
Using k8s-apiserver as AAA server for microservices?
With all that said, K8s is not really meant to function as an API gateway to arbitrary services. You should look into API gateways such as NGINX, Kong or others, service meshes as others have already pointed out, or have a look at the K8s Gateway API the SIG is currently working on. The last one is in the early stages of adoption, but it could provide you with a nice way to do an API Gateway right in K8s.
-
load balancer and kubernetes
Maybe there's something in the new fangled gateways.
-
Service Mesh Considerations
Keep an eye on the Gateway API GAMMA Initiative as it is currently evolving with the goal of streamlining how services meshes can implement the Gateway API and reduce some overlap.
- EKS: is it possible to rewrite the URL with ALB?
-
Apache Apisix: Open-Source API Gateway and API Management Platform
The selling point for me was ability to configure it using Kubernetes CRD's and future support of the Gateway API (under development - <https://gateway-api.sigs.k8s.io/>).
Developers can version their API now within helm charts or even yaml templates held along the code in their repositories.
-
A quick glance at the Kubernetes Gateway API
-- https://gateway-api.sigs.k8s.io
-
Sharing load balancers between containers
While you're learning about ingresses, also look into the k8s Gateway API, which is the next generation. https://gateway-api.sigs.k8s.io/
What are some alternatives?
k3os - Purpose-built OS for Kubernetes, fully managed by Kubernetes.
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
apisix-opa-plugin
local-path-provisioner - Dynamically provisioning persistent local storage with Kubernetes
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
kairos - :penguin: The immutable Linux meta-distribution for edge Kubernetes.
tyk-operator - Tyk Operator for Kubernetes
os2 - EXPERIMENTAL: A Rancher and Kubernetes optimized immutable Linux distribution based on openSUSE
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
kusk-gateway - Kusk-gateway is an OpenAPI-driven API Gateway for Kubernetes
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes