Skip to content

Centralized OAuth2 authentication with Kong Ingress Controller Not Working #1833

Answered by shahamit
shahamit asked this question in Q&A
Discussion options

You must be logged in to vote

I could resolve the "address field not be populated for the ingress resource" problem by disabling traefik ingress controller that gets by default installed on k3s. After disabling it, my ingress resource does get an external ip assigned after which apis can be called from outside.

The plugin still isn't getting activated though. The original problem remains

Replies: 1 comment 7 replies

Comment options

You must be logged in to vote
7 replies
@shaneutt
Comment options

@shahamit
Comment options

@shaneutt
Comment options

@shahamit
Comment options

@shaneutt
Comment options

Answer selected by shaneutt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants