Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

🦍 Kong for Kubernetes: The official Ingress Controller for Kubernetes.

License

NotificationsYou must be signed in to change notification settings

Kong/kubernetes-ingress-controller

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

kong-logoBuild StatusGo ReferenceCodecovLicenseTwitterConformance

Kong Ingress Controller for Kubernetes (KIC)

UseKong for KubernetesGateway API orIngress.Configureplugins, health checking,load balancing and more, all usingCustom Resource Definitions (CRDs) and Kubernetes-native tooling.

Features |Get started |Documentation |main branch builds |Seeking help

Features

  • Gateway API supportUseGateway API resources (official successor ofIngress resources) to configure Kong.Native support for TCP, UDP, TLS, gRPC and HTTP/HTTPS traffic, reuse the same gateway for multiple protocols and namespaces.
  • Ingress supportUseIngress resources to configure Kong.
  • Declarative configuration for KongConfigure all of Kong features in declarative Kubernetes native way with CRDs.
  • Seamlessly operate KongScale and manage multiple replicas of Kong Gateway automatically to ensure performance and high-availability.
  • Health checking and load-balancingLoad balance requests across your pods and supports active & passive health-checks.
  • Enhanced API management using pluginsUse a wide array ofplugins for e.g.
    • authentication
    • request/response transformations
    • rate-limiting

Get started (using Helm)

You can useMinikube or Kind on your local machine or usea hosted Kubernetes service likeGKE.

Install the Gateway API CRDs

This command will install all resources that have graduated to GA or beta,includingGatewayClass,Gateway,HTTPRoute, andReferenceGrant.

kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml

Or, if you want to use experimental resources and fields such asTCPRoutes andUDPRoutes,please run this command.

kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/experimental-install.yaml

Install the Kong Ingress Controller with Helm

helm install kong --namespace kong --create-namespace --repo https://charts.konghq.com ingress

To learn more details about Helm chart follow theHelm chart documentation.

Once installed, please follow theGetting Started guideto start using Kong in your Kubernetes cluster.

Note: Kong Enterprise users, please follow along with ourenterprise guide to setup the enterprise version.

Get started (using Operator)

As an alternative to Helm, you can also install Kong Ingress Controller using theKong Gateway Operator by following thisquick start guide.

Container images

Release images

Release builds of Kong Ingress Controller can be found on Docker Hub inkong/kubernetes-ingress-controller repository.

At the moment we're providing images for:

  • Linuxamd64
  • Linuxarm64

main branch builds

Nightly pre-release builds of themain branch are available from thekong/nightly-ingress-controller repository hosted on Docker Hub:

main contains unreleased new features for upcoming minor and major releases:

docker pull kong/nightly-ingress-controller:nightly

Documentation

All documentation for the Kong Ingress Controller is present in thekong/docs.konghq.com repository. Pull Requests are welcome for additions and corrections.

Guides and Tutorials

Please browse through theguides to get started and to learn specific ingress controller operations.

Contributing

We ❤️ pull requests and we’re continually working hard to make it as easy as possible for developers to contribute.Before beginning development with the Kong Ingress Controller, please familiarize yourself with the following developer resources:

Seeking help

Please search through theFAQs, posts on thediscussions page or theKong Nation Forumsas it's likely that another user has run into the same problem.If you don't find an answer, please feel free to post a question.

If you've found a bug, pleaseopen an issue.

For a feature request, please open an issue using the feature request template.

You can also talk to the developers behind Kong in the#kong channel on the Kubernetes Slack server.

Community meetings

You can join monthly meetups hosted byKong to ask questions, provide feedback, or just to listen and hang out.See theOnline Meetups Page to sign up and receive meeting invites andZoom links.

Preview and Experimental Features

At any time the KIC may include features or options that are consideredexperimental and are not enabled by default, nor available in theKongDocumentation Site.

To try out new features that are behind feature gates, please see thepreview features inFEATURE_GATES.md and documentation for thesepreview features can be found inFEATURE_PREVIEW_DOCUMENTATION.md.


[8]ページ先頭

©2009-2025 Movatter.jp