-
Bug
-
Resolution: Done
-
Major
-
None
-
4.14, 4.15, 4.16
-
Important
-
No
-
5
-
OSDOCS Sprint 256
-
1
-
Rejected
-
False
-
Description of problem:
need the Service Account's token to define a TriggerAuthentication for the Ingress autoscaling. But token of the created serviceaccount thanos was none
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-06-03-060250
How reproducible:
100%
Steps to Reproduce:
1. % oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-0.nightly-2024-06-03-060250 True False 4h52m Cluster version is 4.16.0-0.nightly-2024-06-03-060250 2. % oc -n openshift-ingress-operator create serviceaccount thanos serviceaccount/thanos created 3. The "Tokens" of the serviceaccount thanos is none % oc -n openshift-ingress-operator describe serviceaccount thanos Name: thanos Namespace: openshift-ingress-operator Labels: <none> Annotations: openshift.io/internal-registry-pull-secret-ref: thanos-dockercfg-wct9m Image pull secrets: thanos-dockercfg-wct9m Mountable secrets: thanos-dockercfg-wct9m Tokens: <none> Events: <none> %
Actual results:
The "Tokens" of the serviceaccount thanos is none
Expected results:
The "Tokens" should be as "thanos-token-thcr4" as before
Additional info:
- is related to
-
OCPBUGS-35181 CMA should support bound service account tokens
- New
-
OCPBUGS-37431 "Using service accounts in applications" doc inconsistencies regarding legacy service account tokens
- New
- relates to
-
OCPBUGS-13226 Clarify automatically generated service account tokens
- Closed
- links to
(5 links to)