New namespace, kong resource processing failed: failed to fetch the secret about charts

[rainest]

Does the Secret actually exist? I'm unsure whether you meant that cert-manager actually created it and you can kubectl get -n sandbox partner-sandbox-xxx-app successfully or if cert-manager is just configured to create it.

Which KIC version are you using, and does the issue persist if you make some trivial update to the Ingress (add a garbage annotation or similar). We start tracking Secrets based on their attachment to an Ingress, so I'm curious if there was maybe some race condition bug that failed to start tracking it--updating the Ingress forces a rescan of it and any attached resources.

Namespace-related issues shouldn't happen unless you've manually created RBAC configuration for your KIC service account and forgotten Secret read access in a namespace. There is also the --watch-namespaces feature, but that applies to all resources--if it was misconfigured, the controller would not see the Ingress either.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.