We are starting to think this is an issue between our K8S upgrade to 1.21 from 1.19.
- 1.19 - it was working here (no code/config changes)
- 1.20 - dont know if it works or not we only upgraded here to get to latest
- 1.21 - does not work
We know it worked before and as a quick test we deployed it into an older cluster (1.17) and it looks to work as-is.
Our plan, because we are in need, is to try and downgrade (recreate the cluster) to 1.20 and if that does not work go to 1.19.
Maybe it is related to this according to the upgrade log for K8S?
Service account tokens bound to a pod is now a stable feature. The feature gates will be removed in 1.21 release. For more information, refer to notes below on the changelogs.
>kubectl logs my-platform-client-c85ff7478-m7876 -n platform-445-staging
Aug 06, 2021 4:08:37 PM io.fabric8.kubernetes.client.Config
Aug 06, 2021 4:08:37 PM io.fabric8.kubernetes.client.Config
Aug 06, 2021 4:08:37 PM io.fabric8.kubernetes.client.Config
Aug 06, 2021 4:08:37 PM io.quarkus.runtime.ApplicationLifecycleManager run
Message: configmaps "my-config" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "platform-445-staging". Received status: Status(apiVersion=v1, code=403, details=StatusDetails(causes=[], group=null, kind=configmaps, name=my-config, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=configmaps "my-config" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "platform-445-staging", metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Forbidden, status=Failure, additionalProperties={}).