Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to integrate Kong Gateway #168

Open
nth347 opened this issue Feb 3, 2025 · 1 comment
Open

Failed to integrate Kong Gateway #168

nth347 opened this issue Feb 3, 2025 · 1 comment
Labels
kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this

Comments

@nth347
Copy link

nth347 commented Feb 3, 2025

Kuma Version

Kuma 2.9.3 on Kubernetes

Describe the bug

I ran: kubectl apply -f https://bit.ly/demokumakong
And ran kubectl get pods -n kuma-demo -w to check the pods, the ingress-kong-* pod is in either ErrImagePull or ImagePullBackOff, never get to Running state

ubuntu@ubuntu:~$ kubectl get pods -n kuma-demo -w
NAME                                    READY   STATUS             RESTARTS   AGE
ingress-kong-5bd4f5bc64-ht42j           2/3     ImagePullBackOff   0          10m
kuma-demo-app-55958849b8-cn5d7          2/2     Running            0          13m
kuma-demo-backend-v0-56d4fddfbb-4n57p   2/2     Running            0          13m
postgres-master-759b4cf6f5-gfzjb        2/2     Running            0          13m
redis-master-6dd64964c-xztjk            2/2     Running            0          13m
ingress-kong-5bd4f5bc64-ht42j           2/3     ErrImagePull       0          13m
ingress-kong-5bd4f5bc64-ht42j           2/3     ImagePullBackOff   0          13m

To Reproduce

Here is the full output:

ubuntu@ubuntu:~$ kubectl apply -f https://bit.ly/demokumakong
serviceaccount/kong-serviceaccount created
configmap/kong-server-blocks created
service/kong-proxy created
service/kong-validation-webhook created
deployment.apps/ingress-kong created
resource mapping not found for name: "kongclusterplugins.configuration.konghq.com" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "kongconsumers.configuration.konghq.com" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "kongcredentials.configuration.konghq.com" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "kongingresses.configuration.konghq.com" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "kongplugins.configuration.konghq.com" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "tcpingresses.configuration.konghq.com" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "kong-ingress-clusterrole" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "kong-ingress-clusterrole-nisa-binding" namespace: "" from "https://bit.ly/demokumakong": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first


ubuntu@ubuntu:~$ kubectl get pods -n kuma-demo -w
NAME                                    READY   STATUS             RESTARTS   AGE
ingress-kong-5bd4f5bc64-ht42j           2/3     ImagePullBackOff   0          10m
kuma-demo-app-55958849b8-cn5d7          2/2     Running            0          13m
kuma-demo-backend-v0-56d4fddfbb-4n57p   2/2     Running            0          13m
postgres-master-759b4cf6f5-gfzjb        2/2     Running            0          13m
redis-master-6dd64964c-xztjk            2/2     Running            0          13m
ingress-kong-5bd4f5bc64-ht42j           2/3     ErrImagePull       0          13m
ingress-kong-5bd4f5bc64-ht42j           2/3     ImagePullBackOff   0          13m

Expected behavior

No response

Additional context (optional)

Version details:

ubuntu@ubuntu:~$ kubectl version
Client Version: v1.31.5
Kustomize Version: v5.4.2
Server Version: v1.32.0
ubuntu@ubuntu:~$ 
@nth347 nth347 added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels Feb 3, 2025
@bartsmykla bartsmykla added triage/needs-reproducing Someone else should try to reproduce this and removed triage/pending This issue will be looked at on the next triage meeting labels Feb 3, 2025
@nth347
Copy link
Author

nth347 commented Feb 4, 2025

hello @bartsmykla , have a good day! I followed the guide in https://github.com/kumahq/kuma-demo/tree/master/kubernetes and the error is thrown, what do you mean needs-reproducing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this
Projects
None yet
Development

No branches or pull requests

2 participants