kubernetes-ingress-controller icon indicating copy to clipboard operation
kubernetes-ingress-controller copied to clipboard

Published 20 hours ago • verified publisher icon Kong

KIC does not detect newly spawned Gateway Pods and prevents them from getting ready by not sending configuration

Open pmalek opened this issue 1 year ago • 4 comments

Problem statement

When Gateway deployment is being scaled, KIC can sometimes incorrectly not send the configuration to the newly spawned Gateway Pods thus preventing them from getting ready.

How to reproduce

  1. Deploy using ingress chart, values:
gateway:
  env:
    admin_listen: "0.0.0.0:8444 http2 ssl"
    router_flavor: "expressions"
    tracing_instrumentations: "all"
    tracing_sampling_rate: "1.0"
  manager:
    enabled: false
  replicaCount: 1
  readinessProbe:
    initialDelaySeconds: 1
    timeoutSeconds: 1
    periodSeconds: 1
  admin:
    type: LoadBalancer
  image:
    repository: kong/kong-gateway
    tag: "3.7"

controller:
  replicaCount: 1
  ingressController:
    image:
      tag: "3.2"

    env:
      dump_config: "true"
      dump_sensitive_config: "true"
      log_level: debug
      anonymous_reports: "false"
      kong_admin_tls_skip_verify: "true"
      enable_controller_kong_vault: "false"
      feature_gates: "GatewayAlpha=true,FallbackConfiguration=true"

    admissionWebhook:
      enabled: false
  1. Scale Gateway's deployment in and out. The reproduction rate is fairly low so this step might need to be repeated:
k scale deployment -n kong --replicas 1 kong-gateway; k scale deployment -n kong --replicas 5 kong-gateway

Anything else

Logs:

kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:01Z debug   No change in config status, not notifying       {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:01Z debug   Triggering report for configured Kubernetes objects     {"v": 1, "count": 0}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:01Z debug   events  successfully applied Kong configuration to https://10.244.0.13:8444     {"v": 1, "type": "Normal", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "KongConfigurationSucceeded"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:04Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:04Z debug   No configuration change; pushing config to gateway is not necessary, skipping   {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:07Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:07Z debug   No configuration change; pushing config to gateway is not necessary, skipping   {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:08Z debug   Reconciling readiness of gateway clients        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:08Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.13:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongAdminAPIService Notifying about newly detected Admin APIs       {"v": 1, "admin_apis": ["https://10.244.0.88:8444", "https://10.244.0.13:8444"]}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Received notification about Admin API addresses change  {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of pending client for "https://10.244.0.88:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.13:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Notifying subscribers about gateway clients change      {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongAdminAPIService Notifying about newly detected Admin APIs       {"v": 1, "admin_apis": ["https://10.244.0.13:8444", "https://10.244.0.88:8444", "https://10.244.0.86:8444"]}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Received notification about Admin API addresses change  {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of pending client for "https://10.244.0.86:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.13:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Already created client is not ready, moving to pending  {"v": 1, "address": "https://10.244.0.88:8444", "reason": "making HTTP request: Get \"https://10.244.0.88:8444/status\": dial tcp 10.244.0.88:8444: connect: connection refused"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.88:8444"     {"v": 1, "ok": false}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Notifying subscribers about gateway clients change      {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongAdminAPIService Notifying about newly detected Admin APIs       {"v": 1, "admin_apis": ["https://10.244.0.13:8444", "https://10.244.0.88:8444", "https://10.244.0.86:8444", "https://10.244.0.85:8444"]}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Received notification about Admin API addresses change  {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of pending client for "https://10.244.0.88:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of pending client for "https://10.244.0.85:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.13:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Already created client is not ready, moving to pending  {"v": 1, "address": "https://10.244.0.86:8444", "reason": "making HTTP request: Get \"https://10.244.0.86:8444/status\": dial tcp 10.244.0.86:8444: connect: connection refused"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.86:8444"     {"v": 1, "ok": false}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Notifying subscribers about gateway clients change      {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongAdminAPIService Notifying about newly detected Admin APIs       {"v": 1, "admin_apis": ["https://10.244.0.88:8444", "https://10.244.0.86:8444", "https://10.244.0.85:8444", "https://10.244.0.87:8444", "https://10.244.0.13:8444"]}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Received notification about Admin API addresses change  {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of pending client for "https://10.244.0.86:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of pending client for "https://10.244.0.87:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.13:8444"     {"v": 1, "ok": true}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Already created client is not ready, moving to pending  {"v": 1, "address": "https://10.244.0.88:8444", "reason": "making HTTP request: Get \"https://10.244.0.88:8444/status\": dial tcp 10.244.0.88:8444: connect: connection refused"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.88:8444"     {"v": 1, "ok": false}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Already created client is not ready, moving to pending  {"v": 1, "address": "https://10.244.0.85:8444", "reason": "making HTTP request: Get \"https://10.244.0.85:8444/status\": dial tcp 10.244.0.85:8444: connect: connection refused"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   setup.readiness-checker Checking readiness of already created client for "https://10.244.0.85:8444"     {"v": 1, "ok": false}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Notifying subscribers about gateway clients change      {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Parsing kubernetes objects into data-plane configuration        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Successfully built data-plane configuration     {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Sending configuration to gateway clients        {"v": 1, "urls": ["https://10.244.0.87:8444", "https://10.244.0.13:8444", "https://10.244.0.86:8444"]}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Shipping config to diagnostic server    {"url": "https://10.244.0.87:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Shipping config to diagnostic server    {"url": "https://10.244.0.86:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   events  failed to apply Kong configuration to https://10.244.0.87:8444: failed posting new config to /config: making HTTP request: Post "https://10.244.0.87:8444/config?check_hash=1&flatten_errors=1": dial tcp 10.244.0.87:8444: connect: connection refused     {"v": 1, "type": "Warning", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "KongConfigurationApplyFailed"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   events  failed to apply Kong configuration to https://10.244.0.86:8444: failed posting new config to /config: making HTTP request: Post "https://10.244.0.86:8444/config?check_hash=1&flatten_errors=1": dial tcp 10.244.0.86:8444: connect: connection refused     {"v": 1, "type": "Warning", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "KongConfigurationApplyFailed"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   No configuration change, skipping sync to Kong  {"url": "https://10.244.0.13:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Shipping config to diagnostic server    {"url": "https://10.244.0.13:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Config status changed, notifying        {"v": 1, "configStatus": "ApplyFailed"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z error   Failed to recover from configuration rejection with fallback configuration      {"error": "failed to extract broken objects from update error: no broken objects found in UpdateError"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Sending configuration to gateway clients        {"v": 1, "urls": ["https://10.244.0.13:8444", "https://10.244.0.86:8444", "https://10.244.0.87:8444"]}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   events  successfully applied Kong configuration to https://10.244.0.13:8444     {"v": 1, "type": "Normal", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "KongConfigurationSucceeded"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Shipping config to diagnostic server    {"url": "https://10.244.0.86:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   events  failed to apply fallback Kong configuration to https://10.244.0.86:8444: failed posting new config to /config: making HTTP request: Post "https://10.244.0.86:8444/config?check_hash=1&flatten_errors=1": dial tcp 10.244.0.86:8444: connect: connection refused    {"v": 1, "type": "Warning", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "FallbackKongConfigurationApplyFailed"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Shipping config to diagnostic server    {"url": "https://10.244.0.87:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   events  failed to apply fallback Kong configuration to https://10.244.0.87:8444: failed posting new config to /config: making HTTP request: Post "https://10.244.0.87:8444/config?check_hash=1&flatten_errors=1": dial tcp 10.244.0.87:8444: connect: connection refused    {"v": 1, "type": "Warning", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "FallbackKongConfigurationApplyFailed"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   No configuration change, skipping sync to Kong  {"url": "https://10.244.0.13:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   Shipping config to diagnostic server    {"url": "https://10.244.0.13:8444", "v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z error   dataplane-synchronizer  Could not update kong admin     {"error": "failed to recover from gateways sync error: performing update for https://10.244.0.87:8444 failed: failed posting new config to /config: making HTTP request: Post \"https://10.244.0.87:8444/config?check_hash=1&flatten_errors=1\": dial tcp 10.244.0.87:8444: connect: connection refused\nperforming update for https://10.244.0.86:8444 failed: failed posting new config to /config: making HTTP request: Post \"https://10.244.0.86:8444/config?check_hash=1&flatten_errors=1\": dial tcp 10.244.0.86:8444: connect: connection refused\nperforming update for https://10.244.0.86:8444 failed: failed posting new config to /config: making HTTP request: Post \"https://10.244.0.86:8444/config?check_hash=1&flatten_errors=1\": dial tcp 10.244.0.86:8444: connect: connection refused\nperforming update for https://10.244.0.87:8444 failed: failed posting new config to /config: making HTTP request: Post \"https://10.244.0.87:8444/config?check_hash=1&flatten_errors=1\": dial tcp 10.244.0.87:8444: connect: connection refused"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:10Z debug   events  successfully applied fallback Kong configuration to https://10.244.0.13:8444    {"v": 1, "type": "Normal", "object": {"kind":"Pod","namespace":"kong","name":"kong-controller-76fcbdfbd-kjcsm","apiVersion":"v1"}, "reason": "FallbackKongConfigurationSucceeded"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:13Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:13Z debug   No configuration change; pushing config to gateway is not necessary, skipping   {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-admin-2kvk9","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z info    controllers.KongAdminAPIService Reconciling Admin API EndpointSlice     {"v": 0, "namespace": "kong", "name": "kong-gateway-admin-2kvk9"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:15Z debug   controllers.EndpointSlice       Reconciling resource    {"DiscoveryV1EndpointSlice": {"name":"kong-gateway-proxy-ncb8k","namespace":"kong"}, "v": 1, "namespace": "kong", "name": "kong-gateway-proxy-ncb8k"}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:16Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:16Z debug   Parsing kubernetes objects into data-plane configuration        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:16Z debug   controllers.KongLicense No KongLicense available        {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:16Z debug   Successfully built data-plane configuration     {"v": 1}
kong-controller-76fcbdfbd-kjcsm ingress-controller 2024-06-18T12:27:16Z debug   Sending configuration to gateway clients        {"v": 1, "urls": ["https://10.244.0.13:8444", "https://10.244.0.86:8444", "https://10.244.0.87:8444"]}

pmalek avatar Jun 18 '24 12:06 pmalek