Skip to content

Instantly share code, notes, and snippets.

@rainest
Last active November 22, 2023 16:03
Show Gist options
  • Save rainest/947b9a957660dfb1a713eb6cd41a6184 to your computer and use it in GitHub Desktop.
Save rainest/947b9a957660dfb1a713eb6cd41a6184 to your computer and use it in GitHub Desktop.
kong chart 3.x migration
10:35:48-0500 esenin $ helm upgrade --install ana kong/ingress
Release "ana" does not exist. Installing it now.
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:36:05 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
10:36:06-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-controller-7dd6cfd48-ldvmc 0/1 Running 0 9s
ana-gateway-dd7cc786d-44stz 0/1 Running 0 9s
10:36:15-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-controller-7dd6cfd48-ldvmc 1/1 Running 0 25s
ana-gateway-dd7cc786d-44stz 0/1 Running 0 25s
10:36:31-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-controller-7dd6cfd48-ldvmc 1/1 Running 0 32s
ana-gateway-dd7cc786d-44stz 1/1 Running 0 32s
10:36:38-0500 esenin $ helm upgrade --install ana rainestcharts/kong
Release "ana" has been upgraded. Happy Helming!
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:36:44 2023
NAMESPACE: default
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
PORT=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.spec.ports[0].port}')
export PROXY_IP=${HOST}:${PORT}
curl $PROXY_IP
Once installed, please follow along the getting started guide to start using
Kong: https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/getting-started/
10:36:46-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-gateway-dd7cc786d-44stz 1/1 Terminating 0 43s
ana-kong-59b996d844-ndddw 0/1 Running 0 4s
ana-kong-controller-867568756-2s2lh 0/1 Running 0 4s
10:36:49-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-gateway-dd7cc786d-44stz 1/1 Terminating 0 53s
ana-kong-59b996d844-ndddw 0/1 Running 0 14s
ana-kong-controller-867568756-2s2lh 1/1 Running 0 14s
10:36:59-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-kong-59b996d844-ndddw 0/1 Running 0 18s
ana-kong-controller-867568756-2s2lh 1/1 Running 0 18s
10:37:03-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-kong-59b996d844-ndddw 0/1 Running 0 28s
ana-kong-controller-867568756-2s2lh 1/1 Running 0 28s
10:37:13-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-kong-59b996d844-ndddw 1/1 Running 0 37s
ana-kong-controller-867568756-2s2lh 1/1 Running 0 37s
11:01:09-0500 esenin $ helm upgrade --install ana kong/ingress
Release "ana" does not exist. Installing it now.
NAME: ana
LAST DEPLOYED: Wed Nov 22 11:01:11 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
11:01:12-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-controller-7dd6cfd48-ns2xl 1/1 Running 0 2m11s 10.244.0.64 kind-control-plane <none> <none>
ana-gateway-dd7cc786d-dqkh7 1/1 Running 0 24s 10.244.0.68 kind-control-plane <none> <none>
11:01:36-0500 esenin $ kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
ana-controller 1/1 1 1 2m23s
ana-gateway 1/1 1 1 36s
11:01:48-0500 esenin $ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ana-controller-validation-webhook ClusterIP 10.96.254.119 <none> 443/TCP 2m24s
ana-gateway-admin ClusterIP None <none> 8444/TCP 37s
ana-gateway-manager NodePort 10.96.122.39 <none> 8002:32675/TCP,8445:32004/TCP 37s
ana-gateway-proxy LoadBalancer 10.96.49.175 172.19.128.1 80:31948/TCP,443:30045/TCP 37s
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 44m
11:01:49-0500 esenin $ helm upgrade --install ana rainestcharts/kong --set nameOverride=gateway --set admin.type=ClusterIP
Release "ana" has been upgraded. Happy Helming!
NAME: ana
LAST DEPLOYED: Wed Nov 22 11:02:14 2023
NAMESPACE: default
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-gateway-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
PORT=$(kubectl get svc --namespace default ana-gateway-proxy -o jsonpath='{.spec.ports[0].port}')
export PROXY_IP=${HOST}:${PORT}
curl $PROXY_IP
Once installed, please follow along the getting started guide to start using
Kong: https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/getting-started/
11:02:15-0500 esenin $ kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
ana-gateway 1/1 1 1 73s
ana-gateway-controller 0/1 1 0 10s
11:02:25-0500 esenin $ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ana-gateway-admin ClusterIP None <none> 8444/TCP 87s
ana-gateway-manager NodePort 10.96.122.39 <none> 8002:32675/TCP,8445:32004/TCP 87s
ana-gateway-proxy LoadBalancer 10.96.49.175 172.19.128.1 80:31948/TCP,443:30045/TCP 87s
ana-gateway-validation-webhook ClusterIP 10.96.11.167 <none> 443/TCP 24s
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 44m
11:02:39-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-gateway-69794955f7-77h95 1/1 Running 0 33s 10.244.0.70 kind-control-plane <none> <none>
ana-gateway-controller-9bd746c98-fcmjc 1/1 Running 0 33s 10.244.0.69 kind-control-plane <none> <none>
ana-gateway-dd7cc786d-dqkh7 1/1 Terminating 0 96s 10.244.0.68 kind-control-plane <none> <none>
10:39:56-0500 esenin $ helm upgrade --install ana kong/kong --set admin.enabled=true
Release "ana" does not exist. Installing it now.
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:40:08 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
PORT=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.spec.ports[0].port}')
export PROXY_IP=${HOST}:${PORT}
curl $PROXY_IP
Once installed, please follow along the getting started guide to start using
Kong: https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/getting-started/
10:40:09-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-kong-54c66d7f69-tg55s 2/2 Running 0 31s 10.244.0.22 kind-control-plane <none> <none>
10:40:40-0500 esenin $ helm upgrade --install ana rainestcharts/kong
Release "ana" has been upgraded. Happy Helming!
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:40:51 2023
NAMESPACE: default
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
PORT=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.spec.ports[0].port}')
export PROXY_IP=${HOST}:${PORT}
curl $PROXY_IP
Once installed, please follow along the getting started guide to start using
Kong: https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/getting-started/
10:40:52-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-kong-54c66d7f69-tg55s 2/2 Running 0 65s 10.244.0.22 kind-control-plane <none> <none>
ana-kong-59b996d844-zcjgf 0/1 Running 0 22s 10.244.0.24 kind-control-plane <none> <none>
ana-kong-controller-867568756-xjmjb 1/1 Running 0 22s 10.244.0.23 kind-control-plane <none> <none>
10:41:14-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-kong-54c66d7f69-tg55s 2/2 Running 0 73s 10.244.0.22 kind-control-plane <none> <none>
ana-kong-59b996d844-zcjgf 0/1 Running 0 30s 10.244.0.24 kind-control-plane <none> <none>
ana-kong-controller-867568756-xjmjb 1/1 Running 0 30s 10.244.0.23 kind-control-plane <none> <none>
10:41:22-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-kong-54c66d7f69-tg55s 2/2 Terminating 0 86s 10.244.0.22 kind-control-plane <none> <none>
ana-kong-59b996d844-zcjgf 1/1 Running 0 43s 10.244.0.24 kind-control-plane <none> <none>
ana-kong-controller-867568756-xjmjb 1/1 Running 0 43s 10.244.0.23 kind-control-plane <none> <none>
10:41:35-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-kong-59b996d844-zcjgf 1/1 Running 0 51s 10.244.0.24 kind-control-plane <none> <none>
ana-kong-controller-867568756-xjmjb 1/1 Running 0 51s 10.244.0.23 kind-control-plane <none> <none>
10:19:24-0500 esenin $ helm upgrade --install ana kong/kong
Release "ana" does not exist. Installing it now.
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:19:36 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
10:38:22-0500 esenin $ helm upgrade --install ana kong/kong
Release "ana" does not exist. Installing it now.
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:38:31 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
PORT=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.spec.ports[0].port}')
export PROXY_IP=${HOST}:${PORT}
curl $PROXY_IP
Once installed, please follow along the getting started guide to start using
Kong: https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/getting-started/
10:38:32-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-kong-6577d87cdb-smg5v 2/2 Running 0 11s
10:38:43-0500 esenin $ helm upgrade --install ana rainestcharts/kong
Release "ana" has been upgraded. Happy Helming!
NAME: ana
LAST DEPLOYED: Wed Nov 22 10:38:51 2023
NAMESPACE: default
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
To connect to Kong, please execute the following commands:
HOST=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
PORT=$(kubectl get svc --namespace default ana-kong-proxy -o jsonpath='{.spec.ports[0].port}')
export PROXY_IP=${HOST}:${PORT}
curl $PROXY_IP
Once installed, please follow along the getting started guide to start using
Kong: https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/getting-started/
10:38:52-0500 esenin $ kubectl get po
NAME READY STATUS RESTARTS AGE
ana-kong-59b996d844-dh6vv 0/1 Running 0 5s
ana-kong-6577d87cdb-smg5v 2/2 Running 0 25s
ana-kong-controller-867568756-7pxqc 0/1 Running 0 5s
10:38:57-0500 esenin $ kubectl get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ana-kong-59b996d844-dh6vv 0/1 Running 0 15s 10.244.0.21 kind-control-plane <none> <none>
ana-kong-6577d87cdb-smg5v 2/2 Running 0 35s 10.244.0.19 kind-control-plane <none> <none>
ana-kong-controller-867568756-7pxqc 0/1 Running 0 15s 10.244.0.20 kind-control-plane <none> <none>
10:39:07-0500 esenin $ kubectl logs ana-kong-controller-867568756-7pxqc | tail
2023-11-22T15:39:05Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "13/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:06Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "14/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:07Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "15/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:08Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "16/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:09Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "17/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:10Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "18/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:11Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "19/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:12Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "20/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:13Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "21/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
2023-11-22T15:39:14Z info setup Retrying kong admin api client call after error {"v": 0, "retries": "22/60", "error": "making HTTP request: Get \"https://10.244.0.19:8444/\": dial tcp 10.244.0.19:8444: connect: connection refused"}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment