Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2022

[Spike]: Evaluate impact of SA token non-creation by K8s 1.24

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • 1.6.0
    • None
    • ArgoCD, Operator
    • None
    • 5
    • False
    • None
    • False
    • GITOPS Sprint 219, GITOPS Sprint 220

      Details:

      https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#no-really-you-must-read-this-before-you-upgrade-1

      We need to find out if and how this impacts our Operator and its workloads (Argo CD, ApplicationSet, etc). Does it matter when no tokens are stored in the secret anymore by default?

      Acceptance Criteria

      • Find out if any impact when LegacyServiceAccountTokenNoAutoGeneration is default to true. Identify any changes required on OpenShift GitOps (operator, argocd, kam)

            rismishr Rishabh Mishra (Inactive)
            jfischer@redhat.com Jann Fischer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: